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

Paul Davis paul at linuxaudiosystems.com
Sat Nov 25 01:11:21 CET 2006

> So until someone either starts writing a GStreamer application which has
> Jack output as a priority I don't see this changing. 

i thought that the whole idea of gstreamer was to remove this kind of
pressure from app developers. the only pressure for jack output is going
to come from *users* who want to use (say) amarok/rhythmnbox in
combination with other JACK clients. the developers of these apps have
no reason to strive for this functionality - they've been told its part
of the gstreamer/phonon/whatever infrastructure. users are the only ones
who care (e.g. as of the last week, me :)

> Also with the work
> happening in the distributions to try to move away from the situation
> with a separate system for normal and pro audio I am not sure how much
> pressure there will be for a resolution here long term. Seems the
> distro's prefer a MacOSX like situation with one system for both targets

a noble sentiment. the problem is that even gstreamer (initially) and
certainly almost all desktop media app developers ran screaming when
those of us with pro-audio leanings said "the basic model needs to be
build around a pull design". and guess what? one of the reasons we said
this was that CoreAudio, which was clearly satisfying both pro and
desktop audio needs, was built around a pull design. yet people continue
to insist that the pull model cannot work, that its too complex for
people to use etc etc. 

More information about the gstreamer-devel mailing list