musescore / musescore/MuseScore
Editing volta text should automatically update repeat line/repeat count
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Your idea
After adding a volta, if I edit the staff text to "4.", for example, the repeat list could be automatically updated, so it doesn't have to be manually edited.
If I edit it to "4.5.", the play count on the measure with the repeat barline could be automatically updated to 3*, so it doesn't have to manually edited.
Problem to be solved
Not at all obvious that multiple fields on multiple element types need to be modified to get volta/repeat behaviour that is well-defined based on the volta text.
Prior art
No response
Additional context
Should support any volta text that has contains a series of numbers with any separator, or ranges of numbers separated with a hyphen. E.g.
1.2.3-5,6
1 2-3 4
1, 3&4, 5
If it can't be parsed, no automatic update of the repeat list or repeat count on measures is made. A warning of some sort might be nice.
(*) Note that the "play count" property is incorrect for voltas currently. It needs to be 2 for the repeat to be honoured at all, even though the measure in question is only played once. Hence it needs to be 3 for the repeat to be played twice. What it appears to mean, in most cases, is "the number of times to execute the repeat, plus 1".
At least this proposal will avoid users having to understand that much for simple case...
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
No files, tests, or entry points are named. Start by tracing how volta text is parsed and how the repeat list and measure play count are updated, then verify the examples in the issue, including ranges and separators. Done means valid volta text updates both values automatically while unparsable text leaves them unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100