> I'm not top posting.
(Sorry, I didn't know I should have sent the bug report to this list instead of
the google code bug tracker)
In the Following code, the `string 2' is tuned to `beh'.
The bug sets bih *and* cih to fret 1 on that same string,
and all other notes are not correctly set,
the tablature is always one fret down from the third note on.
Trying more variants I find it does have nothing to do with the pitch beh, but
maybe setting a quarter-tone tune to the second string will always triggers the
bug?
Also tested with git version from 27/jun/2011.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\makeStringTuning #'custom-tuning <eeh, a, d ges beh eeh'>
notes = {
beh\2 bih\2 cih'\2 deh'\2 dih'\2 eeh'\2
}
\score {
<<
\new Staff {
\clef "treble_8"
\notes
}
\new TabStaff {
\set TabStaff.stringTunings = #custom-tuning
\notes
}
>>
}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Changing the second string from beh to aeh is also buggy:
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\makeStringTuning #'custom-tuning <eeh, a, d ges aeh eeh'>
notes = {
beh\2 bih\2 cih'\2 deh'\2 dih'\2 eeh'\2
}
\score {
<<
\new Staff {
\clef "treble_8"
\notes
}
\new TabStaff {
\set TabStaff.stringTunings = #custom-tuning
\notes
}
>>
}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
