musescore / musescore/MuseScore
Saving a selection should add a tempo mark to the first bar of the selection in order to adapt the tempo of the original score
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
See title.
Problem to be solved
MuseScore does not yet support audio export for a loop range
so that you always have to save a selection first.
If you do so and save a selection
previous tempo changes of the original score are lost
and you have to take another step.
It would be nice if MuseScore could automatically take that step for you.
Prior art
No response
Additional context
No response
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 locating the selection-save flow and how existing tempo changes are represented in the original score. Confirm that saving a selection adds a tempo mark at its first bar and preserves the original score’s tempo behavior; the issue names no file or test to begin with.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100