[gst-devel] JACK and GStreamer, from the horse's mouth

Edgard Lima edgard.lima at indt.org.br
Thu Nov 30 19:46:51 CET 2006

pull or push...it will end-up at the same thing....

if all elements are working in push mode and you have jackaudiosink, 
like this:

src -> dec1 -> filter1 -> filter2 -> ... filterN -> queue -> jackaudiosink

it is desirable to have a queue before the audiosink (possible with a 
min-threshold) to avoid decode samples arrive too late. At some time the 
queue will be full and it wil works like pull.
Even if all the pipeline is working in pull mode, it would be also 
desirable to have a queue so that the audiosink has data already ready 
when need it.


ext Jussi Laako escreveu:
>> The pull model for audio playback creates as many problems as it
>> solves. It makes some things easier, but others more
> I have to also say, that practically all the audio hardware works in
> "pull-model". They'll trigger hardware interrupt each time they need
> more data, in other words, they "pull" data. You can't "push" data
> there. In pull-based model you bring this same functionality up to
> software, otherwise you need nasty buffer somewhere in-between.
> 	- Jussi
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel

More information about the gstreamer-devel mailing list