On Wed, 17.06.09 02:22, Fons Adriaensen (
fons@...) wrote:
>
> On Wed, Jun 17, 2009 at 01:57:40AM +0200, Lennart Poettering wrote:
>
> > And what I was proposing at the beginning of that other thread is that
> > if Jack takes a service name on the bus PA could watch for it and load
> > the connectivity modules automatically, providing some ports in jack
> > that folks can connect if they wish.
>
> I'm trying to understand this and failing (but maybe
> at 02:25 it's just too late).
>
> "some ports in jack that folks can connect if they wish"
>
> If jack has taken over a particular sound card, and
> created its own ports for that card, what would those
> ports you refer to represent ? Applications ?
Yes. Everything that doesn't use JACK natively but does support PA
would appear on those ports, since JACK would appear as virtual sound
card inside of PA.
Initially, when I wrote the PA/JACK connectivity modules for PA I
wrote it mostly as a toy and to understand jack better, not because it
really made much sense to me to use them for anything serious.
However as it turned out the lines between audio production and
desktop audio are blurred and a lot of folks seem to be using those
modules and have been asking for closer integration. And heck, maybe
it even makes sense, dunno.
Lennart
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
