I am trying to create a preset for my Emu Morpheus.
My e1 mkII is connected via USB to the computer and the web editor can see it.
I have created a preset and saved it to My Presets, and have selected it for editing in the web editor.
I have selected ‘edit device’ in the web editor.
I have selected the ‘mapping’ tab in the web editor.
I have a DIN5 cable directly from the MIDI out on my Emu Morpheus into the MIDI In 1 DIN5 socket on the back of the e1 mkII.
I have selected ‘start listening…’
I initiate a patch dump on the Emu Morpheus:
I can see the MIDI IN 1, USB DEVICE and USB HOST indicators light up on the e1 mkII.
Nothing shows up in the web editor - still listening…
What am I doing wrong?
There is more than one listening function in the editor. Can you take a snapshot of the page where you initiate the listening?
Other possibility: you need to configure at least the response header of the Sysex in the editor so the E1 knows what message to listen to. The E1 will filter out all other SysEx responses.
Here is where I’m trying to MIDI listen from.
I’m intrigued by your comment about configuring the response header.
The Morpheus sysex documentation is good, but maybe I’m not reading it correctly. The Morpheus sysex message header encapsulates hex and MSB / LSB values which vary depending on what the message type is. Which message type should I choose to configure against?
Also, how do I configure the default request and response syntax to include nibbelised values? I only see two options - ‘Constant byte’ and ‘LUA function’.
Perhaps get a look at my tutorial on patch parsing. See if this helps explain what you look for.
For testing and initial sanity checks, I configure the response header to the minimal number of bytes possible.
For example, the Lexicon PCM 80 sysex starts with
F0, 06, 07, channel info, response type, …
My response header for my editor only has 06 07 in it.
1 Like
Thanks for the replies, I have given up on the ‘MIDI listen’ feature for now and am hard-coding the sysex the old fashioned way. Learning a lot in the process.
For example, did you know that to traverse the Z-Plane filter types in the Emu Morpheus, one has to pass through a non-sequential 14-bit nibbilised unique ID for each increment? Fascinating…