Dear William, Aaron and Pierre,
thank you so much for your quick reply.
I ended up writing it using the hint by Aaron like this (which I find
makes writing the individual voices easier and also 'flipping' the color
over to the other voice):
/\version "2.24.3"
\relative c'
{
f2( g4
Hi Joop,
I'd forget voices and do:
\version "2.24.3"
nr = \tweak color #red \etc
\relative c
{
f'2( g4.)
8 |
<\nr d f>4 q <\nr e g>16 <\nr f a>
a8 r4
}
HTH, cheers,
Pierre
Le lun. 18 mars 2024 à 18:44, Go77 a écrit :
> Hi,
>
> I'm trying to color the note he
On 2024-03-18 9:41 am, Go77 wrote:
Hi,
I'm trying to color the note heads of a single voice in a staff. I
tried to do that with the following code:
/\version "2.24.3"
\relative c
{
f'2( g4.)
<< { d8 | f4 f4 g16 a }
{ \override NoteHead.color = #red
g8
Dear Joop,
Use \tweak color #red , like so
\version "2.25.6"
\relative c
{
f'2( g4.)
<< { d8 | f4 f4 g16 a }
{ \tweak color #red
g8 | d4 d4 e16 f
}
>>
a8 r4
}
Thanks,
-William
On 3/18/24 12:41, Go77 wrote:
Hi,
I'm trying
Hi,
I'm trying to color the note heads of a single voice in a staff. I tried
to do that with the following code:
/\version "2.24.3"
\relative c
{
f'2( g4.)
<< { d8 | f4 f4 g16 a }
{ \override NoteHead.color = #red
g8 | d4 d4 e16 f
\revert N
Richard Sabey hotmail.co.uk> writes:
> How come LilyPond can't output the correct MIDI for 2 or more
> simultaneous notes in a non-standard tuning?
I believe the stable version 2.12.3 works correctly in this area.
> Is LilyPond actually assigning the notes to the same channel despite my
> eff
How come LilyPond can't output the correct MIDI for 2 or more simultaneous
notes in a non-standard tuning? After all, it does output the correct MIDI for
individual notes in a non-standard tuning.
Investigating LilyPond's limits in this area, I find that LilyPond outputs the
correct MIDI for s
[EMAIL PROTECTED] writes:
>
>
> Agreed- nothing is assumed, although from a theoretical standpoint everything is a
>design decision. (Sorry, I'm being too picky.)
>
> Could this behaviour be made explicit in the docs? I would like to
> suggest a code change or adjustable property setting (t
- Original Message -
> > in two separate bracketed-voice-contexts, why assume that it's the
> > same Voice?
>
> Nothing is assumed, the names are simply the same: "" -> same voice.
>
> Jan.
Agreed- nothing is assumed, although from a theoretical standpoint everything is a
design deci
Hans Kieserman <[EMAIL PROTECTED]> writes:
> Sorry, I think I understand- the default is to name all of the voices
> the same, so lilypond treats both voices as one.
Yes.
> This default behaviour seems odd, though. If I'm entering note data
> in two separate bracketed-voice-contexts, why assum
Sorry, I think I understand- the default is to name all of the voices
the same, so lilypond treats both voices as one.
This default behaviour seems odd, though. If I'm entering note data in
two separate bracketed-voice-contexts, why assume that it's the same Voice?
Thanks again,
Hans
11 matches
Mail list logo