musescore / musescore/MuseScore
Percentages displaying inaccurately w/ large numbers
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
UI bug (incorrect info or interface appearance)
Description with steps to reproduce
This appears to occur for every value I have tested with percentage input (rit., fermatas, Measure width)2. Start a new file
- Place a fermata
- Under Properties > Playback set the time stretch to a value
- Observe the value snap to some other smaller amount (100% for fermatas, 0% for width)
- Note that the value appears to be updated internally
- Note that the value properly displays upon reopening the UI element.
Supporting files, videos and screenshots
N/A
In which versions of MuseScore Studio is this issue present?
Present on 3c5fb261da (current master HEAD) at time of writing
Regression
Yes, this works in the latest released version and is broken in the nightly builds
Operating system
MacOS 26.2
Additional context
No response
Checklist
- This report follows the guidelines for reporting bugs and issues
- I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
- I have attached all requested files and information to this report
- I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
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
Reproduce the issue in a current MuseScore Studio build by changing percentage values for fermata playback time stretch and Measure width, then compare with the latest released version. Trace the UI path responsible for displaying the edited value; done means large percentage values remain accurate immediately after editing and still display correctly when reopening the UI element.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100