musescore / musescore/MuseScore
Implement an auto-assignment feature for sound flags based on stave text parsing
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
For some reason*, sometimes it happens that Muse Sounds instruments have to be manually reassociated with certain staves. Incidentally, it generates an often massive number of sound flags to manually reassign, and the process just basically consists of the following algorithm: scroll though the entire score progressively, and each time you encounter stave text with specific words like "ordinary", "classic phrasing",..., open sound flags and click the button with the same wording.
https://github.com/user-attachments/assets/6763dc2d-8fce-4064-9d80-4446f6d294c2
Having a feature do it at once (upon request!) would save a great amount of time in this instance, and would extend (or could be extended to) similar features on text parsing, e.g. #25396.
Algorithmically-wise, it could look like this:
- for each stave that uses Muse Sounds, gather all stave texts on each stave
- for each of them, parse/retrieve those with a perfect match with the key words in the list of sound flags available for the instrument selected on that stave (special case to consider for text with multiple sound flags separated by commas).
- auto-assign them (transform those stave texts into sound flags).
Problem to be solved
See above.
*Typical common mishandling of MS4 in three steps: Muse Sounds disappear for some reason; the user isn't alerted and saves a file unintentionally with all sounds turned to MS Basic; then Muse Sounds reappear later, but since the user saved their file with MS Basic, all the sounds use MS Basic now. All corresponding sound flags are lost.
Prior art
No response
Additional context
(It could lie somewhere in the "Tools" menu.)
Checklist
- This request follows the guidelines for reporting issues
- I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests
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.
Assessment
This issue has not been assessed yet.