[Bug 757548] aggregator: Forced to produce data in paused state

[GStreamer (GNOME Bugzilla)]

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

Nicolas Dufresne (stormer) <nicolas at ndufresne.ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #314772|needs-work                  |none
             status|                            |
 Attachment #314772|0                           |1
        is obsolete|                            |

--- Comment #2 from Nicolas Dufresne (stormer) <nicolas at ndufresne.ca> ---
Created attachment 325883
  --> https://bugzilla.gnome.org/attachment.cgi?id=325883&action=edit
This is really a tentative patch, I didn't go around everything to make sure

it is right. What I try is simply move the query (which is done only once) from
pad activation to the moment we receive STREAM_START event.

aggregator: Start the task when linked

Until now we would start the task when the pad is activated. Part of the
activiation concist of testing if the pipeline is live or not.
Unfortunatly, this is often too soon, as it's likely that the pad get
activated before it is fully linked in dynamic pipeline.

Instead, start the task when the first serialized event arrive. This is
a safe moment as we know that the upstream chain is complete and just
like the pad activation, the pads are locked, hence cannot change.

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