[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Substitute for s1*0

From: Keith OHara
Subject: Re: Substitute for s1*0
Date: Tue, 8 May 2012 02:48:36 +0000 (UTC)
User-agent: Loom/3.14 (

Trevor Daniels <t.daniels <at>> writes:

> Yes, I now agree.  We can't continue to advocate s1*0
> in the docs now we are aware of these pitfalls.

I suggest we mention that <> takes no time in NR 1.5.1 
Chorded Notes, but avoid it in the examples.

Most of the visible uses of s1*0 in the docs were instigated 
by me, so I see how to avoid them.

The use of s1*0 to label music from \cueDuring 
  s1*0^\markup { \right-align { \tiny "Flute" } }
  \cueDuring "flute" #UP { g4 bes4 }
got some strong negative feedback
so I'm happy to put these back to use a temporary voice
  \new CueVoice {
    \override InstrumentSwitch #'self-alignment-X = #RIGHT
    \set instrumentCueName = "Flute" 
  \cueDuring "flute" #UP { g4 bes4 }
I had complained that this method caused problems when instruments
take cues from each other, but these problems are avoided so 
long as the temporary voice is explicitly created and finished.

The uses to finish spanners after the last note, 
  { e'2\p\< d'\> s1*0\! }
can also be handled with a temporary voice
    { e'2 d'! }
    { s2\p\< s4\> s8. s16\! }
Other uses are simlarly avoided with parallel voices.

David Kastrup <address@hidden> writes:

> I tried discussing using "< >" in the documentation vs the possibly
> stranger looking "<>". 
> However, there has been no feedback whatsoever on this proposal.

It has not yet been a day.  They way you have \displayLilyMusic
write < > makes sense for consistency there.  In the documentation,
<> is more consistent with <c e g>, as you already concluded.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]