[Bug 739472] multifilesrc: Lost the ability to start at a different frame

[GStreamer (GNOME Bugzilla)]

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

Tim-Philipp Müller <t.i.m at zen.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|git master                  |1.5.90

--- Comment #15 from Tim-Philipp Müller <t.i.m at zen.co.uk> ---
Pushed slightly more conservative version that checks the STARTED flag (with
OBJECT_LOCK, natch):

commit 29afa758589620f4572ca2f1bbbac073318df071
Author: Tim-Philipp Müller <tim at centricular.com>
Date:   Thu Aug 13 17:29:58 2015 +0100

    multifilesrc: fix regression with starting from index set via index
property

    When we haven't started yet, set the start_index when we set the index
property,
    so that we start at the right index position after the initial seek. The
index
    property was never really meant to be for writing, but it used to work, so
let's
    support it for backwards compatibility.

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


(Didn't bother making any of the properties thread-safe, they're not marked as
being mutable in playing state anyway.)

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