Hey I just got Virtual DJ and I don't have a real DJ controller so I'm using my Ableton Move. I've set up my pads to work as the pads in the software, but when I use them in stems mode, it just doesn't work most of the time. About 1 out of every 10 presses it'll actually work. All the stems are already generated for all the songs and when I actually click the buttons with my mouse it works fine, just not with the pads for some reason. The fx pads that I have from the Stems & FX plugin (Vocal echo, instrumental echo, instrumental braker and drums echo) work fine every time, but not the vocals, melody, bass and drums. Also, I have pads set to loop 16, loop 50% and loop 200%, but it just doesn't work really, sometimes it doesn't add the loop at all, sometimes it makes it 32 beats instead of 16, sometimes the 200% and 50% act as 400% and 25%, just very weird
idk can anyone help?
idk can anyone help?
geposted 3 days ago @ 1:54 am
oh also I mapped play_pause onto my play button and it also only works like 1/10th of the time
geposted 3 days ago @ 1:55 am
and, is there a way to make just one pad for auto loop, like Serato has? like it'll figure out how many bars to loop, pressing it again deactivates the loop
geposted 3 days ago @ 1:56 am
Most likely you'll have to create a device definition for your controller for everything to work properly.
If I could take a guess, your pads right now send velocity messages which are not interpreted "correctly" by the software. I mean that for VirtualDJ to consider that a button has been pressed, it must send 0x7F. However, when using velocity buttons, this means that you have to push the button/pad really hard to get that value and if you don't VirtualDJ ignores it.
This can be solved by creating/using a device definition that tells VirtualDJ exactly what to expect from every button.
PS: Custom Device Definition need a PRO license.
If I could take a guess, your pads right now send velocity messages which are not interpreted "correctly" by the software. I mean that for VirtualDJ to consider that a button has been pressed, it must send 0x7F. However, when using velocity buttons, this means that you have to push the button/pad really hard to get that value and if you don't VirtualDJ ignores it.
This can be solved by creating/using a device definition that tells VirtualDJ exactly what to expect from every button.
PS: Custom Device Definition need a PRO license.
geposted 2 days ago @ 5:20 am
Alright thanks, I'll try it
geposted 2 days ago @ 1:14 pm
Although I don't think it is that because I can use them fine for everything else, under the hotcues, slicer and sampler pages they work fine, just not stems
geposted 2 days ago @ 1:18 pm