Notes continue to play during playback

• Jan 9, 2021 - 15:43
Reported version
3.5
Type
Performance
Severity
S3 - Major
Reproducibility
Randomly
Status
closed
Regression
No
Workaround
Yes
Project

What was done to create the fault in the first place is not known, but possibly to do with the entry of a tied note. The problem having arisen, it is now present in various forms: Playing the score with no instruments muted, the notes in stave 2 continue to sound from the last crotchet of bar 12 onwards. If stave 2 is muted the score plays correctly. If staves 1 and 3 are muted, then the score plays incorrectly from the start. If stave 3 is moved up to become stave 2, then the fault is transferred to that stave. The workaround is to have an empty stave 2. Deleting the contents of the bars, and deleting the bars themselves, at this point of the score makes to difference, it just happens from the succeeding bars onward. This has previously happened to me awhile ago in an earlier version. I have tried the same file on my macbook air and it worked fine. Possibly connected is the fact that I have to "Restart audio and MIDI devices" at the start of every session, otherwise Musescore stops responding very shortly after I start doing anything, and have to close it down and start again. I am running Windows 10.
The_Lord_bless_you_and_keep_you-Rev1.mscz


Comments

Status active needs info

I loaded this into the current version of MuseScore - 3.5.2 - and didn't hear any problems around measure 12. Can you give precise steps to reproduce the issue you are hearing? Also, are you by chance using a non-standard soundfont or external MIDI output?

In reply to by Marc Sabatella

Hi Marc. To make it happen I was simply playing the score from anywhere. If started before bar 12 it would only start happening at bar 12. If started after that bar it would happen straight away - unless both staves 1 and 3 were muted, in which case it started straight away. I have since re-started Musescore, deleted the empty stave 2 and it is now playing perfectly correctly. A second score I created during the same session was also exhibiting the same problem, but in the new session it too is now fine. I am using the standard soundfont and MIDI output.