Jan, good to know. BTW, I'm not sure if you saw my post somewhere (maybe a year ago? in one of the Yahoo! forums or in your bug-reporting forum) that I finally figured one of the causes a crash I experienced with Prodatum's whenever I tried to test drive it over the years. IIRC it occurs when there is data in a preset pointing to a non-existing resource--e.g., a preset that uses a ROM that is no longer installed-- (not instld). I don't remember if its just some bogus data that triggers Prodatum's crash/lockup. If you are interested, I can try to find where I posted the details.
BTW, one of the tools I originally had in mind for Syxer was a data checker to quickly identify erroneous data in a bank file. Some day . . . .
Royce, good to hear from you on this. Thanks for the specific sysex code. If Paul goes for that workaround, it should be helpful. I assume that dropping the level to -96db should work and that for developing presets, the polyphony issue (voice usage) should not be a problem.
Thinking about it, in a real-time performance to avoid maxing out polyphony, swapping the ROM Instrument to 000:None might give an advantage.
Also, if Paul (or anyone else) creates original presets from a template using 0db for all layers (AMPLIFIER Volume), there's no need to remember what to reset it to after dropping it to -96db to simulate layer solo: off.
As you pointed out, the original level would have to restored. And I just checked a few factory presets--for example: L1=+7db, L2=+10db,L3=-10db, L4=+0db.
It's nice to have the flexibility of all these workarounds and a community of users and software developers to contribute to the knowledge base.
As much as I like the full range of features editors have (like Jan's graphic envelope editors!!!), MIDI-OX is still a reliable and convenient tool to small tasks like sysex stuff.
Paul, I thought of another option (if you are still looking for workarounds)--using embedded sysex commands in the on-board sequencer. For example, I have some dial-able sysex switches to turn Remote Control Mode on and off in out-of-the-way pattern slots--125^7 is RemoteControlOFF, 126^7 is RemoteControlON, etc.
You could do something similar in combination with one (or more) of the sysex command workarounds. Such as: 110^7 as L1 L2 L3 L4 - 0db, 111^7 as L1 - 0db etc. for the whole set of permutations. If this would work for you, you would need software that can save the sysex commands in *.mid files and upload them into the sequencer via e-loader.
For my embedded sysex patterns I used early versions of Cakewalk software, but any tool that allows for editing of sysex commands and saving them within a standard midi file should work.
If you don't have that ability (or would prefer it to be worked out and tested), in a couple of days I should have some time to create some test-of-concept embedded sysex *.mid files.
OH one more thing--Jan, does Prodatum still load a specific multisetup when starting? As I discovered and mentioned previously, Command Stations and the P2500 seem to save what I call "last-state" data, so when Prodatum automatically loads [used to load] a specific multisetup, the last-state data is overwritten.
Apologies if I tested this and found out the answer myself in 2.0 (or 2.1 or was it 2.2); I thought it'd be quicker to just ask you as opposed to trying to do another round of tests--esp. since I moved my P2500 off of the PC that I used to test Prodatum.
Steve