> "a" == andersvi writes:
a> ... but how to add them at the right place?
Like always, reading the manual may be useful... Just glanced through
the section on Ossia staves in lilypond-notation.info, and guess what i
saw?
alignAboveContext = #"firstStave" - to set a stave above a previo
Heres an update with some typos fixed.
Rach_Praeludium_Cmoll.ly
Description: Binary data
Theres the issue of an effective way to add the 2 extra staves in the
Tempo primo section. The way its done now makes it difficult to connect
the arpeggios in mms. 52 & 54. I guess it has something todo w
> "X" == Xavier Scheuer writes:
X> You have an "unwanted extra space" added at the end of the line
X> before the break when adding the new staves. Use \once \set
X> Staff.explicitKeySignatureVisibility = #end-of-line-invisible
X> just after you \new Staff { within your tempoP
On 15 November 2010 13:00, wrote:
>
> Heres a version of the prelude:
>
>
>
> Any comments and suggestions for improvements are of course very
> welcome.
Hi!
It seems nice (although I'm not a pianist).
> Especially concerning the shaky staff-handling introducing the "tutti"
> or "Tempo Primo"
Heres a version of the prelude:
Rach_Praeludium_Cmoll.ly
Description: Binary data
Any comments and suggestions for improvements are of course very
welcome.
Especially concerning the shaky staff-handling introducing the "tutti"
or "Tempo Primo" ending section.
And also the fitting of staffs on
heres the bug report just sent (wo. png-files):
\version "2.13.39"
%% rests in one voice crossing other voice
<<
{c4 c}\\
{ r8 c'' r c''}
>>
<>
%% Rests in mixed (rests+notes) columns don't obey Rest 'direction = #UP:
<<
{c4 c}\\
{\override Rest #'direction = #UP r8 c'' r c''}
>>
<>
%% wan
K> if you send a short example and desired behavior as a bug report
Ill set something up.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
On Wed, 03 Nov 2010 09:01:03 -0700, wrote:
"K" == Keith E OHara writes:
K> It is less clear if the use of Stem 'direction to place rests, in
K> the notes-plus-rests case, was intentional.
Shouldn't the rests by default be placed where the voice goes in the
column - odds up, evens dow
Keith, thanks for the pointers, and a nice solution using stemNeutral.
> "K" == Keith E OHara writes:
K> It is less clear if the use of Stem 'direction to place rests, in
K> the notes-plus-rests case, was intentional.
Shouldn't the rests by default be placed where the voice goes in
On Tue, 02 Nov 2010 09:19:53 -0700, wrote:
Yes, thanks. The problem is getting at the automatic behaviour which is
already available.
I beleive its a bug, that \stemDown obstructs explicit coming later.
\override Rest #'direction = #UP
Anders,
LilyPond does obey a simultaneous \stemDow
On Tue, Nov 2, 2010 at 9:39 PM, wrote:
> I beleive its a bug, that \stemDown obstructs explicit coming later.
> \override Rest #'direction = #UP
> Or perhaps ive misunderstood something in the way this works. Happy for
> any pointers towards clearifying stuff.
Greetings,
sorry for not having
> "E" == -Eluze writes:
E> you can also override the rest's position:
Yes, thanks. The problem is getting at the automatic behaviour which is
already available.
I beleive its a bug, that \stemDown obstructs explicit coming later.
\override Rest #'direction = #UP
Or perhaps ive mi
you can also override the rest's position:
\new Staff <<
\new Voice {
\voiceTwo
\override Voice.Rest #'staff-position = #3.7
\musicA
\revert Voice.Rest #'staff-position
\musicA
}
\new Voice {
\voiceOne
\musicB
\musicB
}
>>
--
View this message in
> "K" == Keith E OHara writes:
K> On Mon, 01 Nov 2010 12:25:12 -0700,
wrote:
>> Q: How Can i separate handling of rests from stem-directions in
>> polyphonic voice-handling?
>>
Hello Anders,
K>I would also have expected Rest 'direction to do what you
K> asked.
> James Bailey writes:
> You can always do \voiceOne \stemDown
Does the below work in your lilypond? Which version are you using?
\new Staff {
<<
\new Voice {\voiceOne \stemDown r8 c'' r c'' }
\new Voice {\voiceTwo c4 c}
>>
}
> What's odd? It looks normal to me.
The p
Hi Keith. Thanks for your answer.
> "K" == Keith E OHara writes:
K> I recommend that you continue as you are with Rest 'direction,
K> and whenever Lilypond puts the rests in the wrong places, use
K> pitched rests {f''\rest c'' f''\rest c'' }
Yes, i know about the explicit possi
On Nov 1, 2010, at 4:14 PM, ander...@notam02.no wrote:
> Hello. Im doing some testing on Rachmaninovs C-minor praeludium.
>
> Q: How Can i separate handling of rests from stem-directions in
> polyphonic voice-handling?
>
> Id actually want the default behavior of \voiceOne, except for pointing
On Mon, 01 Nov 2010 12:25:12 -0700, wrote:
Q: How Can i separate handling of rests from stem-directions in polyphonic
voice-handling?
Hello Anders,
I would also have expected Rest 'direction to do what you asked. It does
change the placement of rests in columns with only rests, but wh
Hello. Im doing some testing on Rachmaninovs C-minor praeludium.
Q: How Can i separate handling of rests from stem-directions in
polyphonic voice-handling?
Id actually want the default behavior of \voiceOne, except for pointing
the stems down.
<<
\new Voice {\voiceTwo \override Rest #'directi
19 matches
Mail list logo
