Odd short-to-long instrument naming behavior, like a Section Break is being inserted.
MuseScore 3.5.2, Windows 10
In the attached please see page 106 measure 379. In the first system, notice that the "short" instrument names are used on the left.
At measure 380 make an edit to either the System Text at the top or the Staff Text above the Sieglinde staff.
As soon as an edit is made to either, the instrument names change to the "long" version and the brackets become a bit off, it's as if a Section Break (instead of a System or Page Break) were inserted at the end of page 105.
Next, save & close the score; on re-opening the score is back to "short" instrument names.
Any ideas why?
Thanks,
| Attachment | Size |
|---|---|
| Die Walküre, Act III Scene I.mscz | 1.25 MB |
Comments
I can confirm the issue but not explain
In reply to I can confirm the issue but… by Jojo-Schmitz
I don't know if this has been reported before, but the cause is the interaction between the vertical frame (the trigger) and the instrument names when entering staff text or system text, but also chords (Ctrl + K), lyrics (Ctrl + L), figured bass (Ctrl + G), maybe others.
If it has not been reported (?), it is probably because this glitch resolves itself on Saving.
In reply to I don't know if this has… by cadiz1
Thanks for this extra piece of information.
In reply to Thanks for this extra piece… by marty strasinger
Shoichi had provided guidance on how to get the link to the Issue to appear properly, however the instructions were not clear to me; apologies Shoichi!
https://musescore.org/en/node/313939
In reply to Shoichi had provided… by marty strasinger
[#313939] -> #313939: Odd short-to-long instrument naming behavior, especially when a vertical frame is present
In reply to [#313939] -> #313939: Odd… by Jojo-Schmitz
Actually now #288098: Long instrument names appear in first system after vertical frame
In reply to I don't know if this has… by cadiz1
Can you attach your test score to the issue? i tried reproducing this from scratch but could not. not sure what's different about your score from mine, but having a simple test score like this would make debugging much easier.
In reply to Can you attach your test… by Marc Sabatella
You should be able to access the score from the original post, but please find here again just in case.
As cadiz1 noted, it is apparently related to the presence of a vertical frame at the top of the score.
In reply to You should be able to access… by marty strasinger
Sorry, I was talking to cadiz1 :-). I can reproduce with your score, but it's so big and complex it's hard to debug
with. Unfortunately when I try to create a smaller test example, it doesn't show the problem.
In reply to Sorry, I was talking to… by Marc Sabatella
If you think it’s big and complex now, wait until I add scenes 2 and 3. Scene 2 not so bad, about 40 (wagner-size) pages. Scene 3 will be the killer, although I already did the last half of scene 3 previously in MS 2.x and should be able to use lots of copy/paste. Hopefully done late next year! If note entry bogs down (not really an issue yet) I will do copy paste from a simpler score. My visual-based proof reading of scene 1 is complete. Next step is ear-based at about 60% normal speed for wrong notes I missed visually, and adjusting tempos which are presently all 80 bpm. Then posting on musescore.com.
Many thanks to you, Jo-jo, mike320, jeetee and many others who helped with the rough spots.
In reply to Sorry, I was talking to… by Marc Sabatella
Try to add text to measure 6:
Add_text.mscz
In reply to Sorry, I was talking to… by Marc Sabatella
I came across this fault while correcting a score submitted by a transcriber: instrument names suddenly appeared unbidden at the start of a system. This score doesn't use Short Instrument Name, so I think it must be the Long Instrument Name which popped up. The fault seemed to happen whenever I made a small edit to notes, articulations or dynamics on page 2.
There is no vertical frame involved where the problem occurred (on the first system of page 2). But I noticed that the transcriber used a lot of spacers on this page. By removing all the spacers I got the fault to go away.
Attached is the original transcriber's score, before I made any changes.
In reply to I came across this fault… by DanielR
There might not be a frame on the top of page 2, but there is on the bottom of page 1, so I'm pretty sure that's it. I can certainly reproduce the original problem in this score using 3.5, but not with my build using the fix I just implemented for the frame issue. I think the spacers are a red herring. The reality is, certain layout operations (ones resulting in a "partial layout") trigger the bug, whereas ones that trigger a full layout clear it (which is why saving/reloading is a workaround). Your spacer changes probably had a similar effect.