musescore / musescore/MuseScore
Automatically keep ties/slurs synced with Melismas
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
I work with a lot of choral music and what often bugs me are missing or faulty melismas. In my opinion MuseScore should be able to create these (or at least extend) them on its own just by checking ties. So whenever a note with a lyric syllable attached gets tied, the lyric shouldbe extended automatically by a melisma.
Of course there needs to be an opportunity to manually change or suppress that mode, but as far as I am concerned this is a desired behaviour most of the time.
One could even think of a sync both ways: When a melisma is added, the corresponding notes could be tied/slurred automatically (if applicable).
Quick Side Note: To keep a clean overview in my choir scores I tend to make all (or at least the really long) slurs invisible most of the time. This makes sure, to not be mistakenly interpreted as a staffline or a tie. As the melisma is already in place, the slur only has redundant information and only clutters the view for e.g. a passage where voices sing oo_______ whole notes over several bars. Maybe that could be kept in mind during implmentation (workaround: Select All Similar → Hide).
Problem to be solved
Mostly for scanned or imported music, melismas are completely missing or faulty. I need to redo nearly the entire score's lyrics, which is a tedious task (also because melisma-creation is a bit laggy). I am convinced that this could be taken over by MuseScore on its own quite easily.
See the following example, where it is totally clear, how melismas should be placed.
Prior art
No response
Additional context
Found this somewhat relatied Issue: https://github.com/musescore/MuseScore/issues/17753
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.
Research direction
No implementation files, tests, or entry points are identified. Start by reviewing related issue #17753 and the tie/melisma behavior described here; done would require an agreed design for automatic synchronization and manual override or suppression.
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