John Chambers wrote:
>It would be better to adopt notation that says unambiguously how the
>clef and ABC notes are to map to the staff. Possibly the simplest and
>least confusing scheme was mentioned by someone (who was it?) a few
>months ago: Give a clef=<name> and also a middle=<note> clause if you
>want to be precise. The clef name could be one of the three letters
>CFG, or one of the three common English names. (Maybe we should
>include the Italian names, too?)
>
This is the scheme I've adopted for the next version of BarFly.
Four extra fields can be (optionally) added to the K: field -
clef= <name>
middle= <note>
transposeplay= n <semitones>
capo= n <semitones>
The identifiers are all case-insesitive; spaces and the = are optional,
and the clef= identifier can be omitted altogether (since all the
clefs have unique names). For compatibility with MUSE, middle=,
transposeplay= and capo= can be abbreviated to m=, t= & c= respectively.
In the absence of these subfields, the defaults are as follows:
clef= treble
middle= depends on the current clef:
treble: B
alto: C
tenor: A,
bass: D,
gregorian clefs - always depends on the clef only (there's no
middle line on a four line staff:-)
transposeplay= 0
capo = 0
The capo field doesn't actually do anything in BarFly since it doesn't
play guitar chords. All of the subfields can be added to inline K:
fields to change things in mid-tune, and also to V: fields in the
header, so the initial settings for each voice can be set independantly.
Phil Taylor
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
