Ok.
Here's the point:
1. In Cross we try to follow the MIDI specs/recommendations (
http://www.MIDI.org).
2. Most of DJ MIDI controller manufacturers don't give a **** about these MIDI specs and just send what they want thru the MIDI interface.
Result: Some devices don't work well in Cross.
About the other pieces of software, in many of them, developers don't hesitate to mess their code up to fit some controllers whims, for free ! That's not our policy, as far as the mess is bigger than the gain !
To be a bit more technical, the VCi-300 uses some 14-bits messages. These messages are clearly explained in the MIDI specs. There are two ways of interpreting CC messages in MIDI:
1. the 7-bits one: each message (from 0x00 to 0x7F) is interpreted independently
2. the 14-bits one:
* messages from 0x00 to 0x1F are MSB (Most Significant Bits),
* messages from 0x20 to 0x3F are the LSB (Least Significant Bits) matching with the first group,
* messages from 0x40 to 0x7F are standard 7-bits messages.
The "monitor select" knob "is" 7-bits but uses the CC 0x19... This means it interpreted as 14-bits (following the MIDI specs), leading to erroneous values at range bounds.
Note that there's the same issue with most of the VCI-300 knobs, but it's hard to hear that you EQ bass gain (for instance) is not perfectly respecting the knob physical position...
Hope this is clearer for you!
But don't misunderstand me, I'm not happy at all that you can't perfectly use your controller with Cross. If we had the means to develop an app for each controller, we'd do it, for sure... I regret some DJ software companies (MixVibes too, I guess ...) started to accept incoherent MIDI implementations in the past, this has led to that.
Cheers,