-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editing notes in repeated section after arpeggio kills playback. #20752
Comments
@DmitryArefiev @zacjansheski pls check |
FWIW, I was able to reproduce this although the specific symptoms seemed to vary - sometimes it was other notes within the volta that failed to play, sometimes it was notes at the beginning of the following repeat, sometimes it was notes in the next volta. But I could only reproduce with this score - I didn't succeed in reproducing the problem from scratch. |
Would like to add that the issue is present on the 4.2.1 nightly portable build.
I haven't experimented much, but it mostly happens around trills and grace notes. |
Just for visibility/reproduction purposes: video1962262906.mp4 |
I haven't been able to reproduce outside of this score, but definitely still happens in master. Would like to find a more minimal example. @RomanPudashkin Reminds me a bit of #19264 |
arpeggio_playback_issue.mp4 |
Looks like this is a regression between 4.1.1 and 4.2.0 |
…on't mess up ScoreChangesRange::tickFrom
…on't mess up ScoreChangesRange::tickFrom + removed code that did nothing
…on't mess up ScoreChangesRange::tickFrom + removed code that did nothing
Issue type
General playback bug
Bug description
Updated: See @mercuree 's video
Editing notes in repeated section after arpeggio kills playback.
Upon editing a note in any fashion (moving a note up or down in pitch, adding a glissando, etc.) underneath a volta, all notes following the edited one are muted, however do not show they are muted in the properties window. The notes do not play on playback, nor do they display any volume when opening the mixer. This issue is temporarily fixed by restarting Musescore. Also can be temporarily fixed by un-checking and re-checking the "Play" checkbox in the properties window of the note.
Volta Bug.zip
Steps to reproduce
Screenshots/Screen recordings
https://youtu.be/O4Nyv4MMCp0
MuseScore Version
MuseScore version (64-bit): 4.2.0-233521124, revision: github-musescore-musescore-eb8d33c
Regression
I don't know
Operating system
Windows 10, 64 bit
Additional context
No response
The text was updated successfully, but these errors were encountered: