-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Fixed bpm.tapButton in common-controller-script.js #2594
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
Can someone else confirm that this works? My controller's mapping is only in master
and I don't want to remove master
-only features temporarily just for testing this PR. I can confirm that the behaviour is currently broken and was quite confusing when creating my controller mapping.
I just tested it and the missed presses seem to be detected very well. However, when I press the button two times quickly, the bpm is set to a high value. From 150 due to an accidental double click up to 500 because of a bounced button. Afterwards, it is hard to get the bpm back down to the desired tempo. |
Thanks for testing. The double press should be caught technically. Can you try to increase the lower value on Line 439 and see if the issue still occurs? |
Maybe we should require tapping at least 4 times? |
Sometimes you do need that instant feedback so I'd rather not wait 4 taps. I also don't see how it would solve the reported problem. |
0.6 seems fine to me. |
@Holzhaus I think 0.6 is still tolerable, wdyt? |
I cannot test because I'd have to backport my controller mapping, but I trust that you tested this thoroughly. Is this ready to merge? |
This has been broken since Mixxx 1.10, right? As this regression has been in a released version, it deserves a changelog entry. Can you add one above the controller mapping entries? |
res/controllers/common-controller-scripts: increased treshold for detecting duplicate taps as the previous threshold was too low and sometimes failed to identify taps as duplicates
I am not able to test the the last 5 or so commits, so I'd appreciate if @goddisignz could take another look before we merge it. |
Added spaces around operators in bpm.tapButton double/missed taps logic
@goddisignz Can you verify that this works well? I'll go ahead and merge then. |
Hi, |
Great, thanks for testing |
Cool, in that case let's merge this. |
closes #2587
I'm sorry for this PR chaos. I made some mistakes that caused git to not cooperate.