unable to save LADISH session properly

[infamedavid]

I m using Claudia as a Graphical User Interface to LADISH. and I cant find any way to it remember the I/O connections when I load a studio

[Skrylar]

Don't LASH and LADISH require applications to explicitly support them?

[infamedavid]

I m not sure, but reading the xml session file it look very generic, it take the name of the jack ports and them connections and simply reconnect when you load your session , the Core Audio and Audio 16 work perfect with Claudia.
000.zip

[Skrylar]

the Core Audio and Audio 16 work perfect with Claudia.

Are these using patched RtAudio or stock RtAudio going over ALSA?

[infamedavid]

Are these using patched RtAudio or stock RtAudio going over ALSA?

I m not sure what do you mean, using Jack as audio driver and whichever audio device

[Skrylar]

Official builds don't support setting the Audio modules to JACK.

[infamedavid]

it is confused to me, I think I m using jack and an official build (I compile it from the source) but now I m not sure (really) when I use Jack as Driver it is not jack ?(it is a pseudo jack like Pulse Jack or something?)

[Skrylar]

RtAudio itself supports JACK, and source builds can be made to support it. Rack doesn't do anything with this extra information though, which is why I had to write this module. Some people were distributing custom builds with this configuration ("patched RtAudio") but Vortico doesn't support it and they're non-standard.

It's interesting that lash/ladish work with it though.

[samb400]

Correct me if I'm wrong, but I believe he is referring to the fact that since the module's port names change in a new patch, it requires users (including myself) to reconnect ports in Claudia/Catia/Gladish every time we change patches or load a new one, which often is...well...often. It's only a minor inconvenience, but it would be great if there was an option to keep port names consistent. Unless there is something I am missing.

[infamedavid]

actually I m refering to the ladish session, you can keep the names of the inputs and outputs channels in a new patch renaming the channels of the skjack modules and saving as template file
(saving a file named "template.vcv" in you rack folder) in other sense could no be useful since a new skjack module in the patch will create duplicated names

[infamedavid]

it is perhaps a issue no directly related with the Skjack or it is a combination off issues between the Skjack and Claudia I m using Carla (that include a patchbay) and it can remind the Skjack connections of the session