登录:     

Forum: General Discussion

Topic: Sync Behavior
Hi everybody,

I'm on Rane Performer with the most recent firmware, VDJ V2025 m b8528 and Mac M3, 16 GB Ram, Mac OS Sequioa 15.3.2 . I'm observing that pressing the sync button on one deck while another track is playing is not going to the tempo of the other song, sometimes instead going to a tempo much higher or lower than the other song. Anything I may be missing here? I don't recall seeing this before. Behavior seems perfect with using it stand alone without the Rane Performer connected.

Also, I'm still seeing initial latency on the platters when spinning to a different part of a song. The wave start moving only after a few spins on the deck. Once its starts moving it's fine. Any ideas? I don't notice this on other apps. Just wondering if I should be doing something different.

Thanks!
 
发表时间 Fri 21 Mar 25 @ 4:39 pm
I’m seeing something related but not the same as you. I need to check my version numbers today.

My Rane performer is automatically synching to the master deck when I press the play/stop button. When I first load the song, the bpm is set to its normal BPM. When I press the play button it synchs. And I have all the “auto” options turned off.

I have another controller (707m) and with that one it’s not automatically synching and behaves the way I expect.

I am also going to try to reset VDJ by moving the settings file and then see if the behavior is the same once I unset the auto synching features. Have you tried this also? It could be some combination of options causing the issue.
 
 
How is quantize the issue? Is there big in quantize?
 
Update: for the synch issue, I have narrowed down the problem to custom mappings.

I started with a default settings file and added sections from my custom settings until I could reproduce the synch issue.

It’s being caused by the <controller> section where there is a reference for the RPerf and it points to the custom mapping that was created.

I know I adjusted a few behaviors to make them match my 707 behavior, and so I’ll delve into it tomorrow and report back exactly which mapping setting is causing the issue.
 
musicbycsharp wrote :
How is quantize the issue? Is there big in quantize?


Quantize, when ON, enables several automatic/smart features.
One of the features that get activated when quantize is on, is "smart play"
"Smart play" snaps the CBG of the track you press play on, to the CBG of the master deck (based on quantize beats value)
Also, if the pitch change required to sync the BPM of the track to that of the master deck is less than 10%, it will also match the BPM.

That's why Quantize can change the BPM of your track when you press play. Because the CBG of the deck effectively auto-syncs with the CBG of the master deck as part of it's quantized operation.
 
Hoe krjjg ik ook nog de phrase sync vervolgens gekoppeld aan mijn Quantize knop van de pioneer FLX 10?
 
@emulder you have to go into the mapping for the controller and change the code for that button.
 
PhantomDeejay wrote :
musicbycsharp wrote :
How is quantize the issue? Is there big in quantize?


Quantize, when ON, enables several automatic/smart features.
One of the features that get activated when quantize is on, is "smart play"
"Smart play" snaps the CBG of the track you press play on, to the CBG of the master deck (based on quantize beats value)
Also, if the pitch change required to sync the BPM of the track to that of the master deck is less than 10%, it will also match the BPM.

That's why Quantize can change the BPM of your track when you press play. Because the CBG of the deck effectively auto-syncs with the CBG of the master deck as part of it's quantized operation.


Thank you. It looks like the culprit for me is that quantize_all is being used. Quantize_all is a macro setting that controls a bunch of other settings:

Quantize_loop
Quantize_setcue
Quantize_scratch
Auto_Synch on play

And probably other stuff. The documentation for the verb quantize_all just says turns off/on all quantize settings which is not helpful.

For me I’ll be reprogramming the quantize button to just set the quantize loop and setcue because that’s the only time I really use anyway.