lilypond-user
[Top][All Lists]
Advanced

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

Re: Capo chords


From: Ezequiel Sierra
Subject: Re: Capo chords
Date: Mon, 25 Sep 2006 22:24:10 -0400

Here is an example of something i made check it out


Attachment: 001.ly
Description: Binary data


On Sep 25, 2006, at 6:33 PM, Tim Packer wrote:

On Sun, 24 Sep 2006, aabb wrote:

I achieve this by creating 2 parts, so that the transposed chords appear
below the original ones. I've seen this format used in a number of
published song books. You can create the "Capo 3", or similar text using the \set instrument command. This puts "Capo 3" to the far left of the first system, aligned with the transposed chords. I include an example
below. This works for Lilypond version 2.8. I can't vouch for older
versions. The command in the \layout block is needed because, by
default, ChordNames parts don't seem to print the instrument name.

Yes, that works - thanks! It doesn't produce output quite the same as I'm used to, but it's close enough. Turns out that all I was doing wrong was not using \New - d'oh!

I played with chord name exceptions, but they didn't obviously seem to be able to use the existing chord as a parameter - so I could turn G into G() easily, but not G into G(E).

Now my only problem is that my MIDIs have two sets of chords playing in different keys! Is it possible (without an entirely separate score construct for MIDI) to mute a staff or chordname group, so it still renders but doesn't produce any MIDI output? I've tried playing with minvolume and maxvolume, but they don't seem to have any effect on ChordName objects....

Also, it would be nice to be able to put one set of chords in brackets. Chord name exceptions only seem to be able to deal with text *after* the chords; so they can give me G) but not (G). Any ideas?

Thanks,
        Tim
        =-=


_______________________________________________
lilypond-user mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/lilypond-user




reply via email to

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