MS3 -- why are the beams for M12 cello in M4?

• Feb 13, 2019 - 03:54

OS: macOS 10.14, Arch.: x86_64, MuseScore version (64-bit): 3.0.2.20666, revision: 8ca4d2c

See m. 12 and m. 4. Why are the beam offsets 100 times what they should be (I never touched them; I did do "X" a couple of times).

If I try to make them .25, when I save the file they go back to 25.

Attachment Size
Chop-Qtt.mscz 23.61 KB

Comments

In reply to by Marc Sabatella

Now that I think about it, the original posted score suffered (what I considered) wrong-direction stems all over it. Almost certainly, the import from XML inherited explicit stem directions that survived far too long. I wonder if that is one or more bugs (removing them at XML import time unconditionally can't be right, though). And many newbies who don't understand MS voices have 1 & 2 in the bass clef reversed, and tinker with stem directions throughout, so resetting them all to "auto" at MS2 import time is dangerous, too. It's easy enough to "auto" them all, but even to know that that option exists requires experience and sophistication.

In reply to by [DELETED] 1831606

MusicXML files normally encode stem direction and we honor that. This is what you want occasionally - so you can get more consistency when moving files between applications - but not so good if you then plan to edit the music and find your stem directions locked. Maybe we consider a dialog not unlikely the one that appears on import of MuseScore 2 scores, offering to reset things? That or we add an option no one will likely find hidden in Edit / Preferences / Import.

Do you still have an unanswered question? Please log in first to post your question.