search

rncbc / qjackctl

QjackCtl - JACK Audio Connection Kit Qt GUI Interface
https://qjackctl.sourceforge.io
GNU General Public License v2.0
186 stars 42 forks source link

Jack MIDI connections don't show with client/port aliases #196

Closed agraef closed 1 year ago

agraef commented 1 year ago

Hi Rui, this is with the very latest qjackctl from HEAD, and seems to be the same no matter whether using Jack1 or Jack2.

With JACK client/port aliases set to "First" or "Second" on the Display tab of the Setup dialog, like this: image

The aliases are shown alright, but the connections aren't. (This only affects the connection window, which I prefer; the graph window is alright.) image

If I add a new connection, it sometimes briefly flashes into existence and then disappears again. Changing back the JACK client/port aliases option to "Default" all the invisible connections are shown alright: image

It would be really nice if you could fix this, because I like the tidier view provided, in particular, by the "Second" option.

(BTW, can you elaborate how the "First" and "Second" views are constructed? I couldn't find any corresponding information on your website.)

agraef commented 1 year ago

I still need to figure out a way to ensure that the connections view doesn't stomp on its own edits when the server is restarted, though.

Should be fixed now in https://github.com/rncbc/qjackctl/pull/199/commits/2a78048af6c374714dd0c9551410099eaf3488c0. Tested with both Jack1 and Jack2. I still need to test with Pipewire, which I'll do now.

rncbc commented 1 year ago

squashed and merged PR #199 in qjackctl v0.9.11.16git.fcf58e

again, thanks a lot

agraef commented 1 year ago

Thanks a bunch, Rui. :) Pipewire test (with pipewire-jack) is all good as well. Edits survive logging out and back in again, and even a reboot. In fact, they're so sticky now that it seems almost impossible to get rid of them. ;-) (Apart from slashing the aliases section of .config/rncbc.org/QjackCtl.conf, which is good enough for me.)