Comment 6 for bug 1201739

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 pro, so I appologize for using the wrong termanology around sources and 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.

Jackd, with Pulseaudio on top, and the Calf plugin pack, has given me that and really far more than I could have imagined. More sliders, buttons, and knobs than a human should be allowed to play with. Quite great, actually.

If you have any pull with the jackd team(s), I ran into only one very 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 playlist and an activated patchbay where VLC is a defined "Readable Client/Output Port". Every song will trigger a new direct link to the system playback port, constantly putting everything back in parallel with the patchbay processing.

My guess at a "best fix" would be for jackd to not create any automatic patches if a patchbay is active and a port in that patchbay appears/connects on the system (a port already in Connection window of qjackctl will be used). If it has to draw a new, previously non-exsistant port instance, in the Connections window then, yes, make the automatic connection. The workaround is surely easy enough, I just tell everything to use Pulse and patch things in using Pulse's more persistant connection.