[Bug 784791] New: dashdemux: don't rebuild streams if manifest has not changed

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Tue Jul 11 12:24:05 UTC 2017


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

            Bug ID: 784791
           Summary: dashdemux: don't rebuild streams if manifest has not
                    changed
    Classification: Platform
           Product: GStreamer
           Version: git master
                OS: All
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gst-plugins-bad
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: bugzilla at ashley-family.net
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

Every time the manifest is re-loaded, dashdemux creates a new set of stream
objects and destroys the old objects. It then tries to position playback within
these new streams to match the position before the manifest update. As shown by
comments in the source code, this position calculation is not entirely accurate
and there are several open bug tickets relating to manifest refreshes. For
example  https://bugzilla.gnome.org/show_bug.cgi?id=762933

In most situations, the manifest hasn't actually changed and there is no need
to perfom the complex, expensive and slightly inaccurate process of full stream
recreation. To make matters worse, some commercial DASH packagers set the
minimumUpdatePeriod to the same as fragment duration, causing a manifest reload
after every fragment.

I think it would be useful if dashdemux detected that the manifest has not
changed so that it could avoid the whole stream re-creation step when there are
no changes.

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


More information about the gstreamer-bugs mailing list