Hey there #LinuxAudio #Pipewire #ProAudio #Production peeps. Can anyone point me in the right direction to get #qpwgraph to hold on to the names I give my hardware interface ports please?

I can rename them ok, but when I close #Reaper they just go back to 'Capture_AUX0' (etc). I've saved the patchbay but when I reload Reaper they stay default.

Confident that this is user error as this seems like basic functionality, just not sure where to look (is it something to do with 'exclusive'?)

I narrowed it down to the qpwgraph.conf file in /.config/rncbc.org/ backed that up and with a combination of editing stuff, quitting #qpwgraph and restarting it again I can see my edits now being written to the file and they seem to be sticking.

Seems a bit odd to have to quit the app to make it write the edits to the file, but if it's working I'll not complain too loudly about a little ghost in the machine.

@thechildofroth I'm not completely sure this is a user error.

There is a lot of things going on behind the scenes, from what you see in qpwgraph.

I would suggest you reach out to the maintainer, and ask if this is related to qpwgraph, the jack api (Reaper uses pipewire-jack), wireplumper or pipewire. Yep, there is a lot going on :D

There is an e-mail on the Github:

https://github.com/rncbc/qpwgraph

You can also check the Issues tab to see if others have experienced the same issue.

GitHub - rncbc/qpwgraph: qpwgraph - A PipeWire Graph Qt GUI Interface

qpwgraph - A PipeWire Graph Qt GUI Interface. Contribute to rncbc/qpwgraph development by creating an account on GitHub.

GitHub

@mosgaard Thanks, I'll try that.

I just don't understand the point of being able to rename the nodes (as detailed in the user guide, which highlights both f2 and double click will enable you to do so) but for that naming not to 'stick'

I should note it does remember my midi input port naming (but not the outputs?!)

@thechildofroth It does sound strange, I hope you find an answer!