Studio Electronics SE-3X SySex

Instruments
21

Ha, there might be another explanation: sometimes synths have the ability to spontaneously send the sysex dump, when they receive a program change. It might be this can be set up in the global settings, but I suspect one can request such behaviour as well… via Sysex.
Do check if the editor doesn’t send out some kind of request at the start of a session…

22

I’m now certain the editor is only sending a sysEx patch dump when changing patches if it is a patch with unsaved edits. These are highlighted on the editor and it only occurs the first time I select an edited patch. Once it is sent when I go back to that patch it is not sent again - because it is already in the synths memory.

The editor also sends a patch sysEx when I ask it to load a patch from the patch folder. Or when I upload a whole bank it sends a huge sysEx message with all the patches of that bank.

I will investigate if there is an initial message on startup. But I haven’t seen one so far.

1 Like
23

When I first started up my editor I had to request all patches from the atc-x, there was a “get” for that. Might be that SE synths can only get and be send the whole banks

24

looked again at the manual, and for the ATC-X at least you have to right click on the patch number and then have the option to request. Hopefully the same for the SE-3Xß

image
image307×265 35.8 KB

1 Like
25

I checked the sysex comms on my SE02:
After the header

image
image322×320 1.4 KB

comes the command or the response:

  • command 11h is met by a 12h response

And there are 4 requests I send out

   midi.sendSysex (devPort, {0x41,  0x10, 0x00, 0x00, 0x00, 0x44, 0x11, 0x05, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x40, 0x3B})
   midi.sendSysex (devPort, {0x41,  0x10, 0x00, 0x00, 0x00, 0x44, 0x11, 0x05, 0x00, 0x00, 0x40, 0x00, 0x00, 0x00, 0x40, 0x7B})
   midi.sendSysex (devPort, {0x41,  0x10, 0x00, 0x00, 0x00, 0x44, 0x11, 0x05, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x40, 0x3A})
   midi.sendSysex (devPort, {0x41,  0x10, 0x00, 0x00, 0x00, 0x44, 0x11, 0x05, 0x00, 0x01, 0x40, 0x00, 0x00, 0x00, 0x30, 0x0A})

I’ll need to do some experiments to find out what each of these actually do…

1 Like
26

@markus.schloesser Thanks for looking that up. The SE-3X editor is similar. However, the option to receive is not really about sending a request message to the SE-3X. Its actually a request to the user to go and press buttons on the SE-3X :slight_smile: For example,

image
image534×252 63.5 KB

This further confirms my suspicion that the editor is not really doing two-way SysEx patch communication with the Synth. You can use the editor to load patches from your PC to the Synth; you can unload patches from the editor to your PC; and you can push buttons on the SE-3X to send a patch from the synth to the editor. But I’m pretty sure that you can’t send a request message to the SE-3X to do that last function (otherwise the editor would do that and wouldn’t make you physically do it on the SE-3X itself).

In a perverse way this is comforting because I was losing my mind trying to find the SysEx request message. :confused:

@NewIgnis thanks for SE-02 information. I had been studying that too over the last week. I have spent hours trying various versions of that request message using the SE-3X header. But to no avail.

Anyway, I’m ready to move on. I will just use the snapshot tool to store the settings for my go-to patches on the SE-3X. Question: Is there a way to share those snapshots in addition to the E1 preset?

3 Likes