Cross-staff beaming: layout is not preserved after Save
MS 2.1 on Windows
This problem has occurred with one of the songs transcribed for the Lieder Corpus project (Fanny Hensel: Op.1 No.2 - Wanderlied):
https://musescore.com/openscore-lieder-corpus/scores/5004632
This is how bar 5 was intended to look:
When the transcriber uploaded the file for review, I downloaded the score and opened it in MuseScore. In bar 5 the piano part has three sets of triplets which use cross-staff notation, and the first set was displaying like this with a very strange layout:
The layout of bar 5 was corrected before the score was uploaded to the Lieder Corpus, but it would be good to know what went wrong. Has anyone come across a similar problem with cross-staff beaming, where MuseScore silently alters the intended layout of the beaming? Is it happening because the leading note (F natural) of the triplet is "stem up"?
| Attachment | Size |
|---|---|
| Hensel_Wanderlied_bar_5_as_typeset.png | 18.58 KB |
| Hensel_Wanderlied_bar_5_damaged.png | 8.37 KB |
Comments
Just one hypothesis (I'm not competent) possibly because of the original Format (xml)?
In reply to Just one hypothesis (I'm not… by Shoichi
Shoichi, thanks for the suggestion but there's no xml involved. The starting point for this was a score in MuseScore format with the voice part only but a completely blank piano part. The transcriber set the entire piano part in MuseScore.
In reply to Shoichi, thanks for the… by DanielR
Then how comes that MuseScore records originalFormat to be xml?
In reply to Then how comes that… by Jojo-Schmitz
The score started as a voice only part probably in the key of F. The transcriber added the piano and transposed the score to the proper key. The transcriber also made any necessary adjustments to the lyrics to make them look as they do now.
In general manual adjustments should be remembered when you save, but depending on how the adjustment was performed, if other layout changes occurred as well, sometimes your adjustment may no longer make sense, leading to results like this.
When I look at bar 5 in the score you linked to, all looks fine to me (using MuseScore 2.1). Is there something I would need to do in order to reproduce the problem? It is possible the person who edited the file before you messed something up, but whatever correction you made apparently "took".
In reply to In general manual… by Marc Sabatella
Marc, it's a strange situation. The file looks fine on the transcriber's own PC. Only after an upload did the problem show up on musescore.com here:
https://musescore.com/user/27968710/scores/5026767
After I downloaded the score and corrected the beaming (back to what the transcriber actually did) and uploaded to the Lieder Corpus, the score seems fine and the correction indeed "took". I can't seem to reproduce this...
In reply to Marc, it's a strange… by DanielR
Only thing I can think is that the user who uploaded it was mistaken about it looking fine on his machine, maybe it did at one point but then something changed in the layout and he failed to notice it broke his manual adjustment. Do you know he performed the manual adjustment that led to this?
In reply to Only thing I can think is… by Marc Sabatella
Latest comment from the transcriber:
I have tried very hard to replicate the problem, by typing in that bar several times and editing it in different ways, but I have failed - when I upload it, it stays the same. Perhaps all that is required is to delete the bar, type it in again, and adjust the beam, then see if it uploads without changing.