Hi Alasdair,
Many thanks indeed - I hadn't thought of using \transpose for this
purpose, although I have indeed used it for other reasons. Several
of the initial responses to my query recommended \transpose as well.
It still means though that I need a separate declaration for every
score
Dear Christian,
Many thanks indeed - I hadn't thought of using \transpose for this purpose,
although I have indeed used it for other reasons. Several of the initial
responses to my query recommended \transpose as well. It still means
though that I need a separate declaration for every score
Hi Alasdair!
Two pretty easy options here as transposing a whole lot of stuff is pretty
straight forward in lilypond:
You could exchange the lines like
\new Staff << \global \global_two \global_prelude \prelude_two >>
with
\new Staff << \transpose #FROM #TO { \global \global_two
Thank you all so much for your help and advice. Given that there might
have been some confusion about what I was asking, I've added below a sort
of template of what I'm doing. Note that this is a duet, and the notes for
the first part (first instrument) are given as variables *_one; and for the
On Wed 09 Feb 2022 at 18:52:52 (+0100), David Kastrup wrote:
> David Wright writes:
> > On Wed 09 Feb 2022 at 14:24:14 (+), Valentin Petzel wrote:
> >>
> >> I think Alasdair does not want to specify relative at toplevel, but
> >> he has his voices in multiple consecutive parts, and he wants
Maybe this does what you want?
\version "2.22.1"
ref = c'
%ref = c
<<
\new Staff \relative \ref { g'4 a b c }
\new Staff \relative \ref { c4 d e f }
>>
On 09/02/2022 07:16, Alasdair McAndrew wrote:
I'm sorry about all these damn-fool queries of mine; I promise to go
back under my rock
On Wed 09 Feb 2022 at 14:24:14 (+), Valentin Petzel wrote:
>
> I think Alasdair does not want to specify relative at toplevel, but he has
> his voices in multiple consecutive parts, and he wants the whole voice to be
> relative, instead of each part being separately relative. This can of
David Wright writes:
> On Wed 09 Feb 2022 at 14:24:14 (+), Valentin Petzel wrote:
>>
>> I think Alasdair does not want to specify relative at toplevel, but
>> he has his voices in multiple consecutive parts, and he wants the
>> whole voice to be relative, instead of each part being
Hello Jean, hello David, hello Lukas,
I think Alasdair does not want to specify relative at toplevel, but he has his
voices in multiple consecutive parts, and he wants the whole voice to be
relative, instead of each part being separately relative. This can of course
simply be done using
Jean Abou Samra writes:
>> Le 09/02/2022 14:43, David Kastrup a écrit :
>>
>> > Though this might not be considered very clean.
>> The word "atrocity" readily suggests itself.
>>
>> I don't think I have thought of using #{ ... \etc #} as kind of a lambda
>> function created with LilyPond
> Le 09/02/2022 14:43, David Kastrup a écrit :
>
> > Though this might not be considered very clean.
> The word "atrocity" readily suggests itself.
>
> I don't think I have thought of using #{ ... \etc #} as kind of a lambda
> function created with LilyPond before and/or connecting this to
>
Jean Abou Samra writes:
>> Le 09/02/2022 09:23, Lukas-Fabian Moser a écrit :
>>
>> - There's no way to globally declare your input mode to be relative
>
>
> Well ...
>
>
> \version "2.22.1"
>
> #(set! toplevel-music-functions (cons #{ \relative c' \etc #}
> toplevel-music-functions))
>
> { d
Hello Alasdair,
I don’t think anyone here has a problem with you asking questions. After all
this list is for users to help users. And in the Lilypond manual it can be
hard to find very specific things.
Anyway. What you want to do is very well possible, see this example:
test = { c a }
> Le 09/02/2022 09:23, Lukas-Fabian Moser a écrit :
>
> - There's no way to globally declare your input mode to be relative
Well ...
\version "2.22.1"
#(set! toplevel-music-functions (cons #{ \relative c' \etc #}
toplevel-music-functions))
{ d e f }
Though this might not be considered
On 09/02/2022 08:00, Wols Lists wrote:
On 09/02/2022 07:16, Alasdair McAndrew wrote:
I'm sorry about all these damn-fool queries of mine; I promise to go
back under my rock soon. Anyway:
In the current 18th century suite I'm typesetting (for two treble
instruments without bass), there is a
Hello Alasdair,
Le mer. 9 févr. 2022 à 08:24, Alasdair McAndrew a écrit :
>
> The one thing I don't know how to do is to declare the relative pitch
> globally. Thus, each music variable looks like
>
> movement1_part1 = \new Voice \relative c'' { notes, notes, and more notes }
>
> The
Hi Alasdair,
Am 09.02.22 um 08:16 schrieb Alasdair McAndrew:
I'm sorry about all these damn-fool queries of mine; I promise to go
back under my rock soon. Anyway:
In the current 18th century suite I'm typesetting (for two treble
instruments without bass), there is a separate variable
On 09/02/2022 07:16, Alasdair McAndrew wrote:
I'm sorry about all these damn-fool queries of mine; I promise to go
back under my rock soon. Anyway:
In the current 18th century suite I'm typesetting (for two treble
instruments without bass), there is a separate variable (containing the
notes)
Alasdair,I am not sure to correctly understand what you want to do...Do you have a small example ?ThanksRémyenvoyé : 9 février 2022 à 08:16de : Alasdair McAndrew à : lilypond-user@gnu.orgobjet : Setting relative pitch as a global declaration?I'm sorry about all these damn-fool queries of mine; I
I'm sorry about all these damn-fool queries of mine; I promise to go back
under my rock soon. Anyway:
In the current 18th century suite I'm typesetting (for two treble
instruments without bass), there is a separate variable (containing the
notes) for each part of each movement. Then there are
20 matches
Mail list logo
