Message
RESULTS - Re: Well, how about an old ensoniqs VFX and sysex control???
2008-05-25 by rpcfender
> I figured out how to route the midi to from the BCR.
> Here is my current setup.
> BCR> (usb to midiox mapped to motu (usb) midi interface midi out 1>vfx
> Midiox is input and output window agree. Midi out show activity on
> the motu midi interface.
> When I turn the knob 49 any amount.
> The VFX responds "Midi sys-ex receive error press any key to continue"
> I suspect I have some sort of time issue with the vfx and receiving
> sysex messages.
Well... long distance programming without anything to test on means I am likely to miss something and I did
Header is OK
$F0 $0F $05 $00 $00 (chan 1)
but
$F0 $0F $05 $00 $00 $CommandType $Voice $Page $Slot $4byte-value $F7
$F0 $0F $05 $00 $00 $01 $Voice $Page $Slot $4byte-value $F7
should be
$F0 $0F $05 $00 $00 $MessageType $CommandType $Voice $Page $Slot $4byte-value $F7
MessageType is 0, CommandType is 1 (see section 3.1 and 3.1.1)
$F0 $0F $05 $00 $00 $00 $01 $Voice $Page $Slot $4byte-value $F7
so the new .tx line should be
.tx $F0 $0F $05 $00 $00 $00 $01 0 12 1 val12.13 val8.11 val4.7 val0.3 $F7
BUT I loaded MidiQuest and checked its output and got
$F0 $0F $05 $00 $00 $00 $00 $01 $00 $00 $00 $0D $00 1 val12.13 val8.11 val4.7 val0.3 $F7
The MessageType is 2bytes or the CommandType is 2bytes (?)
The Page is a 4 byte number and the Slot is 2 bytes long.
I haven't found this in the sysex spec. and SoundQuest get their templates wrong a lot of the time.
But if the first one doesn't fix you problem try
.tx $F0 $0F $05 $00 $00 $00 $00 $01 0 0 0 12 0 1 val12.13 val8.11 val4.7 val0.3 $F7
If you have an editor, hook it up to MidiOx and see what you get for the Cutoff on filter#1
Post the output here if it is different.
It is very frustrating not begin able to test before sending the info, but together we should be able to work it out.
All the best
Royce