Virtual dj remote full apk download. Last edit by philibuster, Limited edition user on Thu 28 Jan 16 @ 2:32 am
Dj Brand00 Controllerist Member since 2017 Hi. I want to set my knob that when i turn it (touch it a bit) it sets my selected effect of that knob to zero (all the way to left)v and when i turn it to right it goes all the way to right. And i want to control the sensitivity of a know in script. Any sugestions? Feb 12, 2013 Then there's also midi notes/control CC. Why wont garageband download sounds. These are the ones I have had to map on the jog wheel on the Vestax VCI 100mk 1 to get scratching, jog turn, and scrolling the browser to work And as said previously the commands can vary from Traktor version update. I think there's only two specific jog commands in 2.6.0.
Virtual Dj Jog Wheel Sensitivity Chart
Virtual Dj 8 Jog Wheel Sensitivity
Here are some VDJscript examples compiled by jpboggis:
Control 4 decks with a 2 deck controller (E.g: Hercules DJ Console):
Change the mapping of the PFL button to the following:
Pressing the PFL button will select the deck for headphone pre-listen if it's not currently selected, otherwise it will toggle between controlling decks 1 & 3 on the left side or decks 2 & 4 on the right.
Alternatively, you can assign a separate button that is present on both sides of the controlller to the following:
This will toggle between decks 1 & 3 on the left side and decks 2 & 4 on the right, with the button LED (If it has one) indicating which deck is selected (On = 3/4)
NOTE: On a single deck controller, you can use the action invert_controllers to change which deck it is assigned to. By default, this is assigned to the EJECT button of the controller if it has one.
Toggle single timecode between the decks using TAB:
If you are using a single timecode deck, then by default when you press TAB, it will not follow the selected deck. You must manually assign it in the SCRATCH section of the default skin.
To make it follow the selected deck as you press TAB, simply change the mapping for the TAB key to the following:
Toggle vinyl (Scratch) mode on/off for all decks with a single button:
If you are using a controller such as a Hercules DJ Console that has a single SCRATCH button to toggle vinyl (Scratch) mode on/off, then you will find that this only works for the first two decks. Simply change the mapping for the button as follows to make it work for all 4 (Or 6) decks:
4 decks:
6 decks:
Use a combination of buttons to trigger two different actions (I.e: SHIFT button):
VDJscript for the button that will act as the modifier, i.e: SHIFT:
Button to perform two different actions depending on the state of SHIFT button, e.g: FX:
This causes the button to trigger flanger on its own, and backspin if SHIFT+button is pressed.
Toggle a specific effect on/off with a button:
(Replace Flanger with any other effect name of your choice.)
Toggle a specific video effect on/off with a button:
Adjust FX parameter using the jogwheel:
Change the jogwheel mapping to the following:
(Use touchwheel instead of jogwheel for a touch sensitive jogwheel.)
To adjust parameter 1 with the left jogwheel and parameter 2 with the right jogwheel on a dual-deck controller:
Double/half loop using the jogwheel (When a loop is active):
Change the jogwheel mapping to the following:
The sensitivity can be adjusted by changing the value 100 (Smaller = More sensitive.)
(As above, use touchwheel instead of jogwheel for a touch sensitive jogwheel.)
Adjust loop length using a knob or slider (When a loop is active)l:
To invert the behaviour of the slider, add param_invert, e.g:
NOTE: To adjust loop length with an endless encoder knob (One that can be turned continuously with no stopping point), use:
Assign different actions for the same button/knob on each side of a dual-deck controller:
The controller definitions for dual-deck controllers such as the Hercules DJ Console RMX, Denon DN-HC4500, etc. are setup so that each button only needs to be mapped once (E.g: PLAY is mapped once to play_pause instead of needing to map it twice (Once for each deck.)
This is done for convenience and to make the mapping considerably simpler, because in most cases, the button, knob, etc. will perform the same function on both sides.
However, you can make a mapping perform different functions for each side by using device_side, e.g:
This would make a button trigger a sample on the left side and effect on the right.
Of course, the action will be applied to appropriate deck based on which side it's on. You can also get around this by preceding the action with the following:
deck left to apply to left deck.
deck right to apply to right deck.
deck 1 to apply to deck 1.
deck 2 to apply to deck 2.
deck 3 to apply to deck 3.
deck 4 to apply to deck 4.
deck active to apply to the active deck (The one playing out live.)
deck default to apply to the default deck (The one being cued up/pre-listened to.)
E.g:
NOTE: Old VirtualDJ v6 mappings using action_deck should be changed to action_deck
Trigger a different function if the button is held down for a given amount of time:
By using holding, you can get a button to perform two different functions depending on whether it's 'clicked' or held down and then released. The amount of time in milliseconds can be optionally specified. E.g: A LOAD button on a controller could be mapped to the following:
This will cause the button to load the selected song from the browser if the button is clicked, and unload the song from the deck if the button is held down for 2 seconds and then released.
NOTE: You should be careful using holding with actions where timing is critical, such as hot_cue. This is because the function is triggered when the button is released rather than pressed, resulting in a small random delay depending on how fast you press and release the button. For load/unload, this is not important, but if you are trying to play a hot cue on the beat, this delay may result in your mix being slightly out of time.
Make buttons perform different functions depending on what mode is selected:
First map a button to cycle through the modes, e.g: For 4 different modes Normal, Effects, Video and Sampler:
If your controller does not have text displays, then map the button to:
And map the LED of the button (BUTTONNAME_LED) to indicate the mode:
The variable 'mode' now holds the mode number, which you can then use in the mapping for each button that will act differently depending on the mode, e.g: You could map a button as follows:
The button will act as follows:
Normal: Hot cue #1
Effects: Turns flanger on/off
Video: Turns the video effect 'Negative' on/off
Sampler: Plays sample #1
Fine pitch adjustment with a knob:
Assigning the following to an endless encoder knob on your controller (If it has one) will allow you to make very fine pitch adjustments.
Alternatively, you can map two buttons to the following:
Protected CUE button:
Changing the mapping of the CUE button of a controller to the following will prevent the cue point from being accidentally changed by pressing the CUE button when the song is paused away from the cue point. To change the cue point, it must be deleted first.
CUP (Cue and play):
This feature will go to the current cue point while the button is held down, then start the song playing as soon as the button is released. If the song is already playing, it will jump to the cue point and continue playing.
CUE button that does not modify existing cue points
Map the CUE button to the following:
Stutter button:
The following implements a stutter button. The first press sets the stutter point (Loop in.) Further presses stutter the music from that point. If the button is not used for a few seconds, it will reset automatically.
NOTE: When a loop is active, the button will perform reloop.
Map the button to the following:
Map the button LED (If it has one) separately to the following:
'Chop' between both decks:
The following will pause the active playing deck and start the opposite deck playing:
Simple MIDI Wrapper invert pitch slider
When mapping the pitch slider with Simple MIDI wrapper, you may find that the slider is inverted, so that moving the slider up speeds the song up instead of slowing it down (As on most DJ CD players and vinyl decks.) To invert the pitch slider so that it behaves correctly (Up slows down), simply map it as follows:
Simple MIDI Wrapper Endless Encoder Knobs and Jogwheels
Simple MIDI wrapper only supports very basic MIDI such as buttons, sliders and knobs with a min/max stopping point. Other features such as endless encoder knobs, jogwheels and LED's ideally require a controller definition to work optimally: http://www.virtualdj.com/wiki/ControllerDefinitionMIDI.html
However, you can map an endless encoder knob in Simple MIDI Wrapper by using the following:
E.g:
And you can map a jogwheel using the following:
For a dual-deck controller, you will need to add the appropriate deck in front of each action:
For a touch-sensitive jogwheel, you will need to use touchwheel instead of jogwheel in the above mappings and also map touchwheel_touch to the touch sensor.
Use left/right jogwheels to browse folders and songs on a dual-deck controller:
Map the jogwheel to:
Map the button to toggle browsing on/off to:
Denon HC-DNH4500 A1/A2 buttons:
To make the A1/A2 buttons behave similar to how they do on Denon CD players, change their mappings as follows:
A1 = set 'A1' 1 while_pressed & var 'FLIP' ? delete_cue 98 & loop_exit : hot_cue 98 & loop_in & set 'ABTN' 1
A2 = set 'A2' 1 while_pressed & var 'FLIP' ? delete_cue 99 & loop_exit : hot_cue 99 & loop_in & set 'ABTN' 2
B = var 'FLIP' ? loop_exit : loop ? loop_half : loop_out
LED_A1_DIMMER = hot_cue 98
LED_A2_DIMMER = hot_cue 99
LED_A1 = loop ? var_equal 'ABTN' 1 ? on : off : off
LED_A2 = loop ? var_equal 'ABTN' 2 ? on : off : off
LCD_LOOP1_( = loop ? var_equal 'ABTN' 1 ? on : off : off
LCD_LOOP1_A1 = hot_cue 98
LCD_LOOP1_B = loop ? var_equal 'ABTN' 1 ? on : off : off
LCD_LOOP1_) = loop ? var_equal 'ABTN' 1 ? on : off : off
LCD_LOOP2_( = loop ? var_equal 'ABTN' 2 ? on : off : off
LCD_LOOP2_A2 = hot_cue 99
LCD_LOOP2_B = loop ? var_equal 'ABTN' 2 ? on : off : off
LCD_LOOP2_) = loop ? var_equal 'ABTN' 2 ? on : off : off
FLIP = set 'FLIP' 1 while_pressed & holding 1000ms ? delete_cue 98 & delete_cue 99 & loop_exit : var 'A1' ? wheel_mode 'jog' : var 'A2' ? wheel_mode 'jog' : loop ? wheel_mode 'loop_move,loop_out,loop_in,jog' : wheel_mode 'jog'
NOTE: This uses cue points 98 and 99 - If you don't want these saved in your song, please ensure that you ensure that you clear them first (Hold FLIP for 1 second or press FLIP+A1 and/or FLIP+A2)
Επιστροφή στην αρχική σελίδα
Supported Controllers
Control 4 decks with a 2 deck controller (E.g: Hercules DJ Console):
Change the mapping of the PFL button to the following:
Pressing the PFL button will select the deck for headphone pre-listen if it's not currently selected, otherwise it will toggle between controlling decks 1 & 3 on the left side or decks 2 & 4 on the right.
Alternatively, you can assign a separate button that is present on both sides of the controlller to the following:
This will toggle between decks 1 & 3 on the left side and decks 2 & 4 on the right, with the button LED (If it has one) indicating which deck is selected (On = 3/4)
NOTE: On a single deck controller, you can use the action invert_controllers to change which deck it is assigned to. By default, this is assigned to the EJECT button of the controller if it has one.
Toggle single timecode between the decks using TAB:
If you are using a single timecode deck, then by default when you press TAB, it will not follow the selected deck. You must manually assign it in the SCRATCH section of the default skin.
To make it follow the selected deck as you press TAB, simply change the mapping for the TAB key to the following:
Toggle vinyl (Scratch) mode on/off for all decks with a single button:
If you are using a controller such as a Hercules DJ Console that has a single SCRATCH button to toggle vinyl (Scratch) mode on/off, then you will find that this only works for the first two decks. Simply change the mapping for the button as follows to make it work for all 4 (Or 6) decks:
4 decks:
6 decks:
Use a combination of buttons to trigger two different actions (I.e: SHIFT button):
VDJscript for the button that will act as the modifier, i.e: SHIFT:
Button to perform two different actions depending on the state of SHIFT button, e.g: FX:
This causes the button to trigger flanger on its own, and backspin if SHIFT+button is pressed.
Toggle a specific effect on/off with a button:
(Replace Flanger with any other effect name of your choice.)
Toggle a specific video effect on/off with a button:
Adjust FX parameter using the jogwheel:
Change the jogwheel mapping to the following:
(Use touchwheel instead of jogwheel for a touch sensitive jogwheel.)
To adjust parameter 1 with the left jogwheel and parameter 2 with the right jogwheel on a dual-deck controller:
Double/half loop using the jogwheel (When a loop is active):
Change the jogwheel mapping to the following:
The sensitivity can be adjusted by changing the value 100 (Smaller = More sensitive.)
(As above, use touchwheel instead of jogwheel for a touch sensitive jogwheel.)
Adjust loop length using a knob or slider (When a loop is active)l:
To invert the behaviour of the slider, add param_invert, e.g:
NOTE: To adjust loop length with an endless encoder knob (One that can be turned continuously with no stopping point), use:
Assign different actions for the same button/knob on each side of a dual-deck controller:
The controller definitions for dual-deck controllers such as the Hercules DJ Console RMX, Denon DN-HC4500, etc. are setup so that each button only needs to be mapped once (E.g: PLAY is mapped once to play_pause instead of needing to map it twice (Once for each deck.)
This is done for convenience and to make the mapping considerably simpler, because in most cases, the button, knob, etc. will perform the same function on both sides.
However, you can make a mapping perform different functions for each side by using device_side, e.g:
This would make a button trigger a sample on the left side and effect on the right.
Of course, the action will be applied to appropriate deck based on which side it's on. You can also get around this by preceding the action with the following:
deck left to apply to left deck.
deck right to apply to right deck.
deck 1 to apply to deck 1.
deck 2 to apply to deck 2.
deck 3 to apply to deck 3.
deck 4 to apply to deck 4.
deck active to apply to the active deck (The one playing out live.)
deck default to apply to the default deck (The one being cued up/pre-listened to.)
E.g:
NOTE: Old VirtualDJ v6 mappings using action_deck should be changed to action_deck
Trigger a different function if the button is held down for a given amount of time:
By using holding, you can get a button to perform two different functions depending on whether it's 'clicked' or held down and then released. The amount of time in milliseconds can be optionally specified. E.g: A LOAD button on a controller could be mapped to the following:
This will cause the button to load the selected song from the browser if the button is clicked, and unload the song from the deck if the button is held down for 2 seconds and then released.
NOTE: You should be careful using holding with actions where timing is critical, such as hot_cue. This is because the function is triggered when the button is released rather than pressed, resulting in a small random delay depending on how fast you press and release the button. For load/unload, this is not important, but if you are trying to play a hot cue on the beat, this delay may result in your mix being slightly out of time.
Make buttons perform different functions depending on what mode is selected:
First map a button to cycle through the modes, e.g: For 4 different modes Normal, Effects, Video and Sampler:
If your controller does not have text displays, then map the button to:
And map the LED of the button (BUTTONNAME_LED) to indicate the mode:
The variable 'mode' now holds the mode number, which you can then use in the mapping for each button that will act differently depending on the mode, e.g: You could map a button as follows:
The button will act as follows:
Normal: Hot cue #1
Effects: Turns flanger on/off
Video: Turns the video effect 'Negative' on/off
Sampler: Plays sample #1
Fine pitch adjustment with a knob:
Assigning the following to an endless encoder knob on your controller (If it has one) will allow you to make very fine pitch adjustments.
Alternatively, you can map two buttons to the following:
Protected CUE button:
Changing the mapping of the CUE button of a controller to the following will prevent the cue point from being accidentally changed by pressing the CUE button when the song is paused away from the cue point. To change the cue point, it must be deleted first.
CUP (Cue and play):
This feature will go to the current cue point while the button is held down, then start the song playing as soon as the button is released. If the song is already playing, it will jump to the cue point and continue playing.
CUE button that does not modify existing cue points
Map the CUE button to the following:
Stutter button:
The following implements a stutter button. The first press sets the stutter point (Loop in.) Further presses stutter the music from that point. If the button is not used for a few seconds, it will reset automatically.
NOTE: When a loop is active, the button will perform reloop.
Map the button to the following:
Map the button LED (If it has one) separately to the following:
'Chop' between both decks:
The following will pause the active playing deck and start the opposite deck playing:
Simple MIDI Wrapper invert pitch slider
When mapping the pitch slider with Simple MIDI wrapper, you may find that the slider is inverted, so that moving the slider up speeds the song up instead of slowing it down (As on most DJ CD players and vinyl decks.) To invert the pitch slider so that it behaves correctly (Up slows down), simply map it as follows:
Simple MIDI Wrapper Endless Encoder Knobs and Jogwheels
Simple MIDI wrapper only supports very basic MIDI such as buttons, sliders and knobs with a min/max stopping point. Other features such as endless encoder knobs, jogwheels and LED's ideally require a controller definition to work optimally: http://www.virtualdj.com/wiki/ControllerDefinitionMIDI.html
However, you can map an endless encoder knob in Simple MIDI Wrapper by using the following:
E.g:
And you can map a jogwheel using the following:
For a dual-deck controller, you will need to add the appropriate deck in front of each action:
For a touch-sensitive jogwheel, you will need to use touchwheel instead of jogwheel in the above mappings and also map touchwheel_touch to the touch sensor.
Use left/right jogwheels to browse folders and songs on a dual-deck controller:
Map the jogwheel to:
Map the button to toggle browsing on/off to:
Denon HC-DNH4500 A1/A2 buttons:
To make the A1/A2 buttons behave similar to how they do on Denon CD players, change their mappings as follows:
A1 = set 'A1' 1 while_pressed & var 'FLIP' ? delete_cue 98 & loop_exit : hot_cue 98 & loop_in & set 'ABTN' 1
A2 = set 'A2' 1 while_pressed & var 'FLIP' ? delete_cue 99 & loop_exit : hot_cue 99 & loop_in & set 'ABTN' 2
B = var 'FLIP' ? loop_exit : loop ? loop_half : loop_out
LED_A1_DIMMER = hot_cue 98
LED_A2_DIMMER = hot_cue 99
LED_A1 = loop ? var_equal 'ABTN' 1 ? on : off : off
LED_A2 = loop ? var_equal 'ABTN' 2 ? on : off : off
LCD_LOOP1_( = loop ? var_equal 'ABTN' 1 ? on : off : off
LCD_LOOP1_A1 = hot_cue 98
LCD_LOOP1_B = loop ? var_equal 'ABTN' 1 ? on : off : off
LCD_LOOP1_) = loop ? var_equal 'ABTN' 1 ? on : off : off
LCD_LOOP2_( = loop ? var_equal 'ABTN' 2 ? on : off : off
LCD_LOOP2_A2 = hot_cue 99
LCD_LOOP2_B = loop ? var_equal 'ABTN' 2 ? on : off : off
LCD_LOOP2_) = loop ? var_equal 'ABTN' 2 ? on : off : off
FLIP = set 'FLIP' 1 while_pressed & holding 1000ms ? delete_cue 98 & delete_cue 99 & loop_exit : var 'A1' ? wheel_mode 'jog' : var 'A2' ? wheel_mode 'jog' : loop ? wheel_mode 'loop_move,loop_out,loop_in,jog' : wheel_mode 'jog'
NOTE: This uses cue points 98 and 99 - If you don't want these saved in your song, please ensure that you ensure that you clear them first (Hold FLIP for 1 second or press FLIP+A1 and/or FLIP+A2)
Επιστροφή στην αρχική σελίδα
Supported Controllers