For extensions above the triad, you have to specify all the notes in the stack up to the extension you want named: e.g., d1:7 for D7, d1:7.9 for D9, d1:7.9.11 for D11, d1:7.9.11+ for D9#11, d1:7.5- for D7b5, d1:7.9.11.13 to get a chord to render as "D13.” Etc. If you input d1:13 you'll get odd results like the D9add13; Lilypond doesn’t assume the voices below the highest extension like a musician would but instead is very literal.
Also, if you input a chord that doesn’t specifically exist in your Brandt/Roemer file, Lilypond will default back to the Ignatziek names. Even after 15 years of using a .ily file with the Brandt/Roemer style chord names, I’ll still occasionally have one sneak through and have to update the .ily file. > On Aug 3, 2026, at 2:49 PM, Carl Sorensen <[email protected]> wrote: > > > > On Mon, Aug 3, 2026, 1:35 PM Eric Benson <[email protected] > <mailto:[email protected]>> wrote: >> I started experimenting with LilyPond's ChordGrid display. I can't find very >> many examples using it, so I guess it isn't very popular yet. I'm using >> Brandt and Roemer chord names instead of the built-in Ignatzek chord names, >> using chordNameExceptions for that purpose. It looks like ChordGrid doesn't >> follow chordNameExceptions. Am I doing something wrong, or is that >> intentional? Is there another way to supply my own chord names in the >> ChordGrid context? > > > Please post a small example to the lists we can see what you're trying. > > Thanks, > > Carl
