
Recherche avancée
Autres articles (28)
-
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir -
Supporting all media types
13 avril 2011, parUnlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)
-
Contribute to a better visual interface
13 avril 2011MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.
Sur d’autres sites (6131)
-
Revision 87136 : Suite au message de nico du 15-01-2015 ...
18 janvier 2015, par spip.franck@… — LogSuite au message de nico du 15-01-2015 http://archives.rezo.net/archives/spip-zone.mbox/2015/01/
j’ai fait un up de version aux plug qui en avaient besoin, parfois, il y avait des différence entre paquet et plugins.xml, et d’autres broutilles -
Revision 110893 : On ne teste pas redis dans l’autodetection (le fait que le module soit ...
27 juin 2018, par marcimat@… — LogOn ne teste pas redis dans l’autodetection (le fait que le module soit chargé, ne veut pas dire que la connexion est configurée !)
(Michel) -
Nginx with rtmp-module stalls between streams
14 janvier 2015, par churchmfI’m experiencing some troubles using NGINX with rtmp-module as a media server. I wish to present a continuous video as a live stream (with up to 60 second latency). However, due to some hardware constraints, I am unable to stream directly from the device. Instead, I can save out X amount of seconds from the device’s buffer as an MP4. My solution has been to save X seconds of video from the device then stream that X seconds, rise and repeat. This has been working mostly well, except for stalls ( 20 seconds) in the stream between calls.
I have searched far and wide for a solution to this however most of the people experiencing this problem have the collection of videos before starting the stream and can simply concatenate them.
My running theory is that when a stream finishes, it does an unpublish event in NGINX followed by a timeout period. This prevents the NGINX server from receiving the next publish until the timeout period has expired. I have tried adjusting nginx.config values related to timeouts, respawns, restarts, and publish, but to no avail.
Pseudocode :
while true> capture X seconds of video to "output.mp4" (this takes less than 300ms)
> stream the MP4 with FFMPEG (takes X seconds using -re)
FFMPEG call :
ffmpeg -re -i "output.mp4" -vcodec libx264 -preset veryfast -maxrate 2000k -bufsize 4000k -g 60 -acodec libmp3lame -b:a 128k -ac 2 -ar 44100 -f flv rtmp :/MYSERVER/live/outputI am using JWPlayer client side to watch the video stream, however I experience similar issues using VLC.
I have been trying to figure this out for a few days and I would appreciate any insight an expert to video streaming and NGINX can give. Thank you !