bpm.tapButton in the common script file is not working correctly

Bug #1532383 reported by Sean M. Pappalardo
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Low
Unassigned
2.0
Won't Fix
Low
Unassigned

Bug Description

bpm.tapButton() in the the common controller script file assumes the "bpm" ControlObject holds the track's native BPM value. Since it no longer does as of 2.0, the algorithm needs adjusting because it currently oscillates pretty badly.

Changed in mixxx:
importance: Undecided → Low
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Hm, but "bpm" has always been the effective deck BPM (after rate adjustment) while file_bpm is the native / detected BPM.

Shouldn't scripts use the bpm_tap CO anyway?

Revision history for this message
Sean M. Pappalardo (pegasus-renegadetech) wrote :

According to the wiki, bpm_tap just changes the BPM value on the track, such as when it's incorrectly detected. bpm.tapButton() is supposed to change the speed of the track (via the rate slider) to match the tapped BPM to synchronize with an external beat.

Revision history for this message
Wihola IT (wihola) wrote :

Hi guys. I wanted to map my TAP button, than I saw JS wiki, than I saw examples, than I saw that this is not working as it supposed to work, than I searched in the Internet, and now I am here.

So what gonna happen with the `bpm.tapButton(deck);` in the common scripts? Cuz now it's working way too weird. It sets my BPM to a random value after second tap from 65 to 215.

tags: removed: script
Revision history for this message
Be (be.ing) wrote :
no longer affects: mixxx/2.3
Changed in mixxx:
status: New → Fix Committed
milestone: none → 2.2.4
Changed in mixxx:
status: Fix Committed → Fix Released
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/8434

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.