[07:41] <OvenWerks> Eickmeyer: are they all one type of cpu or graphics card? That would be my first guess. Does it affect Studio on top of other flavour? I don't have 1810 installed, just 1804 and 1904
[14:21] <Eickmeyer> OvenWerks: I don't know. I was mostly wondering if you had an opinion/guess.
[14:22] <Eickmeyer> Also, I don't know if they even bother to update before reporting the issue.
[15:28] <OvenWerks> Threading in python is a pain... so I will opt out..
[16:17] <Eickmeyer> OvenWerks: ??
[16:23] <OvenWerks> Eickmeyer: in -controls I wanted to check if jack is alive in a second thread to not slow down the GUI... but Then I have to learn signals.
[16:24] <Eickmeyer> Yikes.
[16:24] <OvenWerks> Eickmeyer: I think instead I can use a gui timer and only look for jack when it is supposed to be running anyway.
[16:29] <OvenWerks> I tried creating a jack client... this does work ok when jack is running, but throws too many errors that are hard to catch/take time. There doesn't seem to be a call that just looks for jack status besides jack_control status, but that can do bad things too.
[16:30] <OvenWerks> It seems we end up calling jack_control staus at about the same time we do a killall jackdbus... which is bad. If it was after, dbus would just start a new one which is ok.
[16:43] <Eickmeyer> Makes me wonder how qjackctl does it, or Cadence for that matter.
[18:59]  * OvenWerks is looking through the libjack api...