jpboggis
With the increasing number of DJ MIDI controllers becoming available, a number of improvements need to be made to the MIDI mapper in VDJ to allow these to function correctly:
(1) Recognise control change and notes separately (CC (n) and NOTE (n) rather than both returning MIDI (n)) This is needed for most MIDI controllers (Including the new Behringer BCD2000) where some buttons (Notes) use the same number as sliders, knobs or jog wheels (Control change.) Unlike the DAC-3 and Kontrol-DJ, some MIDI controllers may not allow the MIDI messages sent by the device to be customised to get around this problem.
(2) Recognise left/right movements when control change number of jog wheel is mapped to 'scratch 0' or 'pitch_bend 0' - I.e: Controller value of 64 = right. Preferably, scratch/pitch_bend with absolute value >0 (E.g: scratch 512) would send +/- that value (E.g: +512/-512) depending on which way the jog wheel is turned, allowing sensitivity to be customised. Presently, jog wheels will only work in both directions in VDJ if they can be mapped to different control change numbers for left/right movements (DAC-3 and Kontrol-DJ allow this, but othes such as BCD2000 may not.)
(3) Inverse control change value for pitch, so that this works correctly (Up = slow down and down = speed up rather than present inverse of this.)
(4) Support course/fine controllers, for MIDI controllers that support this. This allows 16384 unique values rather than the usual 128 giving considerably finer control (Ideal for pitch, gain knob, etc.) See: http://www.borg.com/~jglatt/tech/midispec/ctllist.htm
(5) MIDI channel awareness - This would allow multiple MIDI devices to be used without conflict.
(1) Recognise control change and notes separately (CC (n) and NOTE (n) rather than both returning MIDI (n)) This is needed for most MIDI controllers (Including the new Behringer BCD2000) where some buttons (Notes) use the same number as sliders, knobs or jog wheels (Control change.) Unlike the DAC-3 and Kontrol-DJ, some MIDI controllers may not allow the MIDI messages sent by the device to be customised to get around this problem.
(2) Recognise left/right movements when control change number of jog wheel is mapped to 'scratch 0' or 'pitch_bend 0' - I.e: Controller value of 64 = right. Preferably, scratch/pitch_bend with absolute value >0 (E.g: scratch 512) would send +/- that value (E.g: +512/-512) depending on which way the jog wheel is turned, allowing sensitivity to be customised. Presently, jog wheels will only work in both directions in VDJ if they can be mapped to different control change numbers for left/right movements (DAC-3 and Kontrol-DJ allow this, but othes such as BCD2000 may not.)
(3) Inverse control change value for pitch, so that this works correctly (Up = slow down and down = speed up rather than present inverse of this.)
(4) Support course/fine controllers, for MIDI controllers that support this. This allows 16384 unique values rather than the usual 128 giving considerably finer control (Ideal for pitch, gain knob, etc.) See: http://www.borg.com/~jglatt/tech/midispec/ctllist.htm
(5) MIDI channel awareness - This would allow multiple MIDI devices to be used without conflict.
Inviato Wed 09 Nov 05 @ 12:34 pm
apopsisdj
We had an interesting conversation about it here..
http://www.virtualdj.com/forums/42209/Software_Technical_Support/Midi_setup_problem_on_actions_like_nudge_scratch__browser_updown__any_help__.html?page=1
I wrote my final conclusions, so copy and paste, here is my version:
Midi improvements ideas for virtual dj:
(reason: compatibility with existing and upcoming midi controllers)
1.Recognize all kind of midi messages (Control change, etc) so that midi notes and commands don't appear the same in vdj. Also recognize midi channels.
2.Midi setup dialog to allow to choose the midi in/out ports and midi mode (omni etc.)
This is useful when more than one midi interfaces are installed.
3.For now, actions like nudge, scratch, browser up/down, need 2 separate midi messages to work in two-way direction.
A single CC must be enough (value=64 as center with clockwise/anti-clockwise +- steps and midi value as velocity) for these actions.
4.An option to invert min/max (0/127) values, some controls may have wrong direction (like the pitch slider on Dac-3)
4.Midi parameter feedback for controllers with motorized faders, endless knobs, leds, this will work as native support, so less work for the team to support every new controller in the market..
http://www.virtualdj.com/forums/42209/Software_Technical_Support/Midi_setup_problem_on_actions_like_nudge_scratch__browser_updown__any_help__.html?page=1
I wrote my final conclusions, so copy and paste, here is my version:
Midi improvements ideas for virtual dj:
(reason: compatibility with existing and upcoming midi controllers)
1.Recognize all kind of midi messages (Control change, etc) so that midi notes and commands don't appear the same in vdj. Also recognize midi channels.
2.Midi setup dialog to allow to choose the midi in/out ports and midi mode (omni etc.)
This is useful when more than one midi interfaces are installed.
3.For now, actions like nudge, scratch, browser up/down, need 2 separate midi messages to work in two-way direction.
A single CC must be enough (value=64 as center with clockwise/anti-clockwise +- steps and midi value as velocity) for these actions.
4.An option to invert min/max (0/127) values, some controls may have wrong direction (like the pitch slider on Dac-3)
4.Midi parameter feedback for controllers with motorized faders, endless knobs, leds, this will work as native support, so less work for the team to support every new controller in the market..
Inviato Thu 10 Nov 05 @ 3:48 am
orange source
anything that will make the BCD2000 work with virtual DJ properly.
Inviato Mon 15 May 06 @ 11:41 pm