You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Musescore 4.3.1-nightly, when editing part of the accordion staff with barlines disabled, empty space after the score's last measure is created whenever a new note is added. This issue was present in the previous 4.3 and 4.2.1 versions as well.
Steps to reproduce
Open a new score with the Accordion instrument.
Disable Staff/Part Properties->Show barlines on the second staff (bass).
Start adding any note on either staff and see empty space being created after the end of the last measure of the score.
Screenshots/Screen recordings
2024-05-15.19-37-28_conv.mp4
MuseScore Version
OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.3.0-241360504, revision: github-musescore-musescore-3121620
Regression
Yes, this used to work in a previous version of MuseScore 4.x
Operating system
Windows 10
Additional context
This issue has also been present since MuseScore 4.2.1.240230937, which I had tried previously.
Before that, I was on 4.1.1.232071203, where this issue did not occur.
I just verified that single-staff instruments (e.g., flute) do not experience this issue.
If both staffs of the accordion have the barlines disabled, this issue also does not appear, but as soon as one of them is enabled (either one), this occurs - see below.
Issue type
Engraving bug (incorrect score rendering)
Bug description
In Musescore 4.3.1-nightly, when editing part of the accordion staff with barlines disabled, empty space after the score's last measure is created whenever a new note is added. This issue was present in the previous 4.3 and 4.2.1 versions as well.
Steps to reproduce
Screenshots/Screen recordings
2024-05-15.19-37-28_conv.mp4
MuseScore Version
OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.3.0-241360504, revision: github-musescore-musescore-3121620
Regression
Yes, this used to work in a previous version of MuseScore 4.x
Operating system
Windows 10
Additional context
This issue has also been present since MuseScore 4.2.1.240230937, which I had tried previously.
Before that, I was on 4.1.1.232071203, where this issue did not occur.
Score from Video above:
issue_space_end_of_score.mscz.zip
Diagnostics File:
issue_space_end_of_score.zip
The text was updated successfully, but these errors were encountered: