[Bug 668094] dashsink: New sink for DASH

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=668094

--- Comment #20 from Isaac Smith <isaac at isrv.pw> ---
(In reply to Alex from comment #19)
> (In reply to Isaac Smith from comment #18)
> > After using the above patch, the dash.js reference player attempts to play
> > the stream but dies with a media player error. It appears that the MP4
> > segments are getting written incorrectly, they don't play in any player I've
> > tested.
> > 
> > Here's a sample MPD:
> > https://video.crosscommunity.com/dashtest/GStreamer%20Adaptive%20Streaming.
> > mpd 
> > 
> > Produced with the pipeline:
> > 
> >     videotestsrc ! x264enc ! h264parse ! mp4dashmux fragment-method=1
> > fragment-duration=2 ! dashsink fragment-duration=2
> > 
> > When played in dash.js on Firefox, resulting in the error "Video Element
> > Error: MEDIA_ERR_DECODE". When played using playbin, it fails to play after
> > the following warnings:
> > 
> >     0:00:00.698391401 15039 0x7f6474005540 WARN                 qtdemux
> > qtdemux.c:6512:gst_qtdemux_process_adapter:<qtdemux0> Unknown fourcc while
> > parsing header : styp
> >     0:00:00.828871236 15039 0x7f6474005540 WARN                 qtdemux
> > qtdemux.c:6315:gst_qtdemux_process_adapter:<qtdemux0> error: This file is
> > invalid and cannot be played.
> >     0:00:00.828909916 15039 0x7f6474005540 WARN                 qtdemux
> > qtdemux.c:6315:gst_qtdemux_process_adapter:<qtdemux0> error: atom ...Q has
> > bogus size 904110311
> > 
> > My best guess is that mp4dashmux isn't working correctly, but I'm way out of
> > my depth here so I have no idea what's wrong.
> 
> I also have a problem corresponding to the absence of 'codecs' property. I
> have tested similar pipeline (but without 'h264parse' before mp4dashdemux)
> in Chrome, Firefox and Epiphany, and only Epiphany was able to play my
> stream (with dash.js library) without 'codecs' property in manifest file.
> 
> But I don't have a problem (MEDIA_ERR_DECODE), described in your last
> message. My guess is that 'h264parse' is not necessary in your pipeline, but
> I am not sure.

I only get the MEDIA_ERR_DECODE message after fixing the codecs property issue
using the patch I posted earlier.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.