musescore / musescore/MuseScore
Glissandi where the end note has the "play" flag off play back incorrectly via muse sampler
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Muse Sounds bug
Description with steps to reproduce
- Create a score using, e.g. Muse Strings, with 3 notes all at different pitches and add a glissando line between the first two.
- Confirm the playback is as expected
- Now turn off the "play" flag for the middle note.
- Repeat playback - observe that the glissando is played between the wrong notes. This happens even if a rest is placed before the 3rd note.
Supporting files, videos and screenshots
https://musescore.com/user/7209246/scores/20045797/s/vsx8fa
Comparison of MS Basic gliss to note with play-flag off vs Muse Sounds (happens with almost any library etc.)
What is the latest version of MuseScore Studio where this issue is present?
4.4
Regression
Yes, this used to work in MuseScore 3.x and now is broken
Operating system
Windows 11
Additional context
Have reported via Muse Hub but it does appear to be an issue in the playback rendering code inside MuseScore itself, as it never sends any information about the silent note to the sampler.
Doesn't happen with MS Basic.
Note that what I'm trying to achieve is a glissando that doesn't end on a sustained pitch at all, i.e. a "fall off".
Checklist
- This report follows the guidelines for reporting bugs and issues
- I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
- I have attached all requested files and information to this report
- I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
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
Reproduce the issue with the linked score using the listed steps, then inspect MuseScore's playback rendering code, especially how glissandi and notes with the play flag disabled are represented for Muse Sounds. Done means the glissando uses the intended notes and supports the described fall-off behavior without changing the MS Basic result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100