[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Auto-transposition
From: |
David Wright |
Subject: |
Re: Auto-transposition |
Date: |
Sun, 10 Dec 2017 20:40:54 -0600 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Sun 10 Dec 2017 at 20:37:03 (+0000), Neo Anderson wrote:
> Hi,
> I'm new to Lilypond, coming over from a commercial program. Please, bear with
> me as I'm still learning.
> The issue:
> I seem to get measures auto-transposed one by one.
> I have one bar of music, then the second one gets transposed one octave
> higher, the next one even one octave higher, and so on.
>
> Without /relative command, the x5 chords get messed up.I use variables but I
> get the same issue without them too.
> Minimal example auto-transpose-minimal.ly
If you write
hita = \relative c { … … … }
then \hita will always yield the same notes. The \relative
construction produces an absolute expression.
Never use \relative { } round the structure that describes your score
because any change you make will change the pitch relationship between
the last note of one variable and the first of the next. LP can manage
it, as you have just shown, but our brains can't keep track.
Cheers,
David.
- Auto-transposition, Neo Anderson, 2017/12/10
- Re: Auto-transposition, David Kastrup, 2017/12/10
- Re: Auto-transposition,
David Wright <=
- Re: Auto-transposition, Kieren MacMillan, 2017/12/11
- Re: Auto-transposition, Shevek, 2017/12/12
- Re: Auto-transposition, Simon Albrecht, 2017/12/12
- Re: Auto-transposition, David Wright, 2017/12/12
- Re: Auto-transposition, Shane Brandes, 2017/12/12
- Re: Auto-transposition, David Wright, 2017/12/13
- Re: Auto-transposition, Ben, 2017/12/13
- Re: Auto-transposition, Kieren MacMillan, 2017/12/13
- Re: Auto-transposition, David Wright, 2017/12/13
- Re: Auto-transposition, Kieren MacMillan, 2017/12/13