Re: [abcusers] Re: Standard: =a proposal for intonation
- David Webber wrote:
> In a way. The assumption that these two routes should lead to soundsIt is just a case of an imperfect example in the specification. Recall
> different in pitch seems to be the problem. A well-conceived music
> notation file (of whatever format) should behave in the same way in
> each case.
that transposition (including octave transposition, K:.. octave=..) was
just recently standardized. There are several files in the real world
that were based in different features of different programs, and yet
files that were specifically written for a single program, ignoring
if/how other programs would interpret them.
As it is, middle= only applies to score, and is intended to avoid
writting many commas in low octaves. To sound right, the music should
include a %%MIDI octave instruction, omited in the example -- is was
that caused the confusion.
* Display clef where wanted for instructional matters.
Simon Wascher wrote:
> Am 05.05.2012 um 18:05 schrieb scheutzow4cond:
>> In my view, "clef=none" means: do not draw any clef here, but display the music as specified in the "middle=" clause, or by default as if a treble clef were present. A new directive "%%suppress..." would be handy for people who do not want to see a clef at the start of every score line, but only at the beginning and whenever clefs *change*. An analogous directive should be introduced for the time signature.
>>> * how to make clear that any usage with the meaning "suppress clef" is an abuse of the standard.
>> The only such "abuse" (or makeshift = Notlösung) I can think of is to try to achieve the effect of the future "%%suppress..." by starting a voice, say, with "clef=bass", and put "K:clef=none middle=D," after the first bar line. It usually works but requires care.
>> A good keyword for that may be something like "%%suppress-repeated-clefs".
> it seems there are several cases of "suppress-clefs", as clefs get drawn automatically (not in the abc text) at several positions in the score:
> * at the beginning of the notation,
> * repeated clefs at the beginning of any new line,
> * a clef at key-changes
> * extra clefs before linebreak if there is a key-change at newline.
> * clefs at clef-changes.
> * extra clef before linebreak if there is a clef-change at newline.
> a good "suppress-clefs" standard should be able suppress clefs in all possible (sensible?) combinations
> The following case I would think is the default behaviour:
> * DRAW clef at the beginning of the notation,
> * DRAW repeated clefs at the beginning of any new line,
> * DRAW clef at key-changes
> * SUPPRESS extra clef before linebreak if there is a key-change at newline.
> * DRAW clef at clef-change.
> * SUPPRESS extra clef before linebreak if there is a clef-change at newline.
> this gives the need for keywords having the following meaning, which can be combined:
> * DRAW extra clefs before linebreak if there is a key-change at newline
> * DRAW extra clefs before linebreak if there is a clef-change at newline (unusual)
> * SUPPRESS clef at the beginning of the notation AND SUPPRESS all repeated clefs at the beginning of any new line
> * SUPPRESS repeated clefs at the beginning of any new line
> * SUPPRESS clef at key-changes (only show key-signature)
> (suppress clef at clef-change seems not to be sensible)
> * the default behaviour is reestablished with the appearing of the next clef command notated in the abc-text.
> additionally a "SUPPRESS THIS clef" command could be handy, in cases where one is happy with the default behaviour but for whatever reason wants to suppress the display of one clef.
> kind regards,
> Yahoo! Groups Links