Hook of note with value of eighth or less misaligned in Emmentaler
Version 2b0cd5c, Windows (running Win7-64, Win7-32, Win Vista-32)
In this version eighth note hooks are misaligned in the tabulature vertically. If the "full" tabulature properties are used, the hooks are slightly misaligned horzontally.
I had this on three different computers one running Windows 7 62 bit, the other running Vista 32 bit and the third running Windows 7 32 bit.
Comments
better attach the images here (bottom of page, File attachments)
A sample score would be helpful too?
Had to correct my html tags to make the images visible. The first one you see is uses the standard TAB properties, the second one - the same score - switched to "full" TAB properties. As you can see, the hooks are also slightly shifted to the left in the standard system. Added a sample score too, look up the attatchment.
Might be 2 independent problems, at least the horizontal misalignment might be a result of the move to SMuFL fonts, and doesn't happen with Bravura, only with Emmentaler.
Switching the sample score to Bravura fixes the horizontal misalignment only.
It's the same with pitched staves - it doesn't seem to affect Emmentaler.
1. Open attached score (produced in 1.3).
2. 'Style'>'General…'
3. Change 'Musical symbols font' to 'Bravura'.
4. 'OK'.
Result: The hooks don't align correctly with the stem.
Using MuseScore 2.0 Nightly Build (ef996b4) - Mac 10.7.5.
I didn't see the issue with Bravura, only with Emmentaler
You're right, Jojo - sorry.
Also see this: #23660: TAB: Eighth note hooks misaligned in Bravura and Emmentaler
Marked #23857: Flags are not aligned to note when using Emmentaler font as a duplicate of this
Marked #24641: Eighth note flags not aligned well with stems in Emmentaler as a duplicate of this
The horizontal misalignment is due to the font design. Bravura is flag starts at 0 while mscore one doesn't.
I guess we need to modify the MScore font and Gonville needs the same treatment?
Seems there are a few relevant passages in the SMuFL spec. This from 0.7, which I have handy, on page 20:
...
length, and such that x=0 corresponds to the left-hand side of the stem.
I am not sure I understand the last one. Maybe they meant right-hand side; ottherwise the flag would overlap the stem, would it not? Bravua's flat looks designed to have X=0 on the right-hand side of the stem to me. But I'm out of my element here.
I am not sure I understand the last one. Maybe they meant right-hand side; ottherwise the flag would overlap the stem, would it not? Bravua's flat looks designed to have X=0 on the right-hand side of the stem to me. But I'm out of my element here.
No. I think flags are indeed designed to overlap the stem. See the drawing a couple of pages above.
Fixed in bbb871f0eb
I modified the mscore font so that
- flags are aligned on the origins
- bearing are 0 width for flags
- the part connected to the stem is a bit bolder so the connection is easier.
Thanks for the pointer to the drawing, that clears up my confusion. I was also thinking the extra "hook" at the end of the flag would be obscured by the stem if they overlapped, but now I see it actually extends past the end of the stem, since it is below the Y=0 axis.
I would like to point out, that the initial problem, the one that made me contribute this thread is still not solved. This thread is about two independent problems one of them being done, the other one still there:
1) The solved one: Slight horizontal misalignment of hooks with the Emmentaler font.
2) The remaining one: The vertival alignment of eigth note flags is wrong in tabulature, if the tabulature properties are set to "common". As you can see in the picture I initially posted, the misalignment is obvious. It disappears though when TAB staff properties are switched to "full". The bug is there no matter what font is used, affects Bravura as well as Emmentaler.
Looks as if an offset was wrong or something like that, does not seem to be a big issue I hope.
If there are two problems, there should be two issues in the issue tracker.
Sorry, it took a while for me to realize, that it was two problems. Am I to understand that I should open a new issue or would it be exceptionally sufficient to remain with this one ?
Fixed in 7616e3be6b
Automatically closed -- issue fixed for 2 weeks with no activity.