Message
RE: Saving/loading Patterns -Eloader *not a valid midi file error* trying to load
2014-03-24 by <smw-mail@...>
One time I used E-Mu remote control to automate randomizing and saving a whole bank of 128 presets. I am thinking if you had a template or a default in slot 000 of any given back, you could write a remote control sysex script to save that to the remaining 127 slots in that bank. If you are adventurous and want to give that a try, I highly reccomend using an offbeat sysex ID that you would never use for anything else. And then change the sysex ID back to 0 when you are done. One of the reasons I never posted the script to randomize a whole back is that I didn't want the responsibility of someone accidentally wioing out a whole bank of prized presets.
If you have never developed an E-Mu remote control sysex script, basically it involves opening remote control mode, simulating keypresses with sysex, and then closing remote control. To do something like copy preset 000 to the remaining 127 slots in a bank (assuming it can be done), you would need to have the front panel in the right spot (at preset 000) before running the script. If you are not at the right spot, you could wipe out any consecutive set 127 of presets (for example, 032^1 to 031^2). I used pre-Sonar Cakewalk software to "play" as a sequence a series of remote control sysex comands. I think I have some demos of non-destructive remote control sysex scripts in the files section.
As for the problem with non-loadable files, that is a mystery. Other than analyzing a file byte at a ti9me, I am not sure how to sort it out. Is it possible that your midi interface, routing, or setup is introducing some stray bytes?
Steve