Comment 0 for bug 1424168

If the Quantize feature is activated, actions like setting loops and cues currently snap to 1 beat ( the white lines).

Current behavior
==============

(Hot)hotcues
--------------------
If the playposition is less then halve the way trough between two beats the action is performed on the PREVIOUS beat (Snap to nearest beat).

Loops
---------
The action is ALWAYS performed on the PREVIOUS beat, no matter how far the playpositions is between two beats (Snap to nearest beat)

Issues
=====

(Hot)cues
--------------
* Always set on a full beat, the Dj is bound to Mixxx` internal decision.

Loops
---------
* Always start on a full beat, the Dj is bound to Mixxx` internal decision.
* You can`t set manual loops smaller then 1 beat.
* Automated loops can easily get out of sync, because is the playposition more then halve the way trough two beats, the loop starts on the PREVIOUS beat. Just start 2 tracks simultaneously and hear them running in sync. Now press the 4-bar automated loop button right in the moment before the playposition is at the next beat marker. They are now out of sync, with every run of the loop a bit more.

Proposal
=======
* Allow finer granularity so that we can sync to up to 1/8 ticks in between two beats (configurable?).
* Unify behavior for (Hot)cues and automated Loops (Snap to nearest tick). We do this already for not automated (manual) loops.
* Is a new automated loops set and snapped to the to nearest coming tick ( > halve way trough 2 ticks), don`t instantly jump to the loop-In point. Normally continue playback to the loops end first, then start looping.

Maybe i missed some discussions about the decision to restrict it to 1 beat, but i think it it puts unnecessary limits to looping and that we can do better.

Thanks for listening.