Dan Taylor schrieb: > >> -----Original Message----- >> From: Michael Smith [mailto:msmith at xiph.org] >> Sent: Friday, February 20, 2009 5:31 PM >> To: Liang Zhao >> Cc: gstreamer-embedded at lists.sourceforge.net; gstreamer- >> devel at lists.sourceforge.net >> Subject: Re: [gst-devel] can playbin handle the sink >> withdecoding functions? >> >> On Fri, Feb 20, 2009 at 5:28 PM, Liang Zhao <liangzhao.bit at gmail.com> >> wrote: >>> Hi, >>> >>> If I have a audio sink with decoding functions, that means this >> audiosink >>> can decode encoded data and render it to audio device. Can playbin >> handle >>> this type audio sink well? >> No. playbin2 should be able to handle this sort of situation, though, >> if you configure it to. >> >> Mike > > Since the function of playbin is to decide what decoders to use, and > this > platform already IS the decoder, why isn't this element simply replacing > playbin in the pipeline? I don't understand the logic of using a > decoder- > match-and-connect element to front-end a decoder, unless there's an > option > of additional decoders, and this hardware is just one of the many. > > source->[demux->]queue->hw_decoder->audio_sink > playbin{,2} does more that. dump the pieplien graph and see yourself. To give some hints, which source-element, parsers, ... Stefan
