lilypond-auto
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lilypond-auto] Issue 703 in lilypond: Enhancement: TabStaff should


From: lilypond
Subject: Re: [Lilypond-auto] Issue 703 in lilypond: Enhancement: TabStaff should handle non-monotonic stringTunings
Date: Sun, 11 Jan 2015 19:25:59 +0000

Updates:
        Labels: -Patch-countdown Patch-needs_work

Comment #13 on issue 703 by address@hidden: Enhancement: TabStaff should handle non-monotonic stringTunings
https://code.google.com/p/lilypond/issues/detail?id=703

Fortunately all Americans are born with an innate knowledge of the banjo. The changed fingering gives the same correct pitch, but using the drone 5th string, which is shorter than the others, starting at fret number 5 or 6. The problem is that the change would require re-writing any existing LilyPond banjo music, or a convert-ly rule.

With the old rule (prefer the lowest-numbered string) banjo indicates the drone with a \5.

  music = << \key g\major
    \transpose c c' { g16*2 g a b g b a d g g a b g g fis fis }
    \repeat unfold 16 {s16 g'\5} >>
  << \new Staff \new Voice \music
     \new TabStaff \with {
       tablatureFormat = #fret-number-tablature-format-banjo
       stringTunings = #banjo-open-g-tuning
     } \music >>

With the proposed rule (prefer the highest-pitch string) writing banjo music we would need to specify the string numbers on non-drone pitches whenever the pitches went above the drone pitch, which would seem more difficult.

It seems that a string-preference order, maybe defined for each tuning, is the way to make both ukelele and banjo easy to enter.

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings



reply via email to

[Prev in Thread] Current Thread [Next in Thread]