BladeRelic
i picked up the mkII last week and i am enjoying it, but im having a issue with using the pitch fader. many times when i move the fader, VirtualDJ doesn't respond. i'd have to move the fader completely up and down several times before VirtualDJ understands what i am trying to do. of course by then the song is either playing too fast or too slow.
i did some research and i see some info about "soft takeover" and i am guessing that could be my issue. is there anything i can do to fix this problem? by the way, the pitch fader works perfectly in serato so i know there's no problem with my controller.
i did some research and i see some info about "soft takeover" and i am guessing that could be my issue. is there anything i can do to fix this problem? by the way, the pitch fader works perfectly in serato so i know there's no problem with my controller.
Posted Fri 12 Sep 25 @ 8:41 pm
DJ VinylTouch
The option you want is controllerTakeoverModePitch=Instant
Be aware this might cause a jump of BPM after loading a new track and moving the pitch (and that is the reason the soft takeover was most likely introduced in the first place).
Be aware this might cause a jump of BPM after loading a new track and moving the pitch (and that is the reason the soft takeover was most likely introduced in the first place).
Posted Fri 12 Sep 25 @ 10:13 pm
BladeRelic
so even with changing that setting, i still have the problem with the pitch fader. it still takes a bit for virtualdj to recognize that i am moving it
Posted Sat 13 Sep 25 @ 1:34 am
DJ VinylTouch
Not sure what you mean there.
Probably you could provide a video showing what you are talking about? Provide the specs of your machine, the version of VirtualDJ and probably show settings like "latency" and the same setting from above as well.
Probably you could provide a video showing what you are talking about? Provide the specs of your machine, the version of VirtualDJ and probably show settings like "latency" and the same setting from above as well.
Posted Sat 13 Sep 25 @ 3:41 am
BladeRelic
im glad you mentioned latency. my latency is set to 512 and i have UltraLatency enabled. i will set those to the default settings and see how everything behaves.
Posted Sat 13 Sep 25 @ 6:34 am
PhantomDeejay
It is quite simple:
When you use "SYNC" or any other action that will force the deck's pitch to adjust, the pitch value of the software will no longer match the position of the physical pitch fader on the controller and they will become unlinked.
When this happens the little arrow LEDs next to the physical pitch slider will turn on to indicate on which direction you need to move the pitch slider in order to "catch up" the software pitch and therefore have them link again.
So, the right way to do it, is to leave controllerTakeoverModePitch setting to the default value (pickup) and learn how to pick up pitch properly.
When you use "SYNC" or any other action that will force the deck's pitch to adjust, the pitch value of the software will no longer match the position of the physical pitch fader on the controller and they will become unlinked.
When this happens the little arrow LEDs next to the physical pitch slider will turn on to indicate on which direction you need to move the pitch slider in order to "catch up" the software pitch and therefore have them link again.
So, the right way to do it, is to leave controllerTakeoverModePitch setting to the default value (pickup) and learn how to pick up pitch properly.
Posted Sat 13 Sep 25 @ 9:38 am
BladeRelic
PhantomDeejay wrote :
It is quite simple:
When you use "SYNC" or any other action that will force the deck's pitch to adjust, the pitch value of the software will no longer match the position of the physical pitch fader on the controller and they will become unlinked.
When this happens the little arrow LEDs next to the physical pitch slider will turn on to indicate on which direction you need to move the pitch slider in order to "catch up" the software pitch and therefore have them link again.
So, the right way to do it, is to leave controllerTakeoverModePitch setting to the default value (pickup) and learn how to pick up pitch properly.
When you use "SYNC" or any other action that will force the deck's pitch to adjust, the pitch value of the software will no longer match the position of the physical pitch fader on the controller and they will become unlinked.
When this happens the little arrow LEDs next to the physical pitch slider will turn on to indicate on which direction you need to move the pitch slider in order to "catch up" the software pitch and therefore have them link again.
So, the right way to do it, is to leave controllerTakeoverModePitch setting to the default value (pickup) and learn how to pick up pitch properly.
my problem happens even when i just load a song and not syncing/bpm matching. i also forgot to mention, the pitch fader works like it's supposed to with my original Rane One. i have a gig to dj later today, i will try to get video footage to show what's going on.
Posted Sat 13 Sep 25 @ 12:21 pm
PhantomDeejay
We also pushed a silent controllers update, but until it makes it to you, you can remap a key by your own to see if it helps:
Find the Key DNC_PITCH_SLIDER_POS
Remap it to: load_pulse ? param_equal `pitch_slider` `pitch` ? send_nothing : pitch : pitch_slider
Find the Key DNC_PITCH_SLIDER_POS
Remap it to: load_pulse ? param_equal `pitch_slider` `pitch` ? send_nothing : pitch : pitch_slider
Posted Sat 13 Sep 25 @ 1:15 pm
BladeRelic
sorry for the delay in my reply. even with that action i still have the same problem. but, something interesting happened to me a couple days ago
i opened VDJ and loaded a track just before i noticed i didn't have my controller turned on. after turning on the controller, i noticed the leds didn't load up the proper colors for my cues (all the buttons were blue). the song played fine. then i loaded a song onto the other deck. it also didnt load up the proper colors for the cues. but then when i moved the pitch fader, it worked almost exactly as i expected it to!
i was able to adjust the tempo with no problem. i even saw the "ghost fader" in the skin and it showed exactly where my fader was. but there were a problem with the range. even with the range set to 10%, i was able to speed up/down the song as if my range was on 50%
i hope this helps diagnose what the problem could be
i opened VDJ and loaded a track just before i noticed i didn't have my controller turned on. after turning on the controller, i noticed the leds didn't load up the proper colors for my cues (all the buttons were blue). the song played fine. then i loaded a song onto the other deck. it also didnt load up the proper colors for the cues. but then when i moved the pitch fader, it worked almost exactly as i expected it to!
i was able to adjust the tempo with no problem. i even saw the "ghost fader" in the skin and it showed exactly where my fader was. but there were a problem with the range. even with the range set to 10%, i was able to speed up/down the song as if my range was on 50%
i hope this helps diagnose what the problem could be
Posted Fri 26 Sep 25 @ 6:49 pm
BladeRelic
PhantomDeejay wrote :
We also pushed a silent controllers update, but until it makes it to you, you can remap a key by your own to see if it helps:
Find the Key DNC_PITCH_SLIDER_POS
Remap it to: load_pulse ? param_equal `pitch_slider` `pitch` ? send_nothing : pitch : pitch_slider
Find the Key DNC_PITCH_SLIDER_POS
Remap it to: load_pulse ? param_equal `pitch_slider` `pitch` ? send_nothing : pitch : pitch_slider
what was the default mapping for this key?
Posted Fri 26 Sep 25 @ 7:23 pm