some visual issues with triplets, cresc, and double-barline in 3.0dev from score imported from 2.1

• Feb 18, 2017 - 02:07

When opening the attached score (saved in 2.1 a week ago) in 3.0dev fade47128 on Windows 10 x86-64, I notice the following things with triplets I'd like fixed:

  1. The tuplet bracket should always be horizontal if all the notes are the on the same staff line, even if there is a rest at beginning or end. As happens on meas 28-30 drum part, there is a rest at the beginning of the triplet, which causes the algorithm to think that the bracket should be diagonal:
    triplet-with-rest-should-be-horizontal-if-all-notes-same-staffline.png
  2. meas 77-78 in bass, there is a cresc that happens to cross a newline, and since it is full score, that means it is on a new page. But the problem is that the algorithm is miscalculating the starting xpos of the 2nd half of the cresc, which starts at begin of meas 78, but somehow looks like it is starting way early at meas 74.
    cresc-broken-poorly-across-newpage.png
  3. meas 83 tenor, the triplet numeral "3" is overlapping the beam of the triplet. The "3" should be higher than the top of the beam such that there is just enough whitespace to clearly read the "3". I suspect maybe part of the issue is due to the jazz font having fat beams??
    triplet-3-overlap-with-beam.png
  4. There is a general problem of bracketed tuplets not having their numeral be vertically & horizontally centered in the middle of the white space between the two halves of the bracket. Here is an example of meas 86 tenor & alto part:
    bracked-triplet-needs-to-center-the-numeral.png
    All those "3" numerals should be moved a little higher and leftward, such that the numeral is center-justified vertically and horizontally with the line of the bracket. (i.e. the center of the 3 should intersect at the point at the middle of the deleted portion of the line)
  5. Double barlines for some reason got imported to believe that they span the entire height of the system, even though they were saved as only spanning their particular staff. Examples are every single double barline:
    double-barlines-defaulted-to-span-entire-system.png
    But note that all repeat barlines were correctly imported as spanning just their staff.
Attachment Size
Yesterday's Date Score_.mscz 145.35 KB

Comments

an in addition to point #1, I would say that even if an isolated stem may be slightly taller than a beamed part of a tuplet, that that shouldn't cause the bracket to be diagonal, as happens in meas 84 for tenor:

triplet-stem-no-diagonal-bracket.png

Even for hypothetical situation if the first stems were down and the last stem is up, I would prefer that the bracket for the tuplet should still be horizontal if all the notes are on the same line.

In reply to by ericfontainejazz

In your last picture the 16th note stem looks longer and goes below the bottom line of the staff. This would explain the bracket being offset to keep a constant distance between the first and last notes. In the 6th staff of the big picture above, the stems do not cross the top line of the staff, so the bracket is parallel. The only question I have is, should the stem on the single 16th note be longer than the stem on the connected 8th notes? It does the same thing in 2.0.3

tuplet.png

In reply to by mike320

well I think regardless of whether the stem is longer, my point was I don't think that the bracket should be non-horizontal if the notes are all the same pitch. I say this because diagonal beams make the think that the notes are changing pitch. But as you point out it does the same thing in 2.0.3, so maybe this is not considered a problem (although I might file a feature request).

Now as the to the question of why is that stem longer than the beams? It could be the jazz font used, but I don't know.

In reply to by mike320

well it is also Emmentaler in my pic too. So maybe I shouldn't have said "font" that is different, but rather it is some thing with the 3.0 jazz style that is different. If I make really thick beams, then I can get the bracket to be horizontal:

thickbeam.png

So maybe the question to look into is why is the beamed stem so much shorter than the non-beamed stem, and is that deliberate, or unintentional.

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