[13:06] <OvenWerks> zequence: about running jackdbus the whole session, qjackctl by default stops jack on exit. I know we are not worrying about this right now, but wanted to mention it so maybe one of us remembers at the time. In the long run it may be better to concider qjackctl replaced by -controls and patchage.
[13:07] <OvenWerks> qjackctl is a great jack starter and patchbay, but we would no longer need a jack starter.
[13:10] <OvenWerks> Another thought for -controls is something that displays any jack servers that are running and provides a way of killing unwanted jackd processes, though starting jackbus at session start should stop second jackds from starting.
[13:10]  * OvenWerks is off to work
[20:30] <OvenWerks> zequence: further to my earlier musings... I am guessing the -controls might turn jack as session audio server off and on and so it would be reasonable to change the users qjackctl config at that time. In fact there could be a button for "update qjackctl" that would set device, rate, latency as well.
[20:31] <OvenWerks> zequence: it is interesting that qjackctl defaults to 44.1k and jackdbus itself defaults to 48k
[20:51] <OvenWerks> however, I think I found qjackctl defaults to 48k at home and is set to 44.1k for debian/ubuntu packages.