[15:42] <OvenWerks> Eickmeyer: FYI (in case you didn't already know) systemctl has not only --system and --user but also --global
[15:43] <Eickmeyer> OvenWerks: Yep.
[15:43] <OvenWerks> Eickmeyer: sudo systemctl --user does not work it has to be done as the user and it adds or takes away files in .config/systemd/user
[15:44] <OvenWerks> --global does files in /etc/systemd/user
[15:45] <OvenWerks> It seems we can switch between pulse/jack and pipewire without a reboot.
[15:45] <Eickmeyer> --global affects all users.
[15:46] <OvenWerks> yeah, so I am wondering which I should use in controls
[15:47] <Eickmeyer> .config/systemd/user trumps /etc/systemd/user in the path, so I'd use --user.
[15:47] <OvenWerks> audio is kind of a global service, only one user can use it at a time.
[15:47] <Eickmeyer> And that's true too.
[15:47] <Eickmeyer> You can't switch users, but logging out and logging in as a different user with a different config can be a thing.
[15:48] <OvenWerks> but if two people use a machine they may both want different setups
[15:49] <Eickmeyer> Right. I'd consider university audio workstations.
[15:51] <OvenWerks> ok, I will set up for --user, it seems to work.
[15:53] <OvenWerks> Eickmeyer: it seems that with pipewire, I don't really need autojack, everything can be set up by the gui anyway.
[15:54] <Eickmeyer> OvenWerks: Right, it seems to "just work", in theory.
[15:54] <OvenWerks> Autojack just needs to "stay out of the way" as in not try to restart pulse
[16:00] <Eickmeyer> Patchance was accepted into Lunar yesterday, building right now in backports for Jammy and Kinetic.
[16:06] <OvenWerks> I guess it won't just show up in an update, so when it makes it I will need to install
[16:15] <Eickmeyer> No, it won't show up because it would have to be added for a meta first.
[16:17] <OvenWerks> If it works well, I will change the Carla button to connections or patch bay or something and have it launch Patchance, catia, patchage or Carla depending on what it finds
[18:17] <OvenWerks> Eickmeyer: just installed Patchance, I like what it does with the Midi-Bridge, nice short names. There is a bug with port names for ports over 9 (or one could argue port names under 10) https://i.imgur.com/JNne4Wt.png
[18:19] <ErichEickmeyer[m> Probably a bug in https://github.com/Houston4444/HoustonPatchbay then.
[18:28] <OvenWerks> Is it the same project? Or a wrapper?
[18:29] <Eickmeyer> So, Patchance (and RaySession) use HoustonPatchbay as the patchbay.
[18:30] <Eickmeyer> It's basically a static lib in both projects, OvenWerks.
[18:33] <OvenWerks> It is interesting to see how different people interperate the names for a patch bay. I am looking at 4 of them: patchance, Carla, Qjackctl, and qpwgraph
[18:33] <OvenWerks> The last two are both by RNC
[18:34] <Eickmeyer> Carla's patchbay comes from Catia. Qpwgraph's patchbay comes from Qjackctl.
[18:34] <OvenWerks> Carla's patchbay is better than catia which is broken
[18:35] <OvenWerks> But I would guess it uses a lot of the same code
[18:35] <OvenWerks> but qjackctl and qpwgraph name the ports (or at least the port boxes) differently
[18:35] <Eickmeyer> Considering it's the same author, I'd guarantee it.
[18:37] <OvenWerks> I would like to see him move some of the fixes in Carla over to Catia.
[18:38] <Eickmeyer> Are you sure you're not mixing up Catia with Claudia? Because Claudia is broken.
[18:39] <OvenWerks> Catia which was broken out into it's own project shows two of each client (or maybe three?)
[18:39] <Eickmeyer> Oh, I didn't know Catia was broken out of Cadence.
[18:39] <OvenWerks> It has one that shows no ports but is just the client
[18:40] <OvenWerks> So it shows controls for example even though controls has no ports
[18:42] <OvenWerks> qjackctl and Carla both show MidiBridge ports as the full long name. In both cases the "box" name is part of the port name (or the client name)
[18:43] <OvenWerks> Actually, patchance does too, but also uses an icon for the program if available and stock icons for devices
[18:44] <OvenWerks> I think the Icons are a nice touch and it helps my eyes pick out clients easier
[18:55] <OvenWerks> qpwgraph, even being similar looking to qjackctl, uses the device description for the box name and then gives each port the full port name. So for example, I have my audiofire12 set so in jack_lsp it is system:playback_aux* and most of these graph applications show it as such but qpwgraph shows the box name as AudioFire12 Pro
[19:08] <OvenWerks> Eickmeyer: Onr thing I don't like about all of them when running pipewire is that when opening pavucontrol or even clicking on the plasma audio widget in the taskbar is that they show up as clients connected to many things, sometimes many clients. It makes the graph very hard to work with. It shows up in jack_lsp too, so this is a PW bug (feature?)
[19:10] <Eickmeyer> I'm not sure. I think in those cases a patchbay becomes the source of truth over pavucontrol.
[19:12] <OvenWerks> I suspect pavu control or plasma pa uses the signals for metering but I think they should be counted as special and hidden because the user doesn't gain anything by changing the connections which will in any case get recreated with each change anyway.