Honestly I can’t believe djay still hasn’t sorted out proper snap/quantize… If any dev reads this, here is what needs fixing, I’ve been asking about this for ages… You can test yourself:
Say I have a track playing and another track paused at a cue point. Sync turned on for both tracks. I am free to trigger the paused track with whatever timing I like, tapping out a rythm etc, and although it will initially launch with the timing of my press, it will then align/snap with the NEAREST beat of the other (already playing) track on the first beat after launching. That’s all fine. We really should be able to have our cue triggers quantized at the point of launching but I can live with it snapping at the first beat after launch.
But now let’s say I have both tracks playing. If I launch a cue in one of the tracks it no longer snaps to the NEAREST beat - instead it now snaps to the NEXT beat. This means if my timing is late by just a few milliseconds, the track will be nudged forward out of sync by one whole beat.
There is no reason anyone would ever desire this behaviour, users would always instinctively expect that any sync feature would correct timing to the beat NEAREST to the trigger.