> On Nov 27, 2024, at 11:39 AM, Knute Snortum <ksnor...@gmail.com> wrote:
> 
> On Wed, Nov 27, 2024 at 9:26 AM Tim's Bitstream via LilyPond user discussion 
> <lilypond-user@gnu.org <mailto:lilypond-user@gnu.org>> wrote:
> I am trying to get a G triad with added #11 in \chordmode.    G add #11 would 
> be fine on the lead sheet as would G (add #11).  So far Lilypond insists on 
> making it a G7#11 and other variants on this.  I even somehow got a G7sus4 9 
> once.
> 
> I am \include-ing roemer-chord.ly <http://roemer-chord.ly/> and have added 
> 
> <c e g fis'>-\markup {"add" \chordSharp "11" }
> 
> to no apparent avail.
> 
> I've tried various ways of calling this from the input file but haven't 
> figured out the right thing.  Currently I have g2:11+ resulting in G7#11 on 
> the lead sheet.  How do I get the dominant 7 to stop printing?  Seems like I 
> am missing something basic here.
> 
> FWIW I am using 2.19.83.  Updating Lily Pond to newer versions on the Mac 
> invariably involves breaking things, so I haven't gotten around to doing it.
> 
> Attached is a LilyPond file that will do "add2's" as well as "add+11's".  I 
> don't know if it works in 2.19.83.
> 
> 
> --
> Knute Snortum
> 
> <add2-demonstration.ly>

Thank you, that doesn’t compile with my antiquated install.  However, other 
than the much longer code for the # accidental, it looks syntactically the same 
as what I already have in roemer-chords.ly

Reply via email to