
Recherche avancée
Médias (1)
-
Bug de détection d’ogg
22 mars 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Video
Autres articles (58)
-
Submit bugs and patches
13 avril 2011Unfortunately a software is never perfect.
If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
You may also (...) -
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs -
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
Sur d’autres sites (15397)
-
How to publish or push the live stream to RTMP-Nginx server using php and FFmpeg ?
27 juin 2020, par vijendarI want to push the live stream to the RTMP-Nginx server. I am recording the webcam and sending it to the PHP running server using the socket but couldn't find the proper way to push the stream on the RTMP-Nginx server. I am appending the stream after receiving through the socket. I have used this


ffmpeg -re -i uploads/test.webm -vcodec libx264 -preset fast -maxrate 1500k -c:a aac -b:a 128k -ac 2 -ar 44100 -f flv rtmp://x.xx.xxx.xx/live/xxx


to push on the RTMP-Nginx server. But it's executing on the very first received packet of the video stream and then terminated. I know It's not working with a continuous appended video stream. may be FFmpeg reading as a whole. Hoping for the right direction. Thanks in advance.


-
Live Streaming WebM with Wowza Server
2 décembre 2010, par noreply@blogger.com (John Luther)Guest blogger Charlie Good is CTO and co-founder of Wowza Media Systems
As a company, we at Wowza move fast and like to tinker. When WebM was announced in May, we saw it as a promising new approach to HTML5 video and decided to do an experiment with live WebM streaming over http.
Adding WebM VP8 video and Vorbis audio to the other encoding formats that our server supported was easy (we designed the Wowza server to be codec-agnostic). We then created a WebMfile and implemented WebM HTTP streaming.
We originally created the demo as a proof-of-concept for the IBC show in September, 2010 but have made it available to watch on our web site.
The file is streamed live (more precisely, "pseudo-live") over http using the Wowza server-side publishing API (PDF). The result is very impressive ; playback starts fast and the VP8 image quality is fantastic.
You will need a WebM-enabled browser or VLC media player 1.1.5 to view the live stream.
If you’re interested in keeping up with Wowza’s WebM progress, visit Wowza Labs or drop us a note at info@wowzamedia.com.
-
Red5 live stream - huge delay on localhost
23 janvier 2013, par user1958067I m running Red5 1.0.0 RC1, with JW Player and ffmpeg on Linux Mint14
There is a huge delay while streaming, even when everythings happening on my
machine/localhost
.I do following steps :
-
FFmpeg :
ffmpeg -i 'http://localhost:port' rtmp://localhost/oflaDemo/live.flv
-
Red5 :
TCPnoDelay
ist set to true. -
JW Player : Bufferlength is set to 0. Also tried 2 and 3.
:
<code class="echappe-js"><script type=&#39;text/javascript&#39;><br />
jwplayer(&#39;mediaspace&#39;).setup({<br />
&#39;flashplayer&#39;: &#39;player.swf&#39;,<br />
&#39;file&#39;: &#39;live&#39;,<br />
&#39;type&#39;: &#39;rtmp&#39;,<br />
&#39;streamer&#39;: &#39;rtmp://localhost/oflaDemo&#39;,<br />
&#39;controlbar&#39;: &#39;none&#39;,<br />
&#39;autostart&#39;: &#39;true&#39;,<br />
&#39;bufferlength&#39;: &#39;3&#39;,<br />
&#39;width&#39;: &#39;640&#39;,<br />
&#39;height&#39;: &#39;380&#39;<br />
});<br />
</script>The delay is something between 7-10 seconds !
This all is happening on and from localhost, so bandwith shouldnt be the issue. -