Comment 8 for bug 1201739

On Wed, September 11, 2013 7:02 pm, Bill Kirkpatrick wrote:
> Len, thank you very much for your help. Once the PCI timers were
> mangled everything has worked exactly as expected. I'm not an audio

Older machine then, PCIe slots are all set to 0. Glad it worked for you.

> pro, so I appologize for using the wrong termanology around sources and

Not a problem at all.

> sinks. Jack seems to have a bad rap, it is actually quite useful to the
> average Joe (Although Grandma did throw both me and the computer out of
> the house :) ) All I really wanted in the end was a good equalizer, as
> I end up with a headache after about an hour of listening to streaming
> mp3 music services.

Anyone who actually does much (semi)pro-audio in Linux, likes jack. It
does take some getting used to.

> If you have any pull with the jackd team(s), I ran into only one very

I don't. I wish I could code well enough to help is all.

> small annoyance. When a patchbay is active, jackd insists on creating a
> new automatic link to the system playback when an application port
> defined in that patchbay conneccts/reconnects. Thus putting the patched
> connections in parallel with the original stream. Reproduce using a VLC

That would not be jack, but the application connecting to jack. It is
normally considered correct not to auto connect, but on the other hand, a
user not used to the jack world expects when they start an application it
will just make sound. Most serious users would prefer some kind of session
management instead. (there are a number out there)

For a really bad example of auto connect... Audacious connects left to all
Odd channels and right to all even... sure makes a mess of things when you
have 10 or more output channels.

Anyway, I think this bug could be made invalid.

--
Len Ovens
www.OvenWerks.net