MIDI-OX User Forum - Print Page


    
      
        MIDI-OX User Forum
        (http://www.midiox.com/cgi-bin/yabb/YaBB.pl)
      

        MIDI-OX >> Mapping Questions >> Send Sysex Confusion
        
(Message started by: motorbikematt on Mar 12^th, 2023, 11:10pm)

Title: Send Sysex Confusion
Post by motorbikematt on Mar 12^th, 2023, 11:10pm

Greetings Earthlings,

I might need some hand-holding or education here. First, some background:

I have a eurorack reverb module with digital pots, buttons, and an undocumented built-in USB MIDI controller on the back. All the pots and buttons send System Exclusive events that MIDI-OX can read just fine. For example, pressing a trigger button on the module produces the following message in the Monitor Input:

Code:

TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
000C0041 Sta -- F0 Buffer: 11 Bytes System Exclusive
SYSX: F0 00 01 55 15 02 10 53 00 00 F7
000C0091 Sta -- F0 Buffer: 11 Bytes System Exclusive
SYSX: F0 00 01 55 15 02 10 53 00 01 F7

This will also illuminate the device's 'SX' Input Port light in the MIDI Port Activity monitor. Lastly, I am able to also Receive Manual Dump of the same HEX codes in the SysEx View & Scratchpad tool. I believe I have everything configured properly, however, I am seeing a problem in the next step that I do not understand.

From the SysEx View & Scratchpad, when I right-click hit the Display Window and Send Sysex of the same HEX code that I just captured, the Monitor - Output displays appears to replay the proper info:

Code:

TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
00387080 MOX Sta F0 Buffer: 11 Bytes System Exclusive
SYSX: F0 00 01 55 15 02 10 53 00 00 F7
00387111 MOX Sta F0 Buffer: 11 Bytes System Exclusive
SYSX: F0 00 01 55 15 02 10 53 00 01 F7

But the SX Input Port light on the MIDI-OX Generated Event does NOT illuminate. Additionally, the eurorack module doesn't produce the expected behavior (pluck a string instrument)

My first question is rather simple: Is the SX Input Port light supposed to illuminate when sending Sysex?

My desired outcome is to trigger behaviors on the module by sending Sysex messages, and in my mind, it starts by the module responding when I Send Sysex via the Scratchpad

(Side note: I have asked the manufacturer for the MIDI spec for the device and they are unable to provide since this is an undocumented feature that I have stumbled upon.)

Thoughts?

PS Here is a screencap of my settings/setup https://twitter.com/motorbikematt/status/1635113738096492545/photo/1

Title: Re: Send Sysex Confusion
Post by Breath on Mar 14^th, 2023, 11:34pm

Hi
it looks like you have set it up correctly.
Did you click the SYX button (enable sysex transmission) in the lower toolbar to turn it off and then again to hi-light it and turn sysex enabled on?
When you set up a new connection in the Midi Routing window you need to refresh this sysex enable (looks like a bug, but it is an easy workaround - as long as you remember).

You should see the sysex being transmitted in Output Monitor window.

I rarely use the MIDI Port Activity window, but just checking now I couldn't get the SX (sysex) light to flash. Even through a loopMidi software cable.
So it look like you can't rely on that.

If you want to keep 'sniffing' you could always download Wireshark and look at the USB port for the module.

I'm not sure much of that was helpful, but feel free to post again to let me know how you got on.

All the best
Royce

Title: Re: Send Sysex Confusion
Post by motorbikematt on Apr 26^th, 2023, 1:16am

Thanks Royce, I am only now seeing this reply!

I will try your advice over the weekend and report back...you've described something I hadn't realized before so this is helpful.

Matt