[16:18] <OvenWerks> Working on autojack... to start jack, pa bridging, a2jmidid, zita-ajbridging etc. at session start.
[16:19] <OvenWerks> This will probably not be ready for 16.04. running zita-ajbridging for every audio IF we find is probably not the best idea as it does use more CPU than some other things. 
[16:21] <OvenWerks> There needs to be a configuration setup for it that explains clearly to the user what they are setting up :)
[16:23] <OvenWerks> I started working on a patch bay (does the same as "connections" in qjackctl) except it would allow a bridge to be created at that time. That is it would show audio devices that are not yet connected to jack and if the user connects them would create the bridge at that time.
[16:25] <OvenWerks> I have gotten the GUI figured out... at least the starting part. I can change the jack master device on the fly so far... but it appears that I need to disconnect all ports first, remember where they are connected and then reconnect after changing the device.
[16:27] <OvenWerks> I also have to consider what to do with connections made to port 3 or more if the new device does not have more than 2 :) although that is an unlikey circumstance.
[16:29] <OvenWerks> Anyway, my patch panel seems to be headed to being a system configuration tool as well as patch panel. That is, it will save a configuration for autojack to use at session start.
[16:33] <OvenWerks> I do not want to put out something that creates more trouble than it solves, so it will take longer than I thought.
[19:09] <zequence> OvenWerks: Does applications keep their connection to jack when you change the interface?
[19:10] <zequence> Or, I mean, they don't of course
[19:10] <zequence> But, do they accept a new connection happily
[19:14] <OvenWerks> They accept the new connections just fine.
[19:14] <OvenWerks> a2jmidid remains running too.
[19:15] <OvenWerks> Changing the master device should be a do once operation configuration wise.
[19:16] <zequence> When you change the device, the jack server keeps running?
[19:16] <OvenWerks> except in the case of a USB device being configured master where it is not plugged in at session start.  :)
[19:17] <OvenWerks> yes. all of the connections between applications remain... for example ardour chaneel to master or to standalone effects rack.
[19:18] <OvenWerks> in fact connections to zita bridge or pabridge that are not connected to system:whatever ramain too.
[19:18] <OvenWerks> *remain.
[19:19] <OvenWerks> Effectively I have to set up a database for all devices that includes who owns it and who it connects to.
[19:20] <OvenWerks> I have to be able to kill a zita bridge process so I can use that device as master
[19:21] <OvenWerks> Then reconnect what was connected there to master :)
[19:30] <OvenWerks> zequence: just had a thought. possibly entering free run mode first would get applications to handle the dis/connect on their own. I have to start talking to jack first though. Have to figure out a database format before that :) Lots to do.