View Single Post
Old 1st July 2020
Lives for gear
Rob Ocelot's Avatar

It would be unusual for a company to downgrade or remove SYSEX functionality from a product. What's more likely is the manual is referencing an earlier or later ROM version than your Proteus 1.

I don't own a Proteus but from what I can find there was an initial version of the Proteus 1 that had no other name. This was followed by two other Proteus 1 modules ('XR', and 'Plus Orchestral') and the original module was rebadged as 'Pop/Rock' so as not to confuse customers. My guess is each of those units were given different SYSEX Product ID bytes in case a customer had two of the modules on one MIDI chain and wanted to send sysex specifically to one. Normally this kind of situation would be handled by giving the modules different Device ID's but that's something the customer would have to dive into the menus and set up manually. I wonder if E/MU tried to make the process simpler for non-techy musicians so it would work right out of the box. It's possible Product ID '04' was retired and the three named modules were given ID's 05-07.

So I see a couple of scenarios here...

*You have one of the later named modules that won't respond to ID 04
*You have an original module that was upgraded to be an XR version internally

What issues are you having with MIDIOX? I've only ever used it to send SYSEX files back and forth... but as far as I know there's no way to send raw SYSEX commends directly. You'd have to write the SYSEX commands to a text file, rename the file to be .syx and then send it to the synth -- and it would be really just for testing purposes.

One other thing springs to mind is that some of synths take extra time to decode SYSEX and that could make real time control laggy enough to be frustrating in practical use. You'd think a circa 1990 module could handle it but I've been surprised on a couple of occasions.