Muse Sounds: trill with a grace after followed by a trilled note with a grace before results in never-ending trill
@matthewreadbass is already working on this.
Since Jun 2, 2024.
Assessment
This issue has not been assessed yet.
Description
Issue type
Muse Sounds bug
Bug description
UPDATE
Please see @zacjansheski 's comment for minimal reproduction steps
So as I run into trill lines with ties and trill lines with changing notes and just trill lines over multiple bars a lot, I also run into issues of either the trill not sounding at all past the first note(ties, or at least, I used to run into that, don't know about now) or the trill not changing notes despite being notated as such(definitely still an issue).
As such, my go to workaround for this and other issues with trill lines has been this:
- Add another staff to the instrument with the trill from the Instruments Panel that's for playback only and is to be hidden once the piece is done
- Make the trill in the visible notation staff silent
- Add the trill notes to the playback only staff
- Add individual trill ornaments to each of the trill notes
- Hear what the notation indicates
However, after updating to 4.3.1, one piece where I had to do this workaround went a bit awry in terms of playback. Instead of stopping the trill as it should, it keeps going on endlessly. Muse Sounds Grand Piano only, MS Basic is fine in this regard as is Muse Sounds Violin 1 Solo.
Steps to reproduce
- Open the score
- Select the piano instrument at measure 208
- Hear that the trill is continuing endlessly after measure 211 it's supposed to stop
Screenshots/Screen recordings
https://github.com/musescore/MuseScore/assets/6530761/55b60eca-8af5-411b-a999-bbce46963184
MuseScore Version
MuseScore Studio 4.3.1
Regression
No
Operating system
Windows 10
Additional context
If I set the bar after the trill in the notation staff to be silent, copy it over to the playback staff and then set it to play in the playback staff, the trill stops as it's supposed to.
Score that is affected:
Violin Sonata no. 1 in D Op. 12 no. 1 - copy.zip
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
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.
More from musescore/MuseScore
-
engraving P3 UI
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
needs design
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
community P3 UI
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
regression nightly UX/interaction
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
All issues in musescore/MuseScore
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·