Streaming video via media source extension fails on first mp4 moof/mdat frame

696 views
Skip to first unread message

Yukkuri Shiteimasu

unread,
Oct 10, 2016, 10:45:52 AM10/10/16
to Chromium HTML5
Hi, i am trying to implement a video streaming, where mp4 container is fetched frame-by-frame and then fed into SourceBuffer of MediaSource element, but experiencing some problems in webkit family of browsers without clear understanding why.

All what i get from chrome://media-internals is

"Append: stream parsing failed. Data size=65488 append_window_start=0 append_window_end=inf"

where 65488 is the size of first mp4 actual frame, first [moof mdat] pair after [ftyp moov] header.

All moof/mdat frames in the file are 1 second long, consisting of 24 video samples @ 24 fps.

The --enable-logging=stderr --v=2 options did not revealed any additional information.

Notably, the same file plays fine when not fetched chunk-by-chunk, but rather placed directly in <video/> tag.
Also, it plays fine in firefox both in plain <video/> and chunked progression.

No errors about the file structure were reported by any of following programs: mplayer, ffmpeg, vlc and mp4file --dump

Please advise, how to get more detailed information on why it refuses to parse frame-chunked video.

In case it helps, i am attaching sample video file and sample.html with js that loads and tries to play the video from local filesystem via input file selector (wasn't able to find a way to play it without input file dialog at all; also note that on default security settings you might be forbidden to play mediasource when html was fetched directly from local filesystem, so you might need some dummy http-server like "python2 -m SimpleHTTPServer" serving current directory content via http/8000 or use a --allow-file-access-from-files switch)
sample.html
sample.mp4

PhistucK

unread,
Oct 10, 2016, 11:28:50 AM10/10/16
to Yukkuri Shiteimasu, Chromium HTML5
You can search crbug.com for an existing issue and star it. If you cannot find one, file a new issue using the "New issue" link on the same page.
Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment. It just wastes the time of Chrome engineers and sends unnecessary e-mails to all of the people who starred the issue.

You can reply with a link to the found or created issue and might get triaged (and fixed) faster.

Thank you.



PhistucK

--
You received this message because you are subscribed to the Google Groups "Chromium HTML5" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-html5+unsubscribe@chromium.org.
To post to this group, send email to chromiu...@chromium.org.
Visit this group at https://groups.google.com/a/chromium.org/group/chromium-html5/.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

Reply all
Reply to author
Forward
0 new messages