Saving in the DSSI protocol
Posted: Sun Feb 17, 2019 5:09 pm
Tim,
I remember briefly a conversation we had here about the lack of "saving" presets in DSSI, and the reference was using the LS16 gui as a linuxsampler dssi plugin.
I will admit i still don't understand this, and ask if you explain a little more.
Test case.
I open a synth track for DSSI LS16, and the track appears. I then have 2 gui options. LS16, which enables me to load a gig file per channel, for 16 channels. I do that. Then, because LS16 has no visible function to save/recall a preset, i close LS16, and open the Muse generic gui, which has the save/recall preset function. I save the preset in the generic gui, and as i've opened Muse3 from a terminal, i can see the gigs i chose have been loaded.
I then close the project without saving it, and open Muse again with a new project. I create a DSSI track with LS16, but use the generic gui, and attempt to load the preset i created.
Nothing.
The preset is there in my custom muse-preset directory, but it won't load. Is this a limitation in the DSSI protocol, or something to do with Muse not saving DSSI presets?
I intend to work with channels per instrument, not instrument maps as Program Changes. This is so i can "blend" different articulations together if required. (I've been working this way for many years)
The intent here is to create presets for every gig instrument i have in my audio samples box, then load and use only those i require for a particular project.
As an aside to this, but part of the workflow described above, can i submit a feature request for Track Templates.
Each track and all it's settings are saved as a preset which can be named, and groups of user selected tracks can be saved as well.
An example is a plugin track containing my instrument (DSSI/LV2) plus any midi tracks that send data to that track.
1st-violins instrument plus 16 midi tracks, all routed and saved as a "1st-violin" preset, which i can load in any project easily and quickly.
Thanks for listening,
Alex.
I remember briefly a conversation we had here about the lack of "saving" presets in DSSI, and the reference was using the LS16 gui as a linuxsampler dssi plugin.
I will admit i still don't understand this, and ask if you explain a little more.
Test case.
I open a synth track for DSSI LS16, and the track appears. I then have 2 gui options. LS16, which enables me to load a gig file per channel, for 16 channels. I do that. Then, because LS16 has no visible function to save/recall a preset, i close LS16, and open the Muse generic gui, which has the save/recall preset function. I save the preset in the generic gui, and as i've opened Muse3 from a terminal, i can see the gigs i chose have been loaded.
I then close the project without saving it, and open Muse again with a new project. I create a DSSI track with LS16, but use the generic gui, and attempt to load the preset i created.
Nothing.
The preset is there in my custom muse-preset directory, but it won't load. Is this a limitation in the DSSI protocol, or something to do with Muse not saving DSSI presets?
I intend to work with channels per instrument, not instrument maps as Program Changes. This is so i can "blend" different articulations together if required. (I've been working this way for many years)
The intent here is to create presets for every gig instrument i have in my audio samples box, then load and use only those i require for a particular project.
As an aside to this, but part of the workflow described above, can i submit a feature request for Track Templates.
Each track and all it's settings are saved as a preset which can be named, and groups of user selected tracks can be saved as well.
An example is a plugin track containing my instrument (DSSI/LV2) plus any midi tracks that send data to that track.
1st-violins instrument plus 16 midi tracks, all routed and saved as a "1st-violin" preset, which i can load in any project easily and quickly.
Thanks for listening,
Alex.