We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Engraving bug (incorrect score rendering)
ACTION
RESULT
OS: macOS 14.6, Arch.: arm64, MuseScore Studio version (64-bit): 4.4.3-242971445, revision: github-musescore-musescore-eb6b367
TEST Piece in 7:8 From Festival copy.mscz.zip
I was unable to check
MacOS 14.6
I am able to restore the page shape by deleting the Title text. BUT when I add the Title back in, the error returns.
I was able to correct the error by deleting the Title Frame and adding back in the Title, Composer and a Subtitle.
The text was updated successfully, but these errors were encountered:
Here's a way to reproduce this bug
Regression occured between 4.4.0 and 4.4.1
Sorry, something went wrong.
FYI @Eism Reminds me of #25076
Eism
No branches or pull requests
Issue type
Engraving bug (incorrect score rendering)
Description with steps to reproduce
ACTION
RESULT
OS: macOS 14.6, Arch.: arm64, MuseScore Studio version (64-bit): 4.4.3-242971445, revision: github-musescore-musescore-eb6b367
Supporting files, videos and screenshots
TEST Piece in 7:8 From Festival copy.mscz.zip
What is the latest version of MuseScore Studio where this issue is present?
OS: macOS 14.6, Arch.: arm64, MuseScore Studio version (64-bit): 4.4.3-242971445, revision: github-musescore-musescore-eb6b367
Regression
I was unable to check
Operating system
MacOS 14.6
Additional context
I am able to restore the page shape by deleting the Title text. BUT when I add the Title back in, the error returns.
I was able to correct the error by deleting the Title Frame and adding back in the Title, Composer and a Subtitle.
Checklist
The text was updated successfully, but these errors were encountered: