Re: Error in tablature automatic string and fret calculation for string one being the highest pitch
Carl Sorensen <[email protected]> Mon, 17 Nov 2025 19:31:29 +0000
| Newsgroups | gmane.comp.gnu.lilypond.bugs |
|---|---|
| Message-ID | <LV3PR22MB5101865D1CF1B368080CFD23EFC9A@LV3PR22MB5101.namprd22.prod.outlook.com> |
>> Tablature automatic string and fret calculations should proceed from >> the lowest-pitched string to the highest-pitched string. A context >> property is available to tell whether string one is the >> highest-pitch string. Setting highStringOne to ##t should have the >> calculation start with the highest-numbered string and proceed to >> the lowest-numbered string (which would be the lowest pitch to the >> highest pitch). The calculation instead starts from string one, >> regardless of the setting of highStringOne. [...] > >Thanks. Please open an issue! > > > Werner Done. Issue lilypond#6865<https://gitlab.com/lilypond/lilypond/-/issues/6865> Carl