>>>>> "Phil" == Phil Taylor <[EMAIL PROTECTED]> writes:
Phil> (You'll have to move the K: field to the end of the header
Phil> where it belongs, and also put a bar line at the end of each
Phil> line, otherwise BarFly will display it all on one line.)
I don't think there are fields after the K: field that aren't
allowable in the body of the tune. (OK, the standard doesn't say that
about N, but I think it should about some note field, and I think it
does about T:, M:, and L:.)
And as far as needing a barline where there isn't an end of a measure,
I'm sure that's a bug in barfly.
>> and in general, since you can
>> specify arbitrary note lengths in abc, is there any consensus on
>> how something like
>>
>> X:1
>> T:Wierd lengths
>> L:1/8
>> M:C
>> K:C
>> a5 b9 c11 a17
>>
>> should be displayed?
>>
Phil> I don't think odd note lengths like that should be used in
Phil> music which is intended to be displayed (although they might
Phil> be useful for music which is intended only to be played).
Phil> You can, of course write them as a4-a, b8-b etc., but there
Phil> are several alternative ways of splitting them up, and this
Phil> affects the appearance of the music, so although it could be
Phil> done by programs which interpret the abc, it's probably
Phil> better to be done by the transcriber.
I agree about the multiple ways of displaying a17, but what about a16?
If I want to transport ABC from a program that knows what a longa
looks like to one that doesn't, how should I do that?
--
Laura (mailto:[EMAIL PROTECTED])
http://www.laymusic.org : Putting live music back in the living room.
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
