My point, exactly - unambiguous to a [human] player of the tradition,
but not unambiguous out of context. And although the R: field is
not standardized, BarFly does useful things with it...
My point was simply that the dots are not enough, and that's
part of the reason for adding extra control fields that set context.
Jack Campin wrote:
> > I think there are already examples where extra information
> > may need to be added in order to make abc unambiguous. A simple
> > example is making | Ac Bd | sound a little more like |A>c B>d |
> > simply by adding R:hornpipe to the header.
>
> except that hornpipes aren't always played dotted. You would need
> yet *another* level of extra information to say the style you're
> using is one where this dotted interpretation is appropriate.
>
> The R: field is long due for deprecation. There is no standard
> list of what rhythms it covers and what to do with them, and nobody
> seems interested in making it extensible in any way that would allow
> different users to agree on what their extensions mean. Why not
> just let it die so that the name can be reused for something more
> important and more definable?
>
> And some of the rhythmic types found in folk music are unimplementable
> by any playback software. A slow strathspey is intrinsically a form
> where the player is *expected* to do their own thing with the rhythm.
> They are only ever played solo. What is a MIDI program supposed to do
> with this? Rubato driven by a random number generator?
>
> =================== <http://www.purr.demon.co.uk/jack/> ===================
>
> To subscribe/unsubscribe, point your browser to:
>http://www.tullochgorm.com/lists.html
--
Wil Macaulay email: [EMAIL PROTECTED]
voice: +1-(905)-886-7818 xt2253 FAX: +1-(905)-886-7824
Syndesis Ltd. 28 Fulton Way Richmond Hill, Ont Canada L4B 1J5
"... pay no attention to the man behind the curtain ..."
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
