=== TheMaster is now known as Unit193 [19:45] test [19:45] how are you [19:45] what is this [19:45] sudo [19:45] sudo -s [19:45] whoami [22:49] Am I understanding it right that US is set up to have a JACK pulseaudio bridge by default? [22:58] yes and no... it depends on what you mean by that. right now if jack is started on a stock US system, there will be a PA-jack bridge. [22:59] if the new controls is put in place, normal operation would see jack run from session start [22:59] The new controls does allow PA alone, PA-jack and Jack alone operation [23:00] it does not really account for jack and PA operation at the same time but with different devices and no connection. [23:01] Also, when in jack alone mode, PA continues to run with it's dummy backend. [23:03] I have found that if PA runs with the dummy backend, the CPU used is not noticable... even on an old P4. (I tried it on ano older machine as well, can't remember if it was 333Mhz or 800Mhz but again no noticable difference) [23:06] I ask because I have problems consistently getting the same behavior...sometimes I start JACK and the sink shows up and is found by things like OBS, others, not [23:06] unfortunately I have a less-than-basic understanding of JACK, etc. so my ability to troubleshoot is limited to say the least [23:10] SlidingHorn: I think you are saying that when the PA-jack bridge is in use that an application using pulse may use the jacksink or it may use another device which pulse sees. [23:10] Is that correct? [23:11] correct, however, I've never manually started the PA-jack bridge, and sometimes it appears to be in use, others, it's not. I don't know how to get a consistent result [23:12] Both Cadence and US-controls fix this problem by not letting Pulse see any other device besides Jacksink. [23:14] if you use pavucontrol you can simulate this by going to the Configuration tab and turning all device profiles to "Off" [23:15] That makes sense, as when I have JACK running, if I want to - say watch YouTube videos, I have to manually go into pavucontrol and select JACK as the output for each specific playback appliation (e.g. firefox) [23:15] However, any time a device is introduced after boot, like a USB device plugged in, that device will show up even though it had a profile set to Off. [23:15] however, sometimes, it won't even show up on the pavucontrol dropdown [23:16] that I don't know [23:17] I would first look to see if it detects jack and makes jack ports, or if it asks pulse/jack for a raw alsa device and fails. [23:17] or maybe chooses a device not being used by anything [23:18] How would I do that? [23:18] I think the best trouble shooting tool is: [23:19] cd /tmp && wget http://jackaudio.org/downloads/adevices.sh && bash ./adevices.sh [23:19] (all one line [23:19] run that while you have an app running that does not show up in either jack or pulse [23:21] That will show each device with either the word "closed" or a line "used by: jackdbus (PID 1634)" [23:21] of course if the device is used by something other than jack it would show that too. [23:23] SlidingHorn: once yu have run that line once, you can cp /tmp/adevices.sh [23:23] to your home directory and run it idrectly from there to use it a second time [23:24] (rather than having it download each time ;) [23:29] Should I be using something like Cadence instead? It seems like qjackctl is more for people who have a strong handle on this kind of thing, lol [23:31] I certainly prefer a system where jackdbus is the audio back end and pulse just acts as a desktop front end [23:32] both Cadence and US-controls (next) do this. [23:32] If that works for you I would suggest using it. [23:33] One thing I was noticing about US-controls was that there's no reporting as to what's happening (e.g. doesn't say whether JACK successfully started, if there are xruns, etc) [23:49] oh wow...just installed cadence and using it with catia is *so* much simpler [23:49] Ya those things haven't been added yet.