The VI49 (and VI61 and VI25) has (have) some 25 configuration profiles, which we have support for at the protocol level, but the UI only operates in terms of configuration 1.
Probably the simplest thing to do is to pop up a modal dialog box to ask which configuration slot to use when loading or saving to the device.
For those wishing to look deeper into this, in class AlesisVSysexApplication, the saveDevice and loadDevice methods are where the configuration slot is currently set. Note that it is a 0-based index at the protocol level, but 1-based in terms of UI.
The VI49 (and VI61 and VI25) has (have) some 25 configuration profiles, which we have support for at the protocol level, but the UI only operates in terms of configuration 1.
Probably the simplest thing to do is to pop up a modal dialog box to ask which configuration slot to use when loading or saving to the device.
For those wishing to look deeper into this, in class
AlesisVSysexApplication, thesaveDeviceandloadDevicemethods are where the configuration slot is currently set. Note that it is a 0-based index at the protocol level, but 1-based in terms of UI.