Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

track out of sync after overview seek, quantisation on. #9044

Closed
mixxxbot opened this issue Aug 23, 2022 · 5 comments
Closed

track out of sync after overview seek, quantisation on. #9044

mixxxbot opened this issue Aug 23, 2022 · 5 comments
Milestone

Comments

@mixxxbot
Copy link
Collaborator

Reported by: daschuer
Date: 2018-01-02T23:13:49Z
Status: Invalid
Importance: Medium
Launchpad Issue: lp1740958


If you enable quantisation,you can start a track in sync with a playing track.
If you now seek the track with there is always the same small offset (double base) between both tracks.
If I disable quantisation I get a random offset as expected.

It would be also cool, if we not just sync the beat but also the bar.
How about using a n x beatjump length?

@mixxxbot
Copy link
Collaborator Author

Commented by: johanLsp
Date: 2018-01-14T15:10:55Z


I couldn't reproduce this.
I loaded 2 tracks with quantization enabled and tempo synced (but not locked), and moved around both tracks using the overview panel : beats stayed synced throughout.

There's though an issue with effects using quantization (Echo, Tremolo), which are getting out of sync when moving manually through a track.

Anyway, being able to move by a multiple of n beats (4 seems right, maybe 8) could be useful to stay rhythmically synced.

@mixxxbot
Copy link
Collaborator Author

Commented by: johanLsp
Date: 2018-01-14T15:53:26Z


My bad, there's indeed a small offset after moving around

@mixxxbot
Copy link
Collaborator Author

Commented by: Be-ing
Date: 2018-03-19T13:25:31Z


I suspect that fixing this will require risky changes to how quantization and track transport are handled, so I'm retargeting this to 2.2.

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2018-11-11T20:34:33Z


Interestingly I cannot confirm this with Mixxx 2.1.5.
@johan: are you able to reproduce this with this version?

@mixxxbot
Copy link
Collaborator Author

Issue closed with status Invalid.

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
@mixxxbot mixxxbot added this to the 2.2.1 milestone Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant