[Bug 701509] dashdemux selects first fragment in the manifest for live streams

Wed Jul 3 11:38:23 PDT 2013

https://bugzilla.gnome.org/show_bug.cgi?id=701509
  GStreamer | gst-plugins-bad | git

Thiago Sousa Santos <thiago.sousa.santos> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |thiago.sousa.santos at collabo
                   |                            |ra.co.uk
         Resolution|                            |FIXED
   Target Milestone|HEAD                        |1.1.2

--- Comment #8 from Thiago Sousa Santos <thiago.sousa.santos at collabora.co.uk> 2013-07-03 18:38:20 UTC ---
commit 5ad2a2d161aad6dc64db53aa5c10daf6ed3d74b4
Author: Alex Ashley <bugzilla at ashley-family.net>
Date:   Tue Jun 11 14:28:53 2013 +0100

    dashdemux: Change first fragment selection for live streams

    When dashdemux selects its first fragment, it always selects the
    first fragment listed in the manifest. For on-demand content,
    this is the correct behaviour. However for live content, this
    behaviour is undesirable because the first fragment listed in the
    manifest might be some considerable time behind "now".

    The commit uses the host's idea of UTC and tries to find the
    oldest fragment that contains samples for this time of day.

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

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.