Bryan Creer wrote:
>Phil Taylor says -
>
>>The system of using ^ and _ to
>>denote annotations over or under the staff was proposed by Wil Macaulay
>>about two years ago and incorporated in the next version of BarFly
>>(which also allows < and > to place the annotation to the left or right
>>of th
Bryan, I think you've hit on the nub of the (pick one) disagreement/
argument/difference in world view between yourself and many of
the people on this list
[EMAIL PROTECTED] wrote:
> Phil Taylor says -
>
> >The system of using ^ and _ to
> >denote annotations over or under the staff was proposed
John Chambers says -
>Except that these are value judgements, and one person't "better" is often
>another person's "worse".
Well, my "better" is more consistent, more reliable and more usable if that
is someone else's "worse" that's their problem.
>I think it is valued, especially in the sens
Richard Robinson wrote:
>On Wed, 24 Jan 2001, Jack Campin wrote:
>
>> > The only other course open to someone determined not to pay
>> > for software but still wanting special funstions is to do
>> > what the rest of us do - get out gcc / emacs / TeX and get started!
>>
>> I'd like to, but (a) th
Phil Taylor wrote:
>John Walsh wrote:
>>[...]
>>M:3/8 L:1/8
>>F3|FFF|F3|FFF|F3|FFF|F3|FFF|F3|FFF|F3|FFF:|
>
>Surely the third voice is half as long again as the other two?
>If it were written like this it would be OK:
> [...]
>V:3
>M:3/8
>L:1/8
>F3|FFF|F3|FFF|F3|FFF|F3|FFF:|
No--there wa
Steve Mansfield said -
>My apologies, I omitted a .htm after extensions. You seem to have
>managed to locate the page eventually despite my error though.
Thanks Steve. Found it now. A lot of good stuff there.
>And how precisely is that 'not a widely held view'?
I share that view but a lot o
Here's my views:
1) Should it be a number and nothing else eg. V:1 V:2 ...
Not necessarily
2) Should it be nameable instead eg. V:soprano, V:alto ...
Yes - this subsumes numbers
3) Should it have parameters eg. V:1 nam=vocal clef=bass or should these
appear in local commands applicable to
Phil Taylor says -
>The system of using ^ and _ to
>denote annotations over or under the staff was proposed by Wil Macaulay
>about two years ago and incorporated in the next version of BarFly
>(which also allows < and > to place the annotation to the left or right
>of the note head when you want
At 07:46 AM 1/21/2001 -0500, Bryan wrote:
>Discuss the draft standard? Haven't seen a mention of it. Instead,
>different bits of it have been implemented in different ways in a piecemeal
>fashion. The classic example is the V: command which is described in the
>1.7.6 draft standard of May last
At 07:46 AM 1/21/2001 -0500, you wrote:
>The truth is that there are quite a few people who seem to regard abc as an
>input format for sophisticated notation printing. abc2ps is a minefield that
>I am not going to enter. Adaptations to suit this need seem to me to put the
>essential simplicity o
> "John" == John Chambers <[EMAIL PROTECTED]> writes:
John> So what it would take to get his tunes' titles into my index files is
John> probably a version of abc2ps that has an "ignore T: lines" option.
John> Then he could put the T: lines into his abc files and still get the
Hi, RJP
You have been able to sum up a confuse and misleading debate in a few words,
and make some sensible considerations, but you are wrong on one pont.
> > Developers are *not* the only people who get a say in what ABC ought
> > to be, or what it should be used for.
You wrote:
> O yes th
[EMAIL PROTECTED] wrote :
>From Steve Mansfield -
>
>>Try http://www.lesession.demon.co.uk/abc/abc_extensions#annot as a
>>starting place - and if I've documented them in there, they must be in one
>>of the abc standards documents on Chris W's site (I would suspect, but
>>haven't checked, in the
Bryan writes:
|
| 1) If you introduce this innovation for Jos=E9 it should be included in =
| the=20
| standard and hence wouldn't be invalid so wouldn't fall foul of validatio=
| n=20
| routines.
Yes. It may not have to be a major part of the standard. The idea
would be to encourage develop
| V:1 abcd abcd |
| V:2 ABCD ABCD |
Well, abc2ps rejects this, but it handles:
[V:1] abcd abcd |
[V:2] ABCD ABCD |
On user-friendliness grounds, I'd think that both should be legal.
But this implies something else: Users would then have to "declare"
voices in the header if they want to inc
James Allwright writes:
| > Hmm. Sort of like a tab stop?
| No, not like a tab stop at all.
|
| > Tell me, can you use that to
| > synchronize at other than a bar line?
|
...
| Since nobody yet seems to have even understood my description, I get
| the feeling that the concept is probably a bi
Definitely not the case with Windows, although the DOS software (for the
most part) appears to be free. ...and one can always ask the developers for
anything. Whether or not they think it worthwhile to implement is up to
them.
"Richard L Walker"<[EMAIL PROTECTED]>
Pensacola, FL 32504-7726 USA
>There are quite a lot of composition packages around already
>- some of them shareware. Would it not be better to keep
> abc simple and concentrate on providing means of importing
> / exporting abc to some of these packages?
This is exactly what happened in the case of Muse.
I added ABC to
It will probably take a while to get all of the bugs out, but
I've programed in TRUE BASIC an ABC player that will play in 12
tone equal temperament or 21 note just intonation. It doesn't
fully implement ABC standards: 1- no double sharps or flats
because in just intonation that requires 14 more n
On Wed, 24 Jan 2001, Jack Campin wrote:
> > The only other course open to someone determined not to pay
> > for software but still wanting special funstions is to do
> > what the rest of us do - get out gcc / emacs / TeX and get started!
>
> I'd like to, but (a) the abc2mtex port for the Mac do
>> Developers are *not* the only people who get a say in what ABC ought
>> to be, or what it should be used for.
> O yes they are! all the Linux software for abc is FREE, so I think
> nobody has the right to ask the `developers' to do ANYTHING. - without
> paying them that is!
The point is tha
Jack Campin wrote:
>Question prompted by the above: is there any ABC implementation out
>there with the ability to automatically place guitar chords or text
>annotations clear of notes on leger lines?
>
Yes, BarFly does! Try this:
X:1
T:test
M:C
K:C
"A"A2 "A"a2 "A"a'2 "A"a''2 | "A"A2 "A"A,2 "A
Somebody wrote:
> Laura:
> >> The reason the guitar chord notation got co-opted for text annotations
> >> is that many, many users needed a text annotation of some kind.
>
> Bryan:
> > No. This is a reason for developing a text annotation system, not a
> > reason for co-opting the guitar chord no
Laurie Griffiths asks -
>Can someone tell me how to access the ABC Users list archive.
>(Do we have one?)
Well, I've heard it mentioned but I don't know how to get at it.
The V: command has moved on since the issue you mention which I agree is
manageable.
The question now is on the format o
Jack Campin says -
>For one group of projects
>I needed something - anything - that would let me put 1700ish ornament
>signs into the ABC score and let me print them in staff notation after
>a fashion.
Well you could have asked Phil Taylor for extensions to BarFly to cover what
you needed and p
On Wednesday 24 January 2001 01:00, you wrote:
> Laura:
> >> The reason the guitar chord notation got co-opted for text annotations
> >> is that many, many users needed a text annotation of some kind.
>
> Bryan:
> > No. This is a reason for developing a text annotation system, not a
> > reason fo
>From Steve Mansfield -
>Try http://www.lesession.demon.co.uk/abc/abc_extensions#annot as a
>starting place - and if I've documented them in there, they must be in one
>of the abc standards documents on Chris W's site (I would suspect, but
>haven't checked, in the 1.7.6 proposal, as that's where
Laurie Griffiths says -
>Fare?? Fair, I think.
Neatly avoiding answering the point. Taking a chance aren't you Laurie?
You're going to have to triple check every post you send from now on in case
I spot a misplaced comma. Don't worry. Weather oar knot eye agree with watt
ewe say, I won't
Laurie wrote:
>I remembered a discussion a bit before that when there were two
>versions, one of which tended to present tunes as
>V:1
>
>V:2
>
>V:1
>
>V:2
>
>and another which did
>V:1
>
>V:2
>
>
>I remember Phil saying that to handle the one that he didn't
>you'd have to keep an internal copy o
James Allwright wrote:
>Since nobody yet seems to have even understood my description, I get
>the feeling that the concept is probably a bit too esoteric and confusing
>for the abc community.
>
I think I understood it OK. Perhaps the word Synch is a bit confusing,
since it implies that the voic
On Wed 24 Jan 2001 at 12:19AM -0800, John Walsh wrote:
>
> Hmm. Sort of like a tab stop?
No, not like a tab stop at all.
> Tell me, can you use that to
> synchronize at other than a bar line?
Yes, the idea is that voices can be synchronized whenever there is the
same musical time in e
Bryan said:
>Which discussion was this? It has cropped up several times.
> The significant one was in the second half of November when
> I think you were out in the Atlantic. (How did it go by the way?
The fact that I'm alive means that it went well!
Can someone tell me how to access th
John Walsh wrote:
>X:7
>T:Polyrhythmic with No Coherent Bar Division
>Z:The notes line up, but the bars don't
>B:MusiXTeX doc p 47
>M:3/4
>L:1/8
>K:C
>V:1
>F2 F2 F2|F2 F2 F2||F2 F2 F2|F2 F2 F2:|
>V:2
>M:2/4
>F2 F2|F2 F2|F2 F2||F2 F2|F2 F2|F2 F2:|
>V:3
>M:3/8 L:1/8
>F3|FFF|F3|FFF|F3|FFF|F3|FFF|F3|F
James Allwright writes:
>The idea is that we introduce another V: directive
>
V:SYNC
>
>which marks the point in the abc where all the currently active voices
>synchronize together and we go back into a global mode. Any K:, L: or
>Q: field from this point on will apply to all voices (so we have a
34 matches
Mail list logo
