Hi everyone,
One problem with this suggestion that Lilypond does not support the simple use of digits
in variable names.
As far as I understand, it is because a digit following directly alphabetic characters is
interpreted as a duration.
I took me a long time to discover that there is a way o
Hi Silvain,
I'd say singleVoice would even be clearer.
But I think maybe it would also be a good idea if we had a synax like \voice
number. Currently Lilypond only supports four voices, and any more requires
knowledge about the scheme interface, but \voice1 \voice2, ... could directly
support
On 2021-09-30 12:36 am, Silvain Dupertuis wrote:
One problem with this suggestion that Lilypond does not support the
simple use of digits in variable names.
As far as I understand, it is because a digit following directly
alphabetic characters is interpreted as a duration.
I think the idea woul
Hello Silvain,
Note that I specified \voice number, so number is not part of the name, but an
argument. But Lilypond does (similar to TeX) interpret \command1 as \command 1
(which is the reason why numbers cannot be part of variable names, also
similar to how \commandA\commandB do not need to b
Le 30/09/2021 à 10:04, Valentin Petzel a écrit :
Hello Silvain,
Note that I specified \voice number, so number is not part of the name, but an
argument. But Lilypond does (similar to TeX) interpret \command1 as \command 1
(which is the reason why numbers cannot be part of variable names, also
si
There is also the to me annoying concept
that \voiceTwo is usually the third voice.
Perhaps we could make \voice n format the
n-th voice in the normal order?
That would mean that in two-part music, \voice 2 is down-stemmed, and in
three-part music, it is up-stemmed.
In fact, from classica
Hello Jean,
this is something we also find in other notation programs, because the voice
does not only give the stem direction, but also the offset direction for
collisions. The idea is basically: While you go from top/bottom to the center
voices they offset into different directions.
So from
Great! That works fine.
Thanks!
Em qua., 29 de set. de 2021 18:15, Hans Aikema
escreveu:
>
>
> On 29 Sep 2021, at 21:28, Jefferson Felix wrote:
>
> Hi everyone,
>
> I'm working on some hymns and noticed that I need to add square brackets
> just above the treble clef to indicate the introductor
Jean Abou Samra writes:
> Le 30/09/2021 à 10:04, Valentin Petzel a écrit :
>> Hello Silvain,
>>
>> Note that I specified \voice number, so number is not part of the name, but
>> an
>> argument. But Lilypond does (similar to TeX) interpret \command1 as \command
>> 1
>> (which is the reason why n
That was a very clear and helpful explanation. Thank you.
On Wed, Sep 29, 2021 at 6:42 PM Lukas-Fabian Moser wrote:
> Hi Kira,
>
> Am 30.09.21 um 00:32 schrieb Kira Garvie:
> > I realize this is a pretty basic question... but what is the
> > difference between voiceOne and oneVoice? I am writing
Hi all,
> You have to set the lengths of the breve notes manually, though.
It sure seems like this could be done automagically (maybe using a Scheme
engraver?). You could say something like
\specialnote \breve 8*931
and it would
(1) engrave a note that looks like the first parameter given
Just want to follow up on what Lukas-Fabian says here:
If you do in-staff polyphony via
<<
{ \upperMusic } \\ { \lowerMusic }
>>
then the \\ makes LilyPond silently add a \voiceOne to \upperMusic and a
\voiceTwo to \lowerMusic, making sure that \upperMusic has upward stems,
articulation
Jean, thank you! This should be the default behavior, imo...
13 matches
Mail list logo
