yeah, stem is too short, thanks for reporting
On Mon, Aug 27, 2018 at 11:12 PM sug1no notifications@github.com wrote:
https://jsfiddle.net/fbowy3d8/
[image: image]
https://user-images.githubusercontent.com/3293067/44698491-1a33aa80-aabb-11e8-80b3-c046f7b864b3.png
- too short stem?
- too large flag?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/0xfe/vexflow/issues/644, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOukzBga4ygjb24depEYgG7IbZ9azwFks5uVLUngaJpZM4WO1v1
.
--
Mohit Muthanna [mohit (at) muthanna (uhuh) com]
one more reference:
As an aside -- I think that Vexflow's code for how to deal with the regular 64th and 128th beams is more correct than Finale's. Finale is trying to add extra space between the 2nd and 3rd beam in order to make it so that every beam surrounds a line rather than landing on a line. This is the correct behavior when the beams are within the staff (so the extra staff line is not distracting), but it's incorrect for when the beams lie outside the staff, since there are no extra lines to make distracting.
@mscuthbert san Thank you for your comment.
As an aside -- I think that Vexflow's code for how to deal with the regular 64th and 128th beams is more correct than Finale's.
agree.
Finale is trying to add extra space between the 2nd and 3rd beam in order to make it so that every beam surrounds a line rather than landing on a line.
I think {extra space} changed by zoom setting:

the following is a musx file of this test:
Fascinating! I'll have to test in finale with lower notes that lie in the staff to see what it does. But in any case, we'll look into the Vexflow gracenote spacing, which is in any case a bit of a problem.
fixed by #649.