gst-plugins-bad: aacparse: allow parsed frames on sink pad

Sebastian Dröge sebastian.droege at collabora.co.uk
Sun Feb 27 00:25:33 PST 2011


On Sun, 2011-02-27 at 00:01 +0000, Tim-Philipp Müller wrote:
> On Sat, 2011-02-26 at 23:42 +0100, Sebastian Dröge wrote:
> 
> > > Shouldn't be that much work, all the information is inside decodebin2
> > > already. You only need to look at all elements in the current
> > > GstDecodeChain and if the element you're going to plug next has the same
> > > type as one of the elements in there you don't use it.
> > > 
> > > I'll work on it now and will CC you in the bugreport with the patch :)
> > 
> > Oh well, I've simply pushed it now, it was even easier than expected:
> > 5058f792263e4214f4655c5ed5956ebfbeb17c99
> > 
> > Feel free to change all parsers now to accept their own output again ;)
> 
> We probably need something a bit more sophisticated though, or limit
> this to parser factories. It's perfectly fine (and common enough) to
> e.g. have two id3demux in a row.

Hmm, I can add a check for parsers there. Good point, I forgot the
demuxers that are no real demuxers and don't get their own
GstDecodeGroup.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20110227/6f88c190/attachment.pgp>


More information about the gstreamer-devel mailing list