Re: Setting pulse not to grab a particular sound device

> > > 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.
>
> Which would mean that PA, depending on which 'sound card'
> it is using, would be either a Jack client, or be independent
> when using another card ?

> > 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.
>
> I think it makes a *lot* of sense. As I said before, I
> don't use PA not because I hate it, but because I don't
> need it, and until now it just got in my way so I removed
> it. But if it could operate as a Jack client I wouldn't
> mind having it running. As long as it doesn't autoconnect
> that is - it would be to the wrong ports most of the time
> and I've already been paying real cash for the damage caused
> by apps doing that.