Skip to content
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

Closed
Jojo-Schmitz opened this issue Nov 16, 2021 · 7 comments

Comments

@Jojo-Schmitz
Copy link
Contributor

Jojo-Schmitz commented Nov 16, 2021

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:

  1. in 3.6.2 have a score with lyrics and melismas.
  2. Make sure at least one of those melismas crosses a system break (with the syllable before it being on the last note of the previous measure).
  3. File > Save online.
  4. See the error when viewing the score on musescore.com.
  5. (Alternatively use the artifacts from [MU3] Fix GH#7449: Almost everything suitable for 3.6.3 or 3.7.0 #9000 and see the issue even locally).

Expected behavior
The lyrics' right edge should not protrude into the page border

Screenshots
image

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

@Jojo-Schmitz
Copy link
Contributor Author

Jojo-Schmitz commented Nov 16, 2021

There's another and related issue, see #9000 (comment)
There lyrics with some (negative) ticks and/or ticks_f like this

          <Chord>
            <durationType>16th</durationType>
            <Lyrics>
              <ticks>-1800</ticks>
              <ticks_f>-15/16</ticks_f>
              <text>lyric</text>
              </Lyrics>
            <Note>
              <pitch>62</pitch>
              <tpc>16</tpc>
              </Note>
            </Chord>

settings destroy the layout quite badly.
It is completely unclear though (to me at least), how those came about.

@Jojo-Schmitz
Copy link
Contributor Author

Jojo-Schmitz commented Nov 16, 2021

Examples for both issues in https://musescore.com/user/23930/scores/7122651/s/LO8Qg1
1st issue at several places, measures 5, 15, 18, 21, 26, 51, 54 (here the Dynamics are manually set off, so not part of the problem).
2nd issue at measure 28.

@gwillen
Copy link

gwillen commented Nov 16, 2021

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.

@Jojo-Schmitz
Copy link
Contributor Author

Jojo-Schmitz commented Nov 16, 2021

The workaround for that 2nd issue is quite easy: double click the next lyrics after the broken one, Press Shift+Space to move to the previous note, press _ to add the missing melisma and the layout looks fine again (well, except for the 1st issue)

@Tantacrul
Copy link
Contributor

@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?

@Jojo-Schmitz
Copy link
Contributor Author

This might meanwhile be an issue with 3.6.2_backend_musicxml rather than 3.6.2_backend and as such no longer actual?

@Tantacrul
Copy link
Contributor

OK, closing for now (unless there is an objection). I don't see us fixing this in favour of focusing on uploads from MS4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants