musescore / musescore/MuseScore
Adding options for the harp glissando
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 propose to improve the existing notation for the harp glissando by adding the ability for users to choose the following type of notation:
Problem to be solved
This will allow performers (or just readers) to better perceive in which scale the glissando should sound (rather than peering into the pedal tuning scheme in order to determine this).
Now about the next problem. Recently, I had the need to mark the glissando one rest after the bar-line. I got the desired look, but not the sound, because there is a rest during the glissando. The glissando eventually sounded to the first rest in the next bar, which is not correct.
https://github.com/musescore/MuseScore/assets/134041121/ed9209c6-a7fe-4958-ba77-9869ebb1bb1d
And in this case, there should be a notation for glissando with note-values designations above the staff.
Such note-values should be set automatically, and the glissando should sound not with the duration that indicates the note from which it comes, but with the duration that the glissando line is drawn.
Prior art
As far as I remember, there is 100% such a notation method in Finale.
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 reviewing the existing harp glissando notation and playback behavior in MuseScore. Determine how selectable notation styles, automatically displayed note values, and glissando duration across rests should work; done means the requested notation options render correctly and playback follows the drawn glissando duration.
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
- Needs clarification
- Newbie friendliness
- 20/100