aknit
I am running Virtual DJ Pro 8.2 (build 3409.1236) for Mac. I am using it with the Numark Mixtrack Pro II controller.
I have configured custom effects and samplers on the 8 pads that are available on Virtual DJ. I would like to map those 8 pads to the 8 pads on each side of the controller as well. The idea is that when I press a pad on the controller, it actions a pad a corresponding pad on Virtual DJ. Please advise how I can go about doing that.
Secondly, I find that Virtual DJ does not properly detect the gain levels of a song when it is loaded, as each song is defaulted to 0dB. As such, many of the songs are too loud for the amplifier when played initially, and I have to manually adjust the gain levels of the song. Is there a way I can map the gain button on Virtual DJ to a button on the controller?
I have configured custom effects and samplers on the 8 pads that are available on Virtual DJ. I would like to map those 8 pads to the 8 pads on each side of the controller as well. The idea is that when I press a pad on the controller, it actions a pad a corresponding pad on Virtual DJ. Please advise how I can go about doing that.
Secondly, I find that Virtual DJ does not properly detect the gain levels of a song when it is loaded, as each song is defaulted to 0dB. As such, many of the songs are too loud for the amplifier when played initially, and I have to manually adjust the gain levels of the song. Is there a way I can map the gain button on Virtual DJ to a button on the controller?
Posted Sun 09 Oct 16 @ 10:22 am
djdad
The Mixtrack (Pro) II is not the ideal controller to handle the PADS of VirtualDJ. I assume you have created a Pad Page with some custom action.
Reason is that the Pads are split into sections.
Top Pads (the "easy" part of the story) : Those 4 top pads always send the same MIDI messages and are named as FX1 , FX2, FX3 and TAP. Those can be assigned as pad 1, pad 2, pad 3 and pad 4 and they can control the 4 top pads of the selected Pads Page.
Low Pads (the "hard" part of the story) : Those 4 bottom pads send different MIDI messages depending on the selected mode from the unit). Unfortunately when a mode is selected from the unit (using SHIFT+Pads5 to 7) they dont send MIDI, so the software doesnt know which one is selected. If the unit was sending MIDI in this case, we woul dhave mapped the unit to control Pads already.
So if you still want to assign the low Pads to control Pads 5 to 8 of the selected Pads Page, you need either to choose on which Hardware mode you need those to work or map all the available keys as pad 5 to pad 8
E.g. if you need the 4 bottom pads to control the Pads of the software when the SAMPLER Hardware mode is selected, you need to assign the follwoing keys..
SAMPLER_1 --> pad 5
SAMPLER_2--> pad 6
SAMPLER_3--> pad 7
SAMPLER_4--> pad 8
There is also an issue with the SHIFT button. SHIFT+PAD8 should work fine, but SHIFT+PAD5,6,7 wont., since those change the Hardware modes.
Reason is that the Pads are split into sections.
Top Pads (the "easy" part of the story) : Those 4 top pads always send the same MIDI messages and are named as FX1 , FX2, FX3 and TAP. Those can be assigned as pad 1, pad 2, pad 3 and pad 4 and they can control the 4 top pads of the selected Pads Page.
Low Pads (the "hard" part of the story) : Those 4 bottom pads send different MIDI messages depending on the selected mode from the unit). Unfortunately when a mode is selected from the unit (using SHIFT+Pads5 to 7) they dont send MIDI, so the software doesnt know which one is selected. If the unit was sending MIDI in this case, we woul dhave mapped the unit to control Pads already.
So if you still want to assign the low Pads to control Pads 5 to 8 of the selected Pads Page, you need either to choose on which Hardware mode you need those to work or map all the available keys as pad 5 to pad 8
E.g. if you need the 4 bottom pads to control the Pads of the software when the SAMPLER Hardware mode is selected, you need to assign the follwoing keys..
SAMPLER_1 --> pad 5
SAMPLER_2--> pad 6
SAMPLER_3--> pad 7
SAMPLER_4--> pad 8
There is also an issue with the SHIFT button. SHIFT+PAD8 should work fine, but SHIFT+PAD5,6,7 wont., since those change the Hardware modes.
Posted Sun 09 Oct 16 @ 2:36 pm
aknit
Many thanks for your reply djdad. It is very helpful.
I don't need to use the pads in SHIFT mode at all, so I'm happy to dedicate them to the pads.
Let me work on coding the mapping as per your suggestions. I'll get back to you with how it goes.
I don't need to use the pads in SHIFT mode at all, so I'm happy to dedicate them to the pads.
Let me work on coding the mapping as per your suggestions. I'll get back to you with how it goes.
Posted Sun 09 Oct 16 @ 3:19 pm