Okay, I updated my version of lilypond and it is almost perfect. Thank you!

Here is the main problem I see now. Lilypond favors the higher strings. Thus, lilypond will try to put the melody on the first string (which is the top string in the tablature). But, for dulcimer tablature, the strings are generally numbered in reverse order. Thus, if we keep the string labeled 1, 2, 3 then I want string 3 (the melody string) favored instead of string 1. This can be solved by manually telling lilypond which string to use, but that is a bit of a pain.

I put my snippet below to illustrate this. The first two measures are what I want (and did by manually entering the string number), the next two measures are what is generated automatically by lilypond.

Thanks!
Blake



\version "2.14.2"


notesA = \relative c' {
  g4\1 a\2 d4\3 e\3
  fis\3 g\3 a\3 b\3
}
notesB = \relative c' {
  g4  a d e
  fis g a b
}


<<
  \new Staff {
    \notesA
    \notesB
    }

  \new TabStaff
  \with {
    stringTunings = #`(
      ,(ly:make-pitch -1 1 0)
      ,(ly:make-pitch -1 5 0)
      ,(ly:make-pitch 0 1 0)
    )

    %TabStaff.stringTunings = #'(14 11 7 2 19 )

    fretLabels = #'(
    "0"   "0+"  "1"  "1+" "2"   "3"  "3+"  "4"  "4+"  "5"  "6"  "6+"
    "7"   "7+"  "8"  "8+" "9"  "10" "10+" "11" "11+" "12" "13" "13+"
    "14" "14+" "15" "15+" "16" "17" "17+" "18" "18+" "19" "20" "20+")
    tablatureFormat = #fret-letter-tablature-format
  }
  \new TabVoice {
    \notesA
    \notesB
  }




_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to