fvkempen
I'm trying to do some custom mapping in order to use midi signals from a Behringer X32 to create a fader start for Virtual DJ (Using M-Audio Fast Track Pro + MacBook).
Until know, I haven't been able to figure out how to use conditions like param_bigger 50% in a solid way and started wondering what values are actually being sent by the X32. Is there a way to see the value that was sent by the midi-device?
Until know, I haven't been able to figure out how to use conditions like param_bigger 50% in a solid way and started wondering what values are actually being sent by the X32. Is there a way to see the value that was sent by the midi-device?
Posted Thu 05 Jan 17 @ 9:28 pm
groovindj
Try using software called MIDI Ox.
Posted Thu 05 Jan 17 @ 10:13 pm
locoDog
tell me in plain english exactly what you want to happen and I may write the script.
Posted Thu 05 Jan 17 @ 10:35 pm
fvkempen
locodog wrote :
tell me in plain english exactly what you want to happen and I may write the script.
Thanks for thr offer! Writing the script isn't my concern though. The challenge is to figure what values can be expected. I was anticipating on receiving 0-127 and by accident just discovered that for example the sliders send 0-1 instead.
So now I'm wondering about the potential values being sent by the jogwheel and encoder.
Posted Thu 05 Jan 17 @ 10:47 pm
fvkempen
groovindj wrote :
Try using software called MIDI Ox.
Thanks, I'll take a look at that one.
Posted Thu 05 Jan 17 @ 10:48 pm
PhantomDeejay
fvkempen wrote :
Thanks for thr offer! Writing the script isn't my concern though. The challenge is to figure what values can be expected. I was anticipating on receiving 0-127 and by accident just discovered that for example the sliders send 0-1 instead.
So now I'm wondering about the potential values being sent by the jogwheel and encoder.
locodog wrote :
tell me in plain english exactly what you want to happen and I may write the script.
Thanks for thr offer! Writing the script isn't my concern though. The challenge is to figure what values can be expected. I was anticipating on receiving 0-127 and by accident just discovered that for example the sliders send 0-1 instead.
So now I'm wondering about the potential values being sent by the jogwheel and encoder.
MIDI is a very well defined protocol.
If your component is a FADER it should send one or two different messages with values 0-127
If it's sending 1 value it's 7-bit MIDI (0-7F) and if it's sending two different values it's 14-bit MIDI (First value is coarse (0-7F) also called MSB - Most Significant Byte and the second value is fine position (0-7F) between two successive coarse values, also called LSB - Less Significant Byte)
If your component is NOT sending values 0-7F but it's sending several "1" values then most likely it's an ENCODER.
ENCODERS don't have a start or an end. Therefore they don't have lower and highest values. They send increase/decrease STEPS instead. So, when you see something like B0 07 01 it means 1 step forward from previous position.
So, generally speaking keep in mind these facts:
FADERS/SLIDERS send "Control Change" (aka CC) messages with values ranging from 0 to 127 (7F in HEX)
7-bit faders send 1 message, 14-bit faders send two messages
ENCODERS also send Control Change messages. They send 0,1,2 e.t.c values for forward movement (depending on speed) and 7F, 7E, 7D e.t.c. values for backwards movement. Some encoders may have their "zero" position set on another value like 0x40 (HEX). In that case you should see 41 when you move the encoder forward, and 3F when you move the encoder backwards
JOGS are basically ENCODERS, therefore their MIDI code is EXACTLY the same!
More information you can find on our Wiki:
www.virtualdj.com/wiki/ControllerDefinitionMIDIv8.html
Posted Fri 06 Jan 17 @ 6:46 pm