MIDI-OX User Forum - Print Page


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

        MIDI-OX >> Mapping Questions >> How do I combine multiple sysex commands in 1 line
        
(Message started by: stevehdj on Feb 21^st, 2016, 11:47am)

Title: How do I combine multiple sysex commands in 1 line
Post by stevehdj on Feb 21^st, 2016, 11:47am

Hi I have constructed a data mapping file to send sysex commands from the pedal board of my Technics GA3 to a Yamaha PSR S770. The map converts pedal notes to trigger style variations. However a single sysex message will not create both a fill in and variation style change. Is it possible to combine multiple sysex commands on one line entry of the data mapping? I am trying to send the format below with F0 as the start of each command segment but not sure if there needs to be some type of separator between commands.

FO 43 7E 00 10 7F F7 F0 43 7E 00 08 7F F7

Title: Re: How do I combine multiple sysex commands in 1
Post by Breath on Feb 21^st, 2016, 10:38pm

Hi

I have to say that the Note to sysex behaves in a strange way.
Windows handles Midi in two ways. The short message (not sysex) and the long message (sysex).

Because of that I think Jamie is expecting just one pair of F0 and F7 in the message.
This may cause problems with two or more messages on one line, but the single line of 2 sysex messages works for me.

What you might be missing is that the sysex comes out of the MidiOx Event Port.
I not sure why.

However it is easy to do with more lines. Lets use Middle C (note 60) as the trigger.
If the GA3A puts out NOTE ON with velocity = 0 instead of NOTE OFF (as many keyboards do) you need to discard the vel = 0 message first
IN Chan 1 Note ON Min 60 Max 60 Min 0 Max 0 - NO check for CLONE
OUT Discard
Add a new line
IN Chan 1 Note ON Min 60 Max 60 Min 1 Max 127 - check the CLONE
OUT Sysex FO 43 7E 00 10 7F F7
Add a new line
IN Chan 1 Note ON Min 60 Max 60 Min 1 Max 127 - NO check for CLONE
OUT Sysex F0 43 7E 00 08 7F F7

It will create them in the wrong order so you need to move the lines up or down to end up with them in the above order

Save the file
Test by checking the TURN MAP ON and pressing OK

Now here is the weird part....
On the Midi Port Routing window....

Normally you would just connect your GA3 to the PSR for to convert simple Midi messages.
For the Sysex you need Connect the MidiOx Event Port to the PSR.

If you just need the Sysex then only connect the MidiOx Event Port to the PSR.
The incoming Note message from the GA3 will trigger the sysex without passing other Midi messages.
Perhaps this is why Jamie did it this way.

Make sure Options / Pass Sysex is checked.
You should be good to go.
The the label on the Port with the sysex message should be threes letters of MidiOx Event Port, but it won't be. Don't know why. A bug?

NOTE: You will get strange results when you start MidiOx with Pass Sysex checked (it remembers the state it was in last).
There is a bug and the fix is - when you start MidiOx you need to un-check then re-check Pass Sysex.

NOTE: a note trigger coming in on ANY Midi port will send the sysex

All the best

Royce