Sign In:     

Forum: VirtualDJ Technical Support

Topic: Rane Twelve MK2 suddenly plays at ridiculous fast speed
My setup is
2x Rane Twelve Mk2
NI NX1MK3
DB4 Mixer
Windows.

I've just started looking further into VDJ and after some month of sessions with that setup today my tracks started playing somehow Factor x3/4 when firing up one of my Twelves. This used to work until 2/3 days ago and I cannot remember having changed anything. The screen shows 0%-Pitch (as do the faders).

Having looked for other ppl there seemed to have been some issue with the sample in the past, so I've tried changing that first, didnt help, so I'm back to 44.1. Restarting/re-connecting several times did not seem to work either.

Whenever unplugging the Twelves sound goes back to normal. as two independent players, exchanged in any way, do cause the same issue I don't think its a hardware issue. I alse tried their timecode feature (no HID) with Traktor which also works fine.

Any ideas?
 
Posted Tue 12 Nov 24 @ 11:13 pm
Ive also had this happen. First with my Technics 1200s with timecode, both serato and vdj tcv. It also recently happened with my Vestax VCI-400. I have no clue what causes it.
 
Did it disappear again or have you been stuck with that? This actually makes me quite nervous as I have thought of switching to VDJ, but something like that would simple fuck me up in a livesetting. Makes me somehow overthink my decision to trust and my impulse buy.

At least this could eventually mean that my idea of "no hardware fault" is correct.

Edit:// Just started it again, today everything seems to work fine. I'd still like to find why that happened and what I could do in case of this coming up again. Completely disconnecting my platter control in case of Emergency is not a solution
 
(Not ruling out weird recent behavior with HID) There could be various things in the connection path causing this (e.g. USB cable used for connection, hub (if using one). Maybe start with checking those (swap out the USB cable on the "bad" side, skip the hub)?
Timecode does use a different type of processing, with traditional timecode (CV and actual needles/tone arm), I've had speed issues come up occasionally but that always seemed to be fixed by checking the needles (cleaning it + headshell terminals) and recalibrating.
 
Have you checked that rotation speed was correct ?
VirtualDJ should "understand" what speed the platters are spinning and where you have set the RPM speed on the units.
But just in case, have you confirmed that both software and hardware were using the same RPM setting (and preferably, during troubleshooting, it was set for both at 33RPM) ?
 
thanks for that idea, rpm settings have been correct. Cannot check further atm as the behavior has vanished.
 
As I had some time and the problem just occurred again randomly I captured my problem. I havent changed anything from the last time when the problem just vanished randomly. Plattter speed is unchanged from a standalone start or when using it as Traktor timecode player.

0:13 CH1 RANE12 #1 connected
0:17 CH1 RANE12 #1 disconnected
0:29 CH1 RANE12 #1 connected

0:31 CH2 RANE12 #2 connected
0:38 CH2 RANE12 #2 disconnected
0:43 CH2 RANE12 #2 connected

https://youtu.be/xVayI9t9LXo

Any ideas?
 
I am having almost identical issue. I am playing music in zoom (using Loopback for a virtual audio cable). The song playing starts speeding up beyond what the pitch should be able to play. I do not have any thing connected (stand alone only playing on computer). It doesn't stop on its own. I have to force quit the app to stop and shut it down. This has happened 2 other random times in the past month only but cant seem to find any correlation to what Im doing at the time.
If anyone can please help me to figure this out. I would be GREATLY appreciative. This is starting to get annoying.
Thanks for any help in advance
Computer/App Info:
Mac Mini 2023
Apple M2 Silicone
Sonoma 14.7
Loopback Audio. 2.4.6
Zoom. 6.4.12 (56699)
 
Shades354 wrote :
I am having almost identical issue.


Unless you are using a RANE12 (or two) it's an unrelated issue
So maybe start a new post