musescore / musescore/MuseScore
Loop region length is not recalculated after tempo change/tempo slider change
Open
Nobody has claimed this yet.
P2
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
To Reproduce
Steps to reproduce the behavior:
- Create a simple score with notes
- Enable a loop for two measures
- Put the tempo change to the first measure of the loop region
- Play
- Pay attention to the loop region length
Expected behavior
Loop region length is recalculated after tempo change according to the new tempo
Screenshots
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with a two-measure loop and a tempo change in the first measure, then trace how playback calculates the loop region length and responds to tempo or tempo-slider changes. Done means the loop length is recalculated for the new tempo during playback and the reported behavior no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100