[01:12] <OvenWerks> wonko: how are things going with qjackctl and jack stops?
[01:12] <wonko> Not sure, walked away with it fine, came back to monitor weirdness and rebooted
[01:12] <wonko> these amazon DP cables are shit
[01:13] <wonko> Huh, this time the mic doesn't get to ardour
[01:13] <OvenWerks> :)
[01:14] <wonko> maybe something was left over that didn't get cleaned up/shut down properly pre-reboot
[01:15] <wonko> that being said though
[01:15] <OvenWerks> That should not be.
[01:15] <wonko> looking at the log I see restarts (I think)
[01:15] <wonko> https://paste.ubuntu.com/p/BV8hbmFRzc/
[01:16] <OvenWerks> Is that jack.log?
[01:16] <wonko> jackdbus.log
[01:17] <OvenWerks> right... thats what I meant :)
[01:19] <OvenWerks> Yes those look like alsa resets... the fact that jack doesn't seem to have actually restarted would indicate something seems to work better
[01:19] <OvenWerks> There does not even seem to be xruns in there
[01:21] <OvenWerks> or is there other stuff inbetween?
[01:21] <wonko> yeah, that's a grep result
[01:23] <wonko> https://paste.ubuntu.com/p/FdxP6kF6tf/
[01:23] <OvenWerks> it looks like jackdbus has been started almost 30 times but I get the idea you did not start jack that many times
[01:23] <wonko> 8:30 I came down and started messing with stuff, so that's probably what that was
[01:26] <OvenWerks> I don't see anything at 830
[01:26] <wonko> I didn't think to check ardour when dealing with monitor bullshit
[01:26] <OvenWerks> they go from 1540 to 2111
[01:26] <wonko> the second link
[01:27] <wonko> oh, HAHAHAHA
[01:27] <wonko> I never started the calf stuff
[01:27] <wonko> which is how the mic gets to ardour
[01:27] <wonko> I R SMRT
[01:28] <wonko> Oh, and FYI that Calf Analyzer crashing Carla issue has been fixed by whatever version of carla (and/or calf) is in 19.10
[01:38] <OvenWerks> I do wonder why you would put all of those things outside of ardour rather than using plugins
[01:38] <OvenWerks> (inside ardour)
[02:20] <wonko> Mostly I was just playing with the Carla rack. I'll probably put them back in ardour where I originally had them. Or even not at all because with the changes to the office there is practically no background noise being picked up by the mic. Even if it's a nice one like I now have.
[13:12] <wonko> OvenWerks: Ardour is still happy this morning so far, but I'm not counting that as a win just yet.
[13:19] <wonko> OvenWerks: Other interesting news, not a single xrun since last night when I was screwing with stuff
[15:30] <OvenWerks> wonko: it sounds like for you (until the next version of -controls comes out) qjackctl or jack_control might be the best way for your case.
[15:55] <wonko> Ok, I'll just get the script that sets everything up tuned for the new system. It was nice not having to use that but it'll do until controls is fixed.
[15:55] <wonko> Thanks for all your awesome work!
[15:57] <wonko> I'll try to take a look at sane bridge naming as well for you but no promises. This week is going to shit.
[16:33] <OvenWerks> wonko: there are some major upgrades for controls.next. It would be easier to add bridge naming as a part of that rather than hacking it into controls.current
[16:42] <wonko> What branch should I work against? Master?
[16:43] <OvenWerks> wonko: what I am saying is maybe leave it alone for now... unless you are willing to have a non-gui addition.
[16:48] <OvenWerks> autojack could be made to use a list of names and the gui could just pass them through. The gui would give it's own names if you add more bridges in the gui and of course if you reduce the number your names would be lost.
[17:32] <wonko> Yeah, that was my plan. I have zero interest in doing anything GUI related so I was going to fashion a new back end kinda like your described that was compatible with the existing GUI but then the GUI could be updated later to support it better. Using the existing bridge name generation. If you don't go change things in the config file for now it would appear to work exactly as it does currently.