There's unfortunately a problem with my idea. If I put the strumming
patterns into the same variable I use for ChordNames, it still
reserves space for them, even if I set chordChanges = ##t. See this
example for comparison. Is there any way around this? I would have
expected non-printed chords to not have impacted the spacing of
printed notes.
\version "2.19.25"
\score {
<<
\new ChordNames { \repeat unfold 32 c8 }
\relative c'' { c1 c c c}
>>
}
\score {
<<
\new ChordNames { \set chordChanges = ##t \repeat unfold 32 c8 }
\relative c'' { c1 c c c}
>>
}
\score {
<<
\new ChordNames { c1 c c c }
\relative c'' { c1 c c c}
>>
}
On Tue, Aug 25, 2015 at 11:31 AM, Joel Ebel <[email protected]> wrote:
>> chordRoot =
>> #(define-music-function (m) (ly:music?) (event-chord-reduce m))
> That works perfectly!
>
>>
>> I don't like the name. Once we come up with a nice bike shed color, we
>> probably should provide that function in LilyPond proper and document it
>> along with Pitch_squash_engraver.
>
> I agree that this would be a handy function to exist and have
> documented in section 1.1.4 of the notation reference, though I don't
> have a better idea for the name. Now that I know about
> event-chord-reduce, I see that this has been discussed before:
> https://code.google.com/p/lilypond/issues/detail?id=185
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
