Marcato articulation incorrectly oriented
I don't know why, but it appears to be an only marcato articulation issue. Everything else is fine.
Is this enough of a problem for the issue tracker?
MuseScoreNightly-2018-11-27-1742-master-2ad0757
I don't know why, but it appears to be an only marcato articulation issue. Everything else is fine.
Is this enough of a problem for the issue tracker?
MuseScoreNightly-2018-11-27-1742-master-2ad0757
Do you still have an unanswered question? Please log in first to post your question.
Comments
This is by design:
Elain Gold: Behind Bars. Faber, 2011, p. 117 "The strong accent usually goes above the stave, regardless of stem direction, because of the amount of space it occupies..."
But if you realy want, you can enforce it below chord/staff in the inspector.
In reply to This is by design: Elain… by tobik
I have no idea who Elaine Gold is, but reading articulation off of notes that low is difficult when they're on opposite sides of the staff. And Bernstein's Goetterdaemmerung piano score appears to disagree.
Also, I didn't see a way to change it. Orientation in in the inspector only changes the direction it's pointed, not the actual positioning. So how do you do that? Thanks.
Edit: I went and looked for the NY Phil's Sousa parts as well, since I couldn't think of anything more likely to have marcato marks than a Sousa march. The trombone and tuba parts also have, as expected, marcato markings according to the stem direction, following the note around.
In reply to I have no idea who elaine… by Laurelin
"Behind Bars" is the accepted reference for notation here.
Set Anchor: Below Chord
Are there opinions from anybody else?
In reply to I have no idea who elaine… by Laurelin
Elaine Gould wrote Behind the Bars that the MuseScore developers adopted as the standard to resolve notation issues such as this.
In all versions, you can use the inspector to change the anchor position which defaults to Chord Automatic.
In reply to Elaine Gould wrote Behind… by mike320
That's going to be a surprise for most - the 2.3.2 option has a gray font, so I just assumed it was unchangeable, and never played with it.
Thanks!
In reply to That's going to be a… by Laurelin
The use of the gray font in previous versions were a mystery to me also.