Problems Entering Lyrics
In the attached score, I'm having great difficulty entering lyrics. If I enter Ctl L the text field doesn't appear in the area I have designated in Text> Lyrics Odd Lines. Now, with Inspector open, and the lyrics field below the first note of the score, Musescore crashes if I change it to Lyrics Even Lines.
| Attachment | Size |
|---|---|
| It Had To Be You.mscz | 26.13 KB |
Comments
It's not clear what you were expecting - it seems to work as it should for me. You have the vertical offset in the text style set to 3.50sp, which is right in the middle of the staff (nbot sure you'd do that), and to that is added the 2.0sp you have set in Lyrics upper margin, which puts it right below the staff. And that's right where it appears.
As for the crash, can you give precise step by step instructions to reproduce? I added a lyric, changed the Lyrics Even Lines using the Inspector, and it worked fine for me.
In reply to It's not clear what you were by Marc Sabatella
I'm using MS 2.0.0 (6e47f74) on Windows 7 but the score has been created with 2.0.1 (c4e4ed5).
I could not at first not open the file - error message informed that measure 1 was expected to have 3 beats but has 0 (none). Ignoring that message resulted with a score consisting of one empty staff. I edited .mscx file and changed <irregular>1</irregular> to <irregular/> in measure 1 to be able to look at the score.
As for the crash - it happens while editing a lyrics entry and there is no text yet. Once there is some text it won't crash anymore.
In reply to I'm using MS 2.0.0 (6e47f74) by .m.i.r.o.
Well, corrupt files do happen, but the file as posted is not corrupt any more. It would be helpful to understand *how* the corruption happens - if you can find steps to reproduce it. There was a bug that appeared very briefly in the nightly builds after 2.0 that could lead to the pickup measure being corrupt, but that was fixed several weeks ago.
For the crash, I'd still need *precise* steps to reproduce using this score. As in, tell me exactly which note to enter a lyric on, what lyrics to enter, what to do with it once I've enetered it, etc. As I said, the things I've tried have worked fine. We need to be able to reproduce a problem to be able to fix it.
In reply to Well, corrupt files do by Marc Sabatella
I'm not the OP, so I cannot comment how the corruption happened in the first place. I just tried to open the file posted above and strangely could not see any score (see below). I was able to fix it as described above.
Now, to reproduce the crash:
As mentioned before I'm using the regular version 2.0.0 and not any of the nightly builds. Windows 7 and 8.
In reply to I'm not the OP, so I cannot by .m.i.r.o.
Confirmed in latest nightly 32791fd, Windows 8.1u1 64bit.
In reply to I'm not the OP, so I cannot by .m.i.r.o.
If I have the nightly open, and use Open to open "It Had To Be You", the score opens just fine. If I go to Windows Explorer and double click on .mscz file, I get the Corrupt File message and if I select ignore I get what you have pasted here.
In reply to If I have the nightly open, by rwmol
I think that must be two separate files, then - the one you are opening in Explorer is in a different folder perhaps. Feel free to post that version, as opposed to the fixed version, and there is a chance we will recognize the corruption as something caused by a known bug. But in general, in order to fix corruption problems, we need to know how to *create* the corruption - an already corrupted score isn't normally much help.
In reply to I'm not the OP, so I cannot by .m.i.r.o.
Crash confirmed, I will submit bug report and hopefully fix.
EDIT: see #58231: Crash changing text style on empty lyric - thanks for finding this!
In reply to Crash confirmed, I will by Marc Sabatella
I find it rather strange all three scores from yesterday are corrupt. I tried opening all three from Internet Explorer and got the "Corrupt" warning.
In reply to I find it rather strange all by rwmol
What is the common denominator, besides that they are from yesterday?
In reply to What is the common by Jojo-Schmitz
I'm Really not sure. I thought the three were done with the same build. Not so. Two done with c4e4ed5. And one done with aa8b93a.
In reply to I find it rather strange all by rwmol
Which build were you using yesterday? There was a bug in nightly builds starting a few days after the release of 2.0 and continuing for a few days after that that would create corrupt scores fairly often. It should be fixed in current builds, so if you were using one of those buggy builds, that could explain it. See #54176: file corrupted in nightly build
In reply to Which build were you using by Marc Sabatella
I don't know if this will help. If I open the file in my latest build aa8b93a, it will open fine. If I open it in 2.0, I get the corrupt warning. I remember we use to get a warning that the file we were opening was created with a new version.
In reply to I don't know if this will by rwmol
Also, here's a score that was created with yesterdays latest build: aa8b93a
In reply to Also, here's a score that was by rwmol
That score opens fine for me using my own current build (which, BTW, contains a fix for the crash you reported, and this will be in 2.0.1 :-).
I still *suspect* the corruption issues you are seeing relate to that bug that was fixed. When you say a score was "created" with a given build, does that, created from scratch using that build, or perhaps are some of these scores ones that were *begun* with an earlier buid, or built from a tempalte that was created ina n earlier build? That could be relevant too.
If there is a way to create a corrupt score using a recent nightly buil, we definitely want to know in order to be able to fix for 2.0.1, which is becoming pretty finalized at this point. The last one I knew of that anyone would be likely to run into was just fixed a few minutes ago as well :-)
In reply to That score opens fine for me by Marc Sabatella
I created a complete score using my usual template and build 5ab192c. Opened it in Version 2.0 and no problems. See attached score for any verification. Thanks for all the help on this.
In reply to I created a complete score by rwmol
IMPORTANT:
I think I may have found where the problem is (or was).
These scores that showed corrupted had under the first measure properties the "exclude from measure count" box checked. When I uncheck the box and had the pickup measure counted as 1, they no longer were corrupted when opened in Version 2.0. I don't know, this may be a bug. Not sure.
In reply to IMPORTANT: I think I may have by rwmol
It *is* helpful, thanks. It means this is almost certainly related to #54196: Regression after 2.0 - Score with pickup measure are corrupted when reopen. since that is the basic cause. So *if* you were creating scores using a nighly build created between March 30 and April 8, then you are seeing that bug, already fixed. If on the other hand you were creating scores using a nightly build from more recently than April 8 and are seeing corruption on load in 2.0, then I think perhaps there is still a problem we need to understand better, so precise step by step instructions would still be most appreciated.
EDIT: actually, I might be mistaken. I think it is unfortunately *expected* that scores with pickup measures created in nightly builds - including 2.0.1 - may be flagged as corrupt in vanilla 2.0. It looks like this is going to be an incompatibility - the way 2.0.1 writes pickup measures appears incompability with how 2.0 reads them. Still investigating to see if that is truly how it will be. But in any case, I can verify it is currently the case - saving a score with a pickup in a nightly build then loading into vanilla 2.0 does indeed report corruption.
In reply to It *is* helpful, thanks. It by Marc Sabatella
Whew. Then I will consider this investigation over. I now know, at this point, any recent builds with a pickup measure is incompatible with vanilla 2.0. Thanks.
BTW: All my scores that would not open in 2.0 were from recent builds.
In reply to Well, corrupt files do by Marc Sabatella
Apparently I changed the values for Text>Lyrics Top Line and Lyrics Bottom Line Vertical Offset and General>Page>Lyrics Top Margin somewhere along the line. There is no way to return them to default. So what would you recommend the values to be?
In the attached score you will note a lot of notes on the lower ledger lines and beams that extend below the staff. When I enter the lyrics, they collide with the notes and beams making it difficult to edit along the way. I thought the logical way around this would to enter the lyric for the first note of the score then simply use Inspector to lower it's position then continue on entering lyrics but that simply doesn't work. What would be the proper method?
As for the crash, as confirmed by m.i.r.o., if you select the first note in the score, press Ctl L, without entering a letter, in Inspector change to Lyric Even Line, Musescore crashes.
In reply to Apparently I changed the by rwmol
Go to Style > Text > Lyrics Odd/Even Lines and Change vertical offset to 6.00 or 7.00sp (I think 7 is the default).
In reply to Apparently I changed the by rwmol
Change them whatever you like. If you want to see the default for the specific tempalte you used (different tempaltes have different defaults), just create a new score using that template.
To adjust lyrics position, either change the overall default in text style to do it globally, or select the lyrics you wish to move then move them using Inspector (eg, *after* entering them). Especially useful might be to right click one lyrics, Select / More, Same system - that allwos you to adjust all lyrics of a system together, which would be the norm.
In reply to Change them whatever you by Marc Sabatella
Thanks m.i.r.o. and Marc. Both comments were helpful.