Am Mo., 11. Nov. 2019 um 21:38 Uhr schrieb Sandro Santilli <[email protected]>: > > I transcribed an A major song with this chords snippet: > > ees:m7.5- | aes:7 | aes:m7.5- | des:7 | > > When transposing it to Eb major it is rendered as: > > Bbbø | Ebb7 | Ebb7sus#4 b3 | Abb7 > > I don't understand why the third chord (m7.5-) > gets rendered as a "7sus#4 b3" chord, very hard > to read ... > > Ideally I'd also like to avoid the double flats, > but what strikes me is the "sus#4 b3" part, is it > a bug ? I'm using GNU LilyPond 2.18.2 and the > .ly file has a \version "2.18.2" header. > > --strk; >
If you transpose the note eeses down an augmented 4th the note beseses results. If you let the chords display in \new Staff you get a warning: 2.18.2: warning: Transposing eeses'' by ges makes alteration larger than double 2.19.83: warning: Could not find glyph-name for alteration -3/2 2.18.2 uses aes instead of beseses, thus the strange chord-name. To circumvent, you could do \transpose a dis instead. Though, tbh I doubt chords based on ees, aes, des _in_ a-major are correct at all. Probably some modulation/key-change before? Or copy from a weird source? Cheers, Harm
