Re: voiceOne and oneVoice

2021-10-01 Thread Leo Correia de Verdier
While this is certainly useful, one should be aware of what is happening. With the syntax soprano.1 = c’4 you are not defining a variable soprano.1 as c’4, you are defining the value corresponding to key 1 in an alist that is the value of variable soprano. This can be very powerful, useful

Re: voiceOne and oneVoice

2021-09-30 Thread Guy Stalnaker
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,

Re: voiceOne and oneVoice

2021-09-30 Thread Ernie Braganza
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

Re: voiceOne and oneVoice

2021-09-30 Thread David Kastrup
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

Re: voiceOne and oneVoice

2021-09-30 Thread Valentin Petzel
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

Re: voiceOne and oneVoice

2021-09-30 Thread Lukas-Fabian Moser
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

Re: voiceOne and oneVoice

2021-09-30 Thread Jean Abou Samra
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

Re: voiceOne and oneVoice

2021-09-30 Thread Valentin Petzel
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

Re: voiceOne and oneVoice

2021-09-30 Thread Aaron Hill
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

Re: voiceOne and oneVoice

2021-09-30 Thread Lukas-Fabian Moser
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

Re: voiceOne and oneVoice

2021-09-30 Thread Silvain Dupertuis
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

Re: voiceOne and oneVoice

2021-09-30 Thread Valentin Petzel
Hi David, 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 an

Re: voiceOne and oneVoice

2021-09-29 Thread Kira Garvie
I think that made sense! I will try it out and let you know if it doesnt! On Wed, Sep 29, 2021 at 6:50 PM David Kastrup wrote: > Lukas-Fabian Moser writes: > > > Hi Kira, > > > > Am 30.09.21 um 00:32 schrieb Kira Garvie: > >> I realize this is a pretty basic question... but what is the > >>

Re: voiceOne and oneVoice

2021-09-29 Thread David Kastrup
Lukas-Fabian Moser writes: > 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 a multivoice >> keyboard-style hymn (as opposed to SATB chorale style) and the >>

Re: voiceOne and oneVoice

2021-09-29 Thread Lukas-Fabian Moser
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 a multivoice keyboard-style hymn (as opposed to SATB chorale style) and the directions say to switch between oneVoice and