Skip to content

urisourcebin: Ensure all stream-start are handled

Edward Hervey requested to merge bilboed/gstreamer:urisourcebin-sticky-streamstart into main

In order to ensure all initial events (stream-start, caps, ..) are present on pads that we expose, those various sticky events are propagated (from parsebin to multiqueue output, from multiqueue output to exposed pads).

The problem was that the "hack" in urisourcebin to inform downstream elements that the stream is parsed data and a collection will be present was only done in one place : a probe on the output of parsebin ... but the stream-start could potentially have already been propagated to the output pads before that.

In order to fix that, we make sure any pending sticky stream-start event is updated before being propagated.

Fixes #3788 (closed)

Merge request reports