Re: [Lilypond-auto] Issue 1150 in lilypond: RehearsalMark at start of line should not be printed above the clef

[lilypond]

Comment #12 on issue 1150 by address@hidden: RehearsalMark at start of  
line should not be printed above the clef
http://code.google.com/p/lilypond/issues/detail?id=1150

I would clearly prefer RehearsalMark to be placed above the "virtual"
bar line at line break as default behaviour.

Out of the six examples given by Reinhold, 2 uses this practice (so it
is non negligible), one put Mark above the first note and 2 above the
key signature (BTW the compromise between first note and key signature
would be the virtual bar line).

And the main reason I'm pushing for this is that this has a logical
justification: RehearsalMarks are placed above the bar line (in the
middle of a line) or "where the bar line would be" at line breaks.

If you want to make an exception for RehearsalMarks at line breaks and
align them on the key signature by default, I'm fine, as soon as it is
also possible to override this and choose to align on the bar line.


The example "Puccini's Il Tabarro by Ricordi" should not count as
"above the clef".  The first part is in C major (same key signature
for all the instruments in the score), and number "2" is indeed above
the clef in order to avoid the tempo indication above time signature
change.  But see number 7, 12, 13, 14, 17, 18, 19, 20 and 24
the placement is non consistent during the piece.

When there is a key signature it is usually placed at the right side
of it (virtual bar line ?) -> 13, 14, 18;
sometimes above the key signature (avoid tempo collision) -> 17
Sometimes it is above the first note (or even more to the right)
-> 19, 20.

Collision avoidance between RehearsalMark and tempo indications also
fluctuates: sometimes Mark above tempo (13, 20), sometimes Mark shifted
left and tempo shifted right (17, 24), sometimes a mix of the
2 solutions (7).

Thank you.

Attachments:
        Puccini.png  201 KB

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings