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

Adjust BPM by uneven factor / re-enable constant tempo broken when assume constant tempo is disabled. #13776

Open
LeonTheOriginal opened this issue Oct 17, 2024 · 2 comments

Comments

@LeonTheOriginal
Copy link

LeonTheOriginal commented Oct 17, 2024

Bug Description

When "Assume constant tempo" is disabled, the uneven BPM multiplication options (2/3, 3/4, 3/2, 4/3) are not working. (Double / Halve are working normally.)
Also (re)enabling "Assume constant tempo" for a single track in its properties is ignored unless the BPM also has been edited manually.
This bug seems to be introduced with version 2.4.x. Version 2.3.6 is unaffected.

Version

2.4.1

OS

Windows 10

@daschuer daschuer added this to the 2.4.2 milestone Oct 20, 2024
@ronso0
Copy link
Member

ronso0 commented Oct 21, 2024

When I try to reproduce I see these warning being logged

warning [Main] Marker with 117 beats till next marker cannot be scaled by 0.75
warning [Main] Marker with 67 beats till next marker cannot be scaled by 0.666667
warning [Main] Marker with 117 beats till next marker cannot be scaled by 1.5

However, this has not been changed by the last commit that touched the scale function 3 years ago 9dbe081
which makes me think that

Version 2.3.6 is unaffected

is true for tracks where by chance the beat counts allow division/multiplication.
Did you test 2.4.1 and 2.3.6 with identical tracks?
(though even that may mean nothing if the beat analyzer yields different results)

@ronso0
Copy link
Member

ronso0 commented Oct 21, 2024

Also (re)enabling "Assume constant tempo" for a single track in its properties is ignored unless the BPM also has been edited manually.

Yes, the UX with this option should be improved.
The checkbox is active (can be changed) only if the track has a beatmap (last analysis was with const tempo off).
Un/ticking the box alone does nothing:

  • if you tick it, you need to tap the BPM in order to create a beatgrid
  • if you untick it, the track has to be re-analyzed to get a beatmap

For both convertions, the track menu's "Re/analyze" actions are more suitable.
Shall we add these àctions to the BPM tab in Track Properties?

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

3 participants