Phil Taylor a skrivas:
[snip]
> The other problem is that BarFly puts lots of stuff into the V:
> header fields:
> (stems) up, down, merge (voice onto previous staff), mute,
> pan (stereo), clef, middle, playtransposed, brackets on and off
> and probably a few more things that I've forgotten. I want, as
> far as possible to keep all of this stuff out of the tune for the
> sake of readability. Wherever it gets put, it has to be in a
> numbered field, because it's all specific to one voice. You don't
> have to look at it to read the abc, so it's best kept in the header
> rather than in the tune itself.
These information should not be in the voice, but rather in a staff
definition: a same voice may go on many staves:
- in time:
- moving from one staff to some other one (floating voices, i.e.
voices which are better displayed on treble -upper staff- or bass
clefs -lower staff-, or voices which exchange their staff position
-organ keyboard change).
- keeping mute for some time (I have organ pieces which have 4 and
then 3 voices at the beginning -3 staves-, 2 voices in the middle
-2 staves- and are ending with 3 voices -3 staves-; I also have
pieces where 3 voices are used, but only 2 are played at the same
time -we have only 2 hands:)-)
- in space:
- when being displayed on many staves at the same time (master
score, song/instrument score).
Then, don't confuse playing and displaying:
- stems up/down, clef, bracket, .. is displaying stuff and it is
staff related,
- transpose, pan (stereo), absolute pitch (note frequency), MIDI
channel(s), .. is playing stuff and it is voice related.
I think these indications should go in different ABC fields. More,
it would be nice to have a common way to define them at program
call (as for extracting some parts/voices of a tune)...
--
Ken ar c'henta� | ** Breizh ha Linux atav! **
| http://moinejf.free.fr/
P�p� Jef | please, on reply, mailto:[EMAIL PROTECTED]
| or mailto:[EMAIL PROTECTED]
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
