GNOME Bugzilla – Bug 784671
*decodebin: [API]: autoplug-discard
Last modified: 2018-06-18 22:47:31 UTC
decodebin2 now emits a signal that uridecodebin relays, letting the application decide whether a stream should be discarded altogether, thus exposing no pad for it. An example use case is an application that doesn't want to filter streams based on their caps, but based on their stream ids. It will thus wait for the signal to be emitted with the source pad of a demuxer, and return TRUE if its stream id is not wanted.
Created attachment 355122 [details] [review] *decodebin: [API]: autoplug-discard
Created attachment 355124 [details] [review] *decodebin: [API]: autoplug-discard decodebin2 now emits a signal that uridecodebin relays, letting the application decide whether a stream should be discarded altogether, thus exposing no pad for it. An example use case is an application that doesn't want to filter streams based on their caps, but based on their stream ids. It will thus wait for the signal to be emitted with the source pad of a demuxer, and return TRUE if its stream id is not wanted.
Comment on attachment 355124 [details] [review] *decodebin: [API]: autoplug-discard Isn't this equivalent to returning GST_AUTOPLUG_SELECT_SKIP from autoplug-select?
(In reply to Sebastian Dröge (slomo) from comment #3) > Comment on attachment 355124 [details] [review] [review] > *decodebin: [API]: autoplug-discard > > Isn't this equivalent to returning GST_AUTOPLUG_SELECT_SKIP from > autoplug-select? Just had a similar use case so I've been able to test it, yes, autoplug-select fits the use case too, we can close WONTFIX :)