Something strange happened today.
Together with my friend, LuLoop, I tried to sync two Sub37, to play sequences in sync. We connected the first Sub’s MIDI Out to the second Sub’s MIDI IN.
The first Sub had Firmware 1.1.14 the second still had the 1.1.13.
When changing a preset on the first Sub, the current preset of the second Sub had been overwritten by the sound of the first.
It seems, the new firmware sends the sound’s SysEx with every program change.
We did the other way: Sub 2 MIDI OUT to Sub 1 MIDI IN. The old firmware does not send SysEx while changing the program.
In MIDI OX all the SysEx data was also visible when changing a preset with the new firmware.
Gil, Amos ?
cheers Bernard
P.S. thanks to LuLoop for using his time.
Looking forwards with warm regards Luloop
Thanks to my friend Bernard.
Both versions send out sysex on preset change, if the Sub 37 thinks that the Editor is connected.
It might be the case that this sysex is sent out both the USB and DIN MIDI outputs, where ideally it should only send sysex to the output which is connected to the editor. I’ll look at this.
Out of curiosity, did the sysex only overwrite the edit buffer, or did it really replace a preset in persistent memory on the other Sub 37?
Yes, the preset will be overwritten immediately, not only the buffer. I think, I’ve read this in a manual too, that an incoming SysEx dump will overwrite the preset directly.
I think the best would be, to NOT send the SysEx usually with every program change.
If the editor receives a program change it could send an dump request to the Sub37.
With an other Sub connected instead of the editor, nothing would be send and so nothing can be overwritten.