I want to reopen a closed topic that I had created sometime ago. The topic was about djing on the prime go. That I would be in the middle of a mix and pressed the loop rotary knob and the track I meant to loop starts to speed up off tempo and some of the replies I got was that I needed to have the quantize off. Well, recently I did a gig and while all was great. I would go into a mix and pressed the loop knob and was great, but there was other times throughout the gig I press the loop knob and looped track starts to speed up out of control. I did check that the quantize indicator was definitely off. So my question is…Could it be that some of the tracks that I have are not beatgrided at all or not analyzed correctly or do my tracks have to be beatgrided in order to use the loop function?
Every track should be analyzed in engine prior to use, unless it’s a streaming track for example which gets analyzed on the player when loaded.
ok understandable. once analyzed, does all my tracks have to be beatgrided to use the loop knob function?
For auto loop (the knob) the BPM being right is the key, providing you have the timing skills to set it at the right point the grid can still be misaligned as you have started the loop yourself. If quantise is on it’ll move the loop to a grid marker, meaning both BPM and grid have to be correct for it to work.
Manual loop you can obviously set it manually which also takes practise.
I don’t use quantise at all as I prefer to have the control myself.
ok, but not having the bpm or the grid markers set correctly would be the reason why a track speeds forward out of control when the auto loop is engaged??
Can you share the track and some screenshots of the grid itself, the bpm etc, or possibly even a video of it happening. That will help people determine the cause of the issue.