-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[MU3.6.2_backend Issue] Lyrics with a melisma across a system break protrude the system, into the page border #9747
Comments
There's another and related issue, see #9000 (comment)
settings destroy the layout quite badly. |
Examples for both issues in https://musescore.com/user/23930/scores/7122651/s/LO8Qg1 |
Original reporter here -- the score (with negative tick values) was created in a release version of MuseScore 3, "3.6.2.548021803". Unfortunately, my friend who created it has no idea how she managed that, and I have no insight into reproducing that specific aspect. |
The workaround for that 2nd issue is quite easy: double click the next lyrics after the broken one, Press |
@oktophonie - is this one we think is fixed in MS4? Or will we (as I suspect) need to wait for MuseScore.com uploads before knowing? |
This might meanwhile be an issue with 3.6.2_backend_musicxml rather than 3.6.2_backend and as such no longer actual? |
OK, closing for now (unless there is an objection). I don't see us fixing this in favour of focusing on uploads from MS4. |
Describe the bug
Lyrics with a melisma across a system break protrude the system, into the page border
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The lyrics' right edge should not protrude into the page border
Screenshots
Desktop (please complete the following information):
Additional context
The culprit probably is #8296, but could also be #8176 or #8461
As far as I can tell none of those have yet been ported over to master, but as soon as that happens, that branch would also be affected. See also #9581, the first part of porting all those 3.6.2_backend fixes over to master
The text was updated successfully, but these errors were encountered: