It *does* use the horizontal space optimally, but I don't think I've
ever seen a published score where it looks like this. I'd have to check
a notation style manual to know if it's a rule, but I'm pretty sure the
clef is supposed to come before the barline. Anyway the trick using
\grace {s4}
> Notice how in the lower staff when the clef changes from alto to
> treble, the treble clef is shoved all the way into the next bar
> instead of remaining behind the barline. When I take out the grace
> notes from the upper staff, the clef change happens as expected. Is
> this a bug?
Actually,
Thanks. I should have seen this before. Sorry for the trouble...
Jon
Wilbert Berendsen wrote:
I think this is caused by grace timing. As a workaround you could add a \grace
s4 in the second staff, the clef change is behind the bar line.
See also
http://lilypond.org/doc/v2.11/Documentation/u
Op vrijdag 10 oktober 2008, schreef Wilbert Berendsen:
> I think this is caused by grace timing. As a workaround you could add a
> \grace s4 in the second staff, the clef change is behind the bar line.
I meant 'before' :-)
best regards,
Wilbert Berendsen
--
LilyKDE, LilyPond for KDE: http://lil
I think this is caused by grace timing. As a workaround you could add a \grace
s4 in the second staff, the clef change is behind the bar line.
See also
http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Grace-notes
under Known issues and warnings.
<<
\new StaffGroup = "strings" <<
\
While working on a project recently I noticed odd behavior in a clef
change in the middle of a system. At the time, I just hacked around it
by adding another voice with nothing but skips and making sure there was
a "s32" after the clef change, but I thought I should report this just
in case it
Date: Thu, 09 Oct 2008 18:51:14 +0200
From: Martial <[EMAIL PROTECTED]>
Subject: Lilypond documentation Custos
To: bug-lilypond@gnu.org
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hello
doc error ?
I think that it is
\override Custos #'style = #'
I posted this message to the user list and it was suggested that I
should send to bug-lilypond so that this clef would be added to the
wishlist. Thanks in advance!
Jon
[first message]
When I was working on the ill-fated Ravel String Quartet passage as an
unfretted strings headword, I noticed
Issue 155: \parenthesize should include accidentals as well as note heads
http://code.google.com/p/lilypond/issues/detail?id=155
Comment #2 by v.villenave:
Risto suggests that the parentheses should include the accidental, as shown
is the
attached picture.
See also
http://lists.gnu.org/arch
