Stream selection with adaptivedemux

Joseph Newman joseph at
Mon Apr 19 09:04:11 UTC 2021


Why does adaptivedemux (and by extension dashdemux) blindly unlink its source pads when advancing a period and immediately proceed to present new source pads for the new period and continue playing? Is there not a risk that there is still buffered data in the original pipeline that needs to be fully drained first?

Was stream selection not considered an appropriate way of solving this, where a stream collection message could be sent for the imminent period, but the period only advanced when a stream selection message is received once it is known that all sinks have completed draining?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the gstreamer-devel mailing list