[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Chord changes over repeat alternatives

From: Yitz Gale
Subject: Re: Chord changes over repeat alternatives
Date: Sat, 12 Aug 2006 19:16:30 +0000 (UTC)
User-agent: Loom/3.14 (http://gmane.org/)

Paul Scott wrote:
> Yitz Gale wrote:
>> The Chord Name engraver with chordChanges = #t
>> does not print the chord at the beginning
>> of a repeat alternative if the chord at the
>> end of the previous repeat alternative was
>> the same.

> The way I read the 2.6 documentation

This bug is not specific to 2.6.
It affects 2.8 and 2.9 also (I think).

> ...you want to set chordChanges = ##f if you
> want the chord printing to change when you want
> it to instead of when the chord changes.
> Is that what you meant?

No. I want the chords to print when they change.
For this, I need to set chordChanges = ##t.
However, there is a bug that causes lilypond to skip
a chord in a certain case even though it is a change,
as described above, and as shown in my example.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]