On Thu, August 26, 2010 11:07 am, Paul Davis wrote: That's an important point. Personally I appreciate the flexibility of having the editor already connected and taking part in the flow of events by default. On a similar note I am wondering what would be the potential issue with enabling volume control on a per route basis directly in jack. Similar to how PA handles volume control per app but in jacks case it would be per route. I can think of a handy tool that would allow managing volume control on all routes or built into qjackctl or even the window manager or stand alone like gnome-vu-control. The current system requires that the user connect the route to a mixer app and the mixer app to the destination input if they want per route volume control. Another way to deal with this situation would be to make all connections pass through the mixer app by default. This could be handled automagically in qjackctl but I like the potential flexibility of per route volume control directly in jack. Just wondering if this has been discussed before? I can't recall. -- Patrick Shirkey Boost Hardware Ltd.

Thanks tremendously, everyone. Yes, I want to be able to configure anywhere from two to 24 inputs, each with its own Jackd identity. I will now commence study :-) J.E.B.