[Bug 750402] tsdemux: pads are removed before new ones are added

[GStreamer (GNOME Bugzilla)]

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

--- Comment #9 from Thiago Sousa Santos <thiagossantos at gmail.com> ---
Created attachment 315138
  --> https://bugzilla.gnome.org/attachment.cgi?id=315138&action=edit
tsdemux: Push GAP events *after* deactivating old programs

The order in which program switch must happen is:
1) drain all data on old pads (but don't push EOS)
2) add new pads (but don't push any data on them)
3) Push EOS and remove old pads
4) Start pushing data on new pads

There was one caveat in this implementation, which is that when
we activate a sparse pad (step 2) we would push a GAP event. The problem
is that, while being an event, it is actually *data*.

We therefore need to make sure pushing those GAP event is done at the step
we start pushing data.

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