The implementation may be a drag&drop in the global controller settings or any well done interface compliant with the actual editor ?
Usage : if we drag one channel to another in the name channels panel, editor would swap the 2 names AND apply this change to all MSGs in presets for all banks replacing old channel number by new one and vice-versa.
This could avoid hours of browsing through banks an presets with all the potential undetected errors.
A major feature for editor, may be more important than the fix in all the Jump to bank MSG after having moved a bank to another number because this error is easily visualy detected on the jump, but a midi channel error is more complex to figure (but this action is also a pain actually).
As a workaround, you might be able save the presets to a file, edit the file and replace the channel, and then load the file back in.
To change all channel 1’s to channel 2, you would replace: "channel": 1 with "channel": 2
Editing the file may be daunting if you are not familiar with yaml. Also helps to reformat the file (beautify) so it not just one long line … or use an editor that understands yaml.
NOTE: This is risky and could break if you make a mistake or channel is used for other reasons. This is free, untested advice . Beware. Keep a backup of the presets and be prepared to restore it.
True, but when I want to write real code I use visual studio
, here I try to keep focus on music (being also an old dev timer I take care to not start taking the bad road to dev hell).
There is often a fastidious work-around as for exemple for your request to add an offset value when sending CC Scroll counters values : you can add as many MSGs to increase the counter value by the offset, send it, then decrease back the countyer value … ![]()
Interesting. Thanks. This will not work in my case as the range of the counter is 1-6 (which I need to make the UI wrap around to the limited value). I just tested and you cannot increment the counter value beyond the range of the counter (if wraparound is off)? I think if you try to go out of range it skips the update.