Run two instances of Guitarix within Claudia… issues…

[wolftune]

Hi,

So I want to run two instances of Guitarix, one for each input and output channel in my system. Claudia seems fine running these, but when I stop and later restart the studio, it seems to not remember which instance with particular settings goes on which channel. It also creates an extra connection where one of the two instances is connected to both channels even though the other is correctly only connected to channel 2.

Is there any way to do this reliable? Perhaps I should try NSM?

[wolftune]

Ok, thanks

[wolftune]

Well, Guitarix runs more correctly with NSM but I get the same connection issue: both instances run, one is correct, but the other instead of having just one connection automatically gets two connections.

I'm pretty sure this is an with Guitarix because it always automatically connects to input 1 and stereo output, even if the session is saved with other connections. That should/could be fixed with an update to Guitarix. Before I report it, I'd like to make sure I'm testing the actually current release version (which I really want anyway, with the new built-in looper — I just added the package request, very surprised KXStudio is months out of date with Guitarix).

So my understanding is that Claudia is still needed for saving the overall JACK settings, even though NSM can save the connections (aside from when programs like Guitarix override it). So I need a Claudia session for the device settings and to run NSM also. I tried adding non-session-manager to Claudia but that was glitchier than just running it separately manually.

I wish Claudia could be told to automatically start the snd-aloop bridge and/or the ALSA MIDI bridge as desired when loading a studio (sometimes I want one or the other or both or neither, I just want it saved with Claudia and started with JACK)

I suppose what I really need is to learn scripting for real so that I can write an automatic script that will change my energy/CPU/network settings, start Claudia with the desired studio, start the bridges, start NSM, load the session, and then remove the extra Guitarix connection. Then I'd just run that script and be automatically set to go…

[tramp]

Check out the guitarix comandline options for the connection issue.
There is also a youtube video from studio32 out there which demonstrat the correct usage from guitarix under NSM control.
Can't give the link, i'm just on my mobile.

[wolftune]

Thanks! That's super helpful!!

[tramp]

'm pretty sure this is an with Guitarix because it always automatically connects to input 1 and stereo output, even if the session is saved with other connections. That should/could be fixed with an update to Guitarix. Before I report it, I'd like to make sure I'm testing the actually current release version (which I really want anyway, with the new built-in looper — I just added the package request, very surprised KXStudio is months out of date with Guitarix).

You better check out guitarix from git or wait for the next release to get the improuved looper, and some more nice, new plugs.

[wolftune]

I'm really hoping KXStudio updates guitarix ASAP, yeah, but I already got it to work! -J in the command stops auto-connect (at least when run within nsm) and jackpatch saves the settings I actually want, so I've got it working with the current version! Just don't have the new features… I also have a really frustrating color issue that makes it impossible to read preset names, and I should check if that's fixed with updates…

[tramp]

There are some known issues with qt based window managers, but unreadable preset names are new. For sure there is no difference in the color shema since a year or so. It is unlikely that this is fixed in newer releases. Maybe you report it to the guitarix bug tracker. Dont forget to provide all relevant information.

[wolftune]

I added a bug here https://sourceforge.net/p/guitarix/bugs/13/
There weren't many other bugs there, so I don't know if that's the normal bug tracker…

[tramp]

It is.
The other way is the developer mailing list.