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
Latency correction #5967
Comments
Commented by: Pegasus-RPG That's a good idea and I think we can make it work without too much trouble. I really like the "human latency correction" idea! Not sure how useful it would be in practice, but still interesting to see if it helps anyone. |
Commented by: ferranpujolcamins If Mixxx asks for the user to do this "human latency correction" not one but many times, the program will be able to "learn" how that particular human responds and help him to stay in sync. It would be kind of an abstraction: the user could be able to push the play button when he feels it in time without the need of thinking that there is a latency. |
Commented by: daschuer Now we have a quantization play. Can we mark this a fixed? |
Commented by: daschuer No responds = Yes :-) |
Commented by: ywwg yeah quantization play makes this irrelevant. |
Issue closed with status Fix Released. |
Reported by: ferranpujolcamins
Date: 2011-08-16T19:33:31Z
Status: Fix Released
Importance: Wishlist
Launchpad Issue: lp827599
It would be nice if Mixxx would have a latency correction function.
For example, assume you have 21ms of latency, then a track will start to play 21ms after the point it was stopped. This way you can start your track in sync much easier.
Not only could this correct sound output latency, but also controller input latency and even "human" latency. It could be done with a latency test placed in preferences. Mixxx would play a beep and measure the time that takes the user to use the controller or the keyboard and the time it takes to receive that message.
The text was updated successfully, but these errors were encountered: