[16:44] <barrymac[m]> Hi All, hope everyone is well! 
[16:46] <barrymac[m]> I'm having trouble with starting any jack application, all of them hang on startup. Jack_control also hangs if you try to get status and will only list the dummy driver 
[16:48] <barrymac[m]> Studio Controls also isn't able to list status, and stays with message "configuring ..."   next to the jack status in the UI 
[16:49] <barrymac[m]> the only messages I get from jackdbus.log are :  " ERROR: Invalid container address 'driver':'device':'(null)' supplied to method 'SetParameterValue'" 
[18:00] <Eickmeyer[m]> barrymac: Clicking "Stop JACK" should get everything reset back to normal PulseAudio, then double-check your configuration in the rest of the tabs.
[20:39] <OvenWerks> barrymac[m]: which flavor are you using? Dummy only sounds like pipewire is running as jack. It shouold appear to you jack is already running
[20:40] <OvenWerks> barrymac[m]: try jack_lsp, if it show a pile of port, just pretend jack is running.
[20:43] <OvenWerks> barrymac[m]: what is happening, is that pipewire has rplaced the pointer to jacklib with their own version. There is a file that can be removed so the system will see the jackdbus version of jacklib, but be warned ahead of time. If you run jackd the jack-source/sink module for pulseaudio will not load.
[20:45] <OvenWerks> this is because if you run pactl info you will probably see: Server Name: PulseAudio (on PipeWire 0.3.59)
[20:47] <OvenWerks> barrymac[m]: honestly, if your audio device(s) work properly with pipewire, I would just use pipewire. Do not install studio-controls if you are using pipewire. Wait for version 3.* of studio-controls which will understand pipewire.