NSM support seems to not work at all.

[Houston4444]

Hello. I tried rakarrack-plus NSM support, but the main NSM goal seems to not work at all: save the rakarrack-plus NSM client doesn't saves anything !

• add executable rakarrack-plus to RaySession or NSM
• move any slider in rakarrack-plus
• save rakarrack-plus client
• stop rakarrack-plus client
• resume rakarrack-plus client

and changes are forgotten :(

Cheers Mathieu

[Stazed]

The way rakarrack-plus, is designed to be used does not fit the normal NSM approach. NSM presumes a single saved state, but r-plus is more designed for live performance, and thus no single state would really be wanted. The user would select a preset from a program provided bank, or user defined bank, likely changing for each song. Even changes made during the performance would not likely want to be saved, since it would be done for the performance, such as volume, tempo, etc.

If you did want to save any changes, then they would need to be saved to a user bank manually. The user banks are global for all instances of r-plus and thus are not exclusive to each NSM session. Or you can manually export the preset to a single file (text) for sharing (Export from the main window).

What you can save in NSM is the individual instance Settings/Preferences. Also the last selected preset chosen from a preset bank will also be saved for re-load on the next start. In addition, the gui show/hide state is saved.

I realize that this usage of NSM is not the way it usually works, but using r-plus as a single state rack does not fit into the way I want things to work. If you do want to use it that way, then you need to manually save the preset state to a user bank, and save NSM with that preset selected from the bank.

Cheers, back at you... Stazed

[Houston4444]

Ok, thanks for your answer. I understand, but I am still septic. I am pretty sure 90 % users don't knowing r-plus will try it, make a sound, save and close the session, and when they will load the session, they will see their changes forgotten, and finally say: I can't trust this soft, I don't use it.

I perfectly understand that if user has mapped parameters (with MIDI or OSC), and theses parameters moves during a song, then we don't need to restore the value they had at the the end of the song...

There is certainly a good compromise. The first idea coming here would be to provide an information dialog (with a "not again" checkbox) to inform user of the NSM r-plus behavior. This dialog would be displayed when r-plus is started from NSM without written config file. What do you think about ?

Cheers Mathieu

[Stazed]

The information dialog would certainly help for new users. Even those not using NSM. But my time for this project is limited and writing user documentation is about the last thing I want to do when I have time. I personally will probably never do this, and the 90% who abandon this project, I am o.k. with.

If anyone else wants to improve the documentation, or add a startup dialog, I would gladly accept a PR.

Otherwise, if a user were to do a tiny bit of investigating and perhaps see this open issue, then they could find the answer without any further effort.

Lets leave this issue open just in case...

Cheers Stazed

[Stazed]

As a compromise, a check box was added in Settings/Preferences/Misc: NSM single state. When in an NSM session you can now check the box to use Rakarrack-plus as a single state rack. I.E. all changes to the main window rack will be saved on NSM save, and loaded on next start. This means any MIDI changes or live performance changes will be saved. The setting is disabled by default, but can be set per individual instance.

@Houston4444 FYI.

Cheers Stazed