Recherche avancée

Sur d’autres sites (10119)

• Prevent suspend event when streaming video via HTML video tag

  24 septembre 2014, par jasongullickson

  I seem to be having the opposite problem of most people who are streaming video using the HTML video tag ; I’m saturating the client with data.

  When playing a long video served via ffserver (webm container) everything works great but eventually the browser (Chrome in this case) will begin throwing "suspend" events. After a number of these ( 50-100), a "stalled" event will fire and playback will stop.

  I believe the problem is that once Chrome has buffered a certain amount of video it goes into "suspend" and stops downloading more data. I’ve tested this theory by throttling the speed at which video data is delivered, and if I keep the delivered frame rate close to the playback rate, I can prevent this from happening, but of course deliberately holding back server performance isn’t ideal.

  What I’m looking for is either a way to suppress this "suspend" behavior altogether, or alternatively a way to respond to the event that prevents the eventual "stalled" state.

  Presumably the browser at some point exits the "suspend" state and begins requesting data again, but I haven’t actually observed this occurring. I’m using a chain of mpeg2 -> ffmpeg -> ffserver to stream the video so if the browser is attempting to resume loading data I don’t see the request in my application. I could use a proxy or a sniffer to watch for the traffic but I would expect that maybe there is an ffserver log that can tell me the same thing ? In any event if it’s attempting to resume the download it’s failing, and there’s no indication server-side that there’s a reason for the request to fail (in fact I can pull up the same video feed from ffserver and see it playing correctly).

  So I feel like I’ve isolated this to a client-side playback issue, and one where the browser is voluntarily giving up on loading the data, but I’m not sure how to convince it to "not do that", or at least attempt to resume when it runs the buffer dry.

• Fragmented mp4 cannot be played on pure html5 video

  23 novembre 2017, par Kevin Youngho Seo

  I need to use a video tag to serve over 3GB of video on the web.
  When the page is loaded, it takes a long time for the media element to receive the ’loadedmetadata event’.

  I’ve found that the size of the moov box is too large (33MB).
  So when I re-encoded it with the ’empty_moov + frag_keyframe’ option of ’ffmpeg’, but it also took longer to fetch all fragmented information from the ’Inspector - Network’ tab in Chrome.

  Is there a way to speed up loading when playing ’fragmented mp4’ with html5 video tag ?

• Debugging an MP4 opened by VLC but not by ffplay

  15 mai 2017, par MaMazav

  I’m writing a code which creates MP4 files. To check it I’ve created an MP4 file.

  The file is played correctly by VLC and Firefox, but not by ffplay or by Chrome. I guess the file contains error which VLC can cope with but more aggressive MP4 reader cannot.

  I’ve thought about repairing the file and check what are the differences to fix my code. However I tried some programs to repair MP4 files, without success until now.

  Can someone reccommend another way to debug the problem, or a good tool to fix MP4 files ? The file is a fragmented MP4 contains both the init section (ftyp, moov boxes) and one fragment section (moof and empty sidx).

  Here is the video file :

  https://www.dropbox.com/s/rojxzvkfxfj31u8/400k00001-3_serialized.mp4?dl=0

  EDIT : It doesn’t work also in Firefox, when using Media Source Extensions like in this example :
  http://people.mozilla.org/ jyavenard/tests/mse_mp4/paper.html

  (don’t forget to enable MSE on Firefox, as explained here :
  http://www.linuxveda.com/2015/04/02/enable-mse-native-html5-support-firefox-linux/)

  EDIT2 : In chrome ://media-internals, I see the following error with the above example :
  Append : stream parsing failed. Data size=131072 append_window_start=0 append_window_end=inf

  (Change the URL to be the file and change the codec to be ’avc1.4d401f’ instead of ’avc1.64000d,mp4a.40.2’).