Re: [abcusers] Issues with abcm2ps---help!
On 20 Jul 2004 at 21:33, Andrew T. Lenz, Jr. wrote:
==
ISSUE 2:
PROBLEM: Bar linking 1/16th notes is split.
{g}f/e/{g}c/{d}A/
Here the first two (non-grace) notes are tied by a 1/16 bar and the
second two are tied also, BUT, between the e and the c, the 1/16th bar
is missing, that is, they are tied together by only the eighth note
single bar.
Have a look at the %%halfbeam command in the latest versions of
abcm2ps. With %%halfbeam 0, you will get full double (16th-note)
beamimg through your group of 16th notes. With %%halfbeam 1 (the
default) you get the group split into 8ths as you are seeing.
Unfortunately, with %%halfbeam 0, and a rhythm with interior 32nd
notes (i.e. L:1/16, ), the 32nds are drawn connected by a 32nd
beam, rather than with flags (or beam stubs?) pointing outward to the
dotted 16ths. %%halfbeam 1 does it dot-and-flag style. Perhaps Jean-
Francois could add a %%centerbeam command to choose which way to do it.
==
ISSUE 4:
Given a series of three gracenotes, is it possible to make the center
gracenote be appear as a 16th note instead of the standard 32nd?
You've already had a reply to this ( {ge2d} ) , but I thought I'd
mention that the gracenote-length modifier feature *is* documented in
features.txt in the Tune Body section.
cheers,
Ewan
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Making a book, how?
On 12 Mar 2004 at 15:09, Jeremy Cowgar wrote: On Fri, 2004-03-12 at 14:43, Ewan A. Macpherson wrote: On 12 Mar 2004 at 14:26, Jeremy Cowgar wrote: Can anyone give me some suggestions as to how I would create a nice book. I want to be able to give a copy or two away to other people who play with me, otherwise I would just print the resulting file from abcm2ps, but I would like to include a title page, table of contents, etc... I don't have my code handy, but I can send you examples later if you like. I would love to see some example code as I am new to really making abcm2ps do it's magic. I've snipped this down to two pages'-worth and an exemplary table of contents ... -- tunebook.abp, the file to run through abcpp %%pageheight 11in %%pagewidth 8.5in %%landscape 1 %%straightflags 1 %%stretchlast 1 %%topmargin 1.5cm %%printtempo 0 %%titleleft 1 % TITLE PAGE %%vskip 4in %%textfont Times-Roman 32 %%center Ann Arbor Pipes Drums %%center 2004 Tunebook %%textfont Times-Roman 16 % TABLE OF CONTENTS %%newpage #include contents.abc % PARADE SETS % %%header A2PD Tunebook 2004 2/4 Parade Set $P %%newpage 1 %%scale 0.65 #include gairloch.abc #include brownhair.abc % %%header A2PD Tunebook 2004 3/4 Parade Set $P %%newpage %%scale 0.68 #include greenhills.abc #include battleoer.abc % %% % LAST PAGE % %% %%header %%newpage %%vskip 5in %%center Compiled by Ewan A. Macpherson. %%center Typeset using abcm2ps by Jean-Francois Moine %%center and abcpp by Guido Gonzato. end of tunebook.abp -- contents.abc - %%center ANN ARBOR PIPES AND DRUMS TUNEBOOK 2004 %%center TABLE OF CONTENTS %%vskip .75in %%multicol start % set names %%begintext obeylines 2/4 Parade Set 3/4 Parade Set %%endtext % tune names %%multicol new %%leftmargin 6cm %%begintext obeylines The High Road to Gairloch Brown Haired Maiden The Green Hills of Tyrol When the Battle's O'er %%endtext % page numbers %%multicol new %%leftmargin 12cm %%begintext obeylines 1 1 2 2 %%endtext % start new TOC meta-column %%multicol new %%leftmargin 15cm %%begintext obeylines 2/4 Parade Set 3/4 Parade Set %%endtext %%multicol new %%leftmargin 20cm %%begintext obeylines The High Road to Gairloch Brown Haired Maiden The Green Hills of Tyrol When the Battle's O'er %%endtext %%multicol new %%leftmargin 25.5cm %%begintext obeylines 1 1 2 2 %%endtext %%multicol end - end of contents.abc --- cheers, e. To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] Uppity typesetting (was: gchordfont and alternate repeats)
On 25 Aug 2003 at 11:59, Jean-Francois Moine wrote: On Thu, 14 Aug 2003 15:42:30 -0400, Ewan A. Macpherson [EMAIL PROTECTED] wrote: I also note that as of 3.7.0, it [abcm2ps] puts in ... a double bar at end of line when next line starts with a repeat bar. It is so in most music scores I have. Granted, but what if *I* don't want it there? Now there's no way not to have it. I find this (new to abcm2ps) business of adding in notational elements not specified in the abc a bit disturbing. If a player program needs to insist on correct notation of repeats or whatever, fine, but a typesetting program shouldn't care. Any way to turn this off, Jef? I don't see what you expect... What I'm getting at is that I don't think an abc typesetting program should be making corrections like this. There is a fairly direct correspondance between the notational symbols in the abc file and what shows up on the rendered page. If a user *wants* a double bar they can write it in the abc file, and if they want something else they can specify that, and the typesetter should typeset it as specified. I guess I think the missing double bar should be treated like bar- length checking. If I give M:2/4 in the header and proceed to write the tune in 4/4, abcm2ps will issue a lot of too many notes in bar X warnings, but it will still only put in bar lines where they are specified and not add in new ones. I don't really care about the double-bar issue itself, but it seems like a departure from past practice to have the typesetter enforcing correct notation. with best wishes, e. To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] gchordfont and alternate repeats
On 14 Aug 2003 at 21:53, I. Oppenheim wrote: On Thu, 14 Aug 2003, Ewan A. Macpherson wrote: I was hoping to be able to use this to implement the mid-repeat variant notation, e.g. |: A A | B B | [1 c c] | [2 d d] | e e :| but unfortunately, abcm2ps also puts in a thick barline after the ']' instead of just closing the bracket. Since you typed a | after c], it seems logical to draw a barline. If you want an invisible barline, type [|]. If you don't want a barline at all, don't type |. In this case, I would want a barline, but the regular one I specified, not the extra-thick one abcm2ps puts in. In the case of |: A A | [1 B] [2 c] d | e e :| I wouldn't want a barline between the B and the c, but I would still get a thick one. I just ran these through 3.7.0, and in each case the first bracket was not actually closed, and the second one extended all the way to the :| cheers, e. cheers, e. To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] gchordfont and alternate repeats
On 14 Aug 2003 at 20:58, Richard Robinson wrote: On Thu, Aug 14, 2003 at 09:53:13PM +0200, I. Oppenheim wrote: On Thu, 14 Aug 2003, Ewan A. Macpherson wrote: I was hoping to be able to use this to implement the mid-repeat variant notation, e.g. |: A A | B B | [1 c c] | [2 d d] | e e :| Is the [ repeat a bracketed construct ? - ie is the closing ] necessary ? In this case yes, because my variant material does not go all the way to the end of the repeated section - it's floating in the middle. Please note that I'm just playing with what I see as a logical (and to me, useful) extension to the repeat/ending syntax - I didn't really expect this to work. cheers, e. To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] gchordfont and alternate repeats
On 14 Aug 2003 at 21:09, I. Oppenheim wrote: I found this in the abcm2ps doc (features.txt): The repeat indication may be explicitly stopped with a ']'. I was hoping to be able to use this to implement the mid-repeat variant notation, e.g. |: A A | B B | [1 c c] | [2 d d] | e e :| but unfortunately, abcm2ps also puts in a thick barline after the ']' instead of just closing the bracket. I also note that as of 3.7.0, it puts in ... a double bar at end of line when next line starts with a repeat bar. I find this (new to abcm2ps) business of adding in notational elements not specified in the abc a bit disturbing. If a player program needs to insist on correct notation of repeats or whatever, fine, but a typesetting program shouldn't care. Any way to turn this off, Jef? cheers, e. To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Re:abcm2ps and 'extras'
On 12 Aug 2003 at 21:03, Martin Tarenskeen wrote: Can anyone recommend some literature, or online documentation, about the Postscript language. A basic introduction or a complete syntax description, or something in between ? In terms of a basic introduction, I have found A First Guide to PostScript, http://www.cs.indiana.edu/docproject/programming/postscript/postscript.html very helpful. e. To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] A question about beams
On 11 Jul 2003 at 12:17, Wil Macaulay wrote: Skink does it the way you want. AFAIK, no other program will. Alasdair McAndrew wrote: Hi there, Suppose I have the following: defg Then there will be a single beam joining all notes, with an extra beam between the e and the f. But what I would like, rather than this extra beam, is an extra flag on the e pointing backwards, and an extra flag on the f pointing forwards. Is this possible with abc/abcm2ps? The latest release (3.6.4) of abcm2ps handles these sorts of broken beam cases the way Alasdair desires (i.e., to my mind, correctly) also. -- Ewan Macpherson To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] End of 2nd time bar
If there was a reply to this, I must have missed it in the recent
torrent of messages, so ...
On 9 Jul 2003 at 9:43, Bernard Hill wrote:
In message [EMAIL PROTECTED], John Chambers
[EMAIL PROTECTED] writes
Bernard Hill writes:
| In message [EMAIL PROTECTED], John Chambers
|
| I opened my copy of Scots Guards, flipped a few pages, and
| on page 15 I found this bar in The Inverness Gathering that
| (with L:1/16) could be written:
|
| ... |[1 {a}G2{d}G{e}G][2 d{e}G{gGd}G2] {gBd}B2{g}A{d}G | ...
|
| This is merely giving alternatives for the first half of
| the measure. As far as I can tell, this use of ] doesn't
| conflict with anything else in abc,
I must say that that example means nothing to me.
a What does it MEAN? Is it a 1st/2nd time bar with the section being
less than a bar?
Yes, there is some material (in this case, less than a bar) which is to
be played only the first time through the repeat. On the second time
through, that material is not played and the material inside [2 ... ]
is played instead. This second stuff is not played the first time
through. This is just a generalization of the endings mechanism, but
the conditional material does not lie at the end of the repeated
section.
If so, where is the repeat barline?
The material shown is in the middle of the repeated section, so the
repeat barlines aren't shown. As an another example:
|: | | [1 cc] [2 dd] ee | :|
b How do you expect it to be notated?
Each piece of conditional material should be surrounded by a closed
bracket, with a number (or other indication, such as 1st time)
indicating on which time through it should be played. Thus,
__ __
|1 ||2 |
|: | | cc dd ee | :|
c Is such a notation legal and clear in meaning?
It is not infrequently used in professionally engraved Highland pipe
music. It is clear in meaning, so there's no reason it shouldn't be
legal. Typically these sections are either N full bars or 1 bar in
length. I suppose things could get murky if there were a barline within
the bracketed section if its length was not an integer number of bars,
but I've never seen that in practice.
d How do you expect a playback to sound?
In my example above,
| | ccee |
| | ddee |
One might argue that there is no need for this notation, and that the
repeated section should be written out in full, but of course one
could argue that for repeats in general. The notation makes the
structure and variation of the repeated section very clear.
--
Ewan Macpherson
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] Gracenote timing in abcMus and elsewhere
Dear Henrik:
I'm greatly enjoying using abcMus version 2.0, particularly the multi-
voice MIDI file creation. I have a wish-list item which could improve
playback and MIDI file timing of multiple-gracenote sequences as occur
in Highland bagpipe music (my main abc application). This might also be
useful for other abc player and MIDI-rendering programs, so I'll CC
this to abcusers.
As far as I can tell, abcMus begins all gracenote sequences at the
nominal start-time of the note that follows. In other words, they steal
time from the following note. This works well for most short gracenote
groups, but some longer ones, such as taorluaths {GdGe} are definitely
meant to *end* when the following note begins and should steal all
their time from the preceding note.
Other gracenote groups have gracenotes that occur both before and after
the beat. For example in a c-doubling, {gcd}c , one school of the
thought has it that the c gracenote should start at the nominal start
time of the c melody note and the g gracenote should precede the beat,
stealing time from the previous note.
To allow for this, here is my suggestion: abcMus would use a (user
editable) file containing a list of gracenote timing templates. Each
template is simply a abc gracenote expression with a '.' added to show
where the zero-time of the embellishment falls. So in the examples
above, the taorluath template would be {GdGe.} and the c-doubling
template would be {g.cd}.
If no match for a given gracenote sequence were found in the template
file, the sequence would simply start on the beat as a default.
Wildcards could be used to cover several gracenote patterns, so {g.*d}
would cover most low-hand doublings. A specific match should over-ride
a wildcard, so if {.gcd} existed, it would trump {g.*d}.
I hope this makes sense! It would be great to hear whether you (or
anyone else) might be interested in implementing something along these
lines.
best wishes,
Ewan Macpherson
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Aligning bars across lines?
Jean-Francois Moine [EMAIL PROTECTED] wrote: On Fri, 4 Apr 2003 12:25:13 +1000, Alasdair McAndrew [EMAIL PROTECTED] wrote: I'm typesetting some highland bagpipe music, and sometimes it would be nice to have the bar lines aligned from one line to the next. Notes as well, if possible. Anyway, you may have quite the same thing using many voices. I explain: But, as there is still a bar on the left side, you will have to remove it manually editing the PostScript file (remove or comment the first line ending with 'bar' after the staff definition). This works very nicely! However, the time signature appears on each line. This can be fixed by commenting out all but the *last* occurrence of the lines ending in 'tsig' (or similar). These appear just below the first line ending in 'bar' that Jean-Francois refers to above. cheers, Ewan Macpherson To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] Mid-repeat variations in abcm2ps
I've recently managed to produce mid-repeat variation brackets in
abcm2ps by adapting the octava decoration. I'm finding it useful for
the occasional Highland pipe tune, and perhaps other will too. The
decoration is implemented using the %%postscript and %%deco pseudo-
comments. Having tinkered sufficiently (I hope) to see how it acts in
various cases and interacts with gracenotes, below are some examples of
usage. Obviously, this won't play properly anywhere, and as it only
works in abcm2ps, I have made liberal use of formatting pseudo-comments
in the examples as well.
To produce bracket decorations with different labels, one need only
duplicate the %%postscript definition (giving it a new name) and change
the text displayed. For example, one could copy the %%postscript chunk,
change (1) to (First time), and then add !first(! and !first)! %%deco
definitions.
As I've mentioned before, it would be great if we could come up with a
native abc notation for this sort of thing. So instead of
|: A4 | A4 | !1(!AB c!1)!d | !2(!cd e!2)!f | A4 :| % as below
we could use something like
|: A4 | A4 | [1 AB cd] | [2 cd ef] | A4 :|
the numeral following the '[' clearly distinguishing it from a chord.
Anyway, here goes ...
%%textfont Courier-New 12
%
% == postscript definitions - must be before any tune ==
%
% -- draw first time indication
%%postscript /firsttime { % usage: len x y firsttime
%%postscriptexch -9 add exch 2 copy
%%postscriptM 0 10 rmoveto /Times-Roman 16 selectfont (1) show
%%postscriptM 0 6 rlineto currentpoint stroke M
%%postscript 30 add 0 rlineto currentpoint stroke M
%%postscript 0 -6 rlineto stroke
%%postscript } bdef
%
% -- draw second time indication
%%postscript /secondtime { % usage: len x y secondtime
%%postscriptexch -9 add exch 2 copy
%%postscriptM 0 10 rmoveto /Times-Roman 16 selectfont (2) show
%%postscriptM 0 6 rlineto currentpoint stroke M
%%postscript 30 add 0 rlineto currentpoint stroke M
%%postscript 0 -6 rlineto stroke
%%postscript } bdef
%
% == decoration definitions ==
%
% -- start / stop of firsttime indication
%%deco 1( 5 - 24 0 0
%%deco 1) 5 firsttime 24 0 0
%
% -- start / stop of secondtime indication
%%deco 2( 5 - 24 0 0
%%deco 2) 5 secondtime 24 0 0
%
X:1
T:Mid-repeat variations
C:Ewan Macpherson [EMAIL PROTECTED]
M:2/4
L:1/8
K:HP
%%text Basic usage: The symbol for the end of the bracket comes
%%text *before* the final bracketed note.
%%text |: A4 | A4 | !1(!AB c!1)!d | !2(!cd e!2)!f | A4 :|
|: A4 | A4 | !1(!AB c!1)!d | !2(!cd e!2)!f | A4 :|
%
%%vskip 1cm
%%text To bracket a single note, put both begin and end codes
%%text *before* the note, with a spacer 'y' in between:
%%text |: A4 | A4 | !1(!y!1)!A2 !2(!y!2)!c2 B2 | A4 | A4 :|
|: A4 | A4 | !1(!y!1)!A2 !2(!y!2)!c2 B2 | A4 | A4 :|
%
%%vskip 1cm
%%text If the bracketed section begins with a gracenote, put a spacer
%%text between the bracket-start and the gracenote.
%%text |: A4 | A4 | !1(!y\{g\}AB c!1)!d | !2(!y\{g\}cd e!2)!f | A4 :|
|: A4 | A4 | !1(!y{g}AB c!1)!d | !2(!y{g}cd e!2)!f | A4 :|
%
%%vskip 1cm
%%text If the bracketed section ends with a gracenote, put the end
%%text code between the gracenote and the main note.
%%text |: A4 | A4 | !1(!AB c\{g\}!1)!d | !2(!cd e\{g\}!2)!f | A4 :|
|: A4 | A4 | !1(!AB c{g}!1)!d | !2(!cd e{g}!2)!f | A4 :|
%
%%vskip 1cm
%%text To bracket a single note with a gracenote, the order is:
%%text begin - spacer - gracenote - end - mainnote
%%text |: A4 | A4 | !1(!y\{g\}!1)!B2 !2(!y\{g\}!2)!c2 A2 | A4 :|
|: A4 | A4 | !1(!y{g}!1)!B2 !2(!y{g}!2)!c2 A2 | A4 :|
--
Ewan Macpherson
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Adding PostScript fonts?
Guido [EMAIL PROTECTED] asked: So, I'd like to know: 1) is it possible to add a new font to GhostScript, and how? 2) how can *abc*2ps use this new font, if at all possible? Under Windows, the file fonts.htm in the GhostScript doc directory explains how to add new fonts. I haven't tried this myself. cheers, Ewan Macpherson To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Typesetting piobaireachd with abc?
Jack Campin [EMAIL PROTECTED] wrote: I've seen optional bars in bagpipe and some other music, written with the usual sort of endings but with just the one bar bracketed. I don't believe I've ever seen that in a pipe score. On the other hand *alternate* single bars are quite common. We've discussed this before. I stick to the position I had then, which is that this feature is not as necessary as its prevalence in pipe music might indicate. I guess it's not necessary until you find you want to write things that way! By the same token, repeats and variant endings aren't strictly necessary - we could just write everything out linearly. That would, to be sure, waste space, but it would also remove the explicit indication of the structure of the tune which the repeat notation provides. I think the same case can be made for notating mid-repeat variants - they make structure explicit and thus help the performer. Its biggest user was David Glen, and it nearly always occurs near the bottom of the page for scores that only just fit on one sheet. He wasn't very good at planning layout before he picked up the punches and burin. These days, we have lithium for people with that kind of impatience and computers to help those that won't take it. This notation pops up regularly (if infrequently) in modern light music collections too. When Andrew Baker and I were discussing/suggesting this a couple of years ago, I did a quick survey through the two volumes of the Scots Guards Collection and found (as I recall) about a dozen instances in total. Most made sense musically as opposed to being kludgey space-savers. A notation whose main point is reproducing 19th century cockups isn't going to see much use. It's exceptionally difficult to learn to read it. Some of the Kilberry-style piobaireachd notation, where singling and doubling variants and AAB,ABB,AB-type structures are all nested and crammed onto one line are indeed hard to read. However, I've never found having a floating variant bar in the middle of a march or a jig part to be obscure. If 8 bars are repeated with a couple of notes different the second time around, I'd rather have those indicated explicitly than having to spot the pigeon with the whole 16 bars written out linearly. cheers, Ewan To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Typesetting piobaireachd with abc?
Henrik Norbeck [EMAIL PROTECTED] wrote:
(2) Optional bars in the middle of a part, with the possibility of
putting text over them such as Play in line 2 only?
[snip]
Jean-Francois Moine wrote:
You may put guitar chords (annotations) on bars, and abcm2ps handles
dashed bars (':' alone) and invisible bars ('[]'). Is it enough for
your purpose?
He wrote BARS, not barlines, so your answer unfortunately does
not cover his problem. I've seen piobaireachd in sheet music, and
they often have bars which are only played the second time
through in the middle of a part (not just at the end as with [1 and [2
in ABC).
I have not yet tried this, but it would seem to be possible to create
optional bar brackets in abcm2ps using the %%postscript and %%deco
pseudo-commands. See the 'octava' example in the file deco.abc
supplied with recent versions of abcm2ps. Using this won't make the
the conditional bars *play* correctly, of course.
cheers,
Ewan Macpherson
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Percussion notation...
On Thu, 23 May 2002, Atte Andre Jensen wrote: [EMAIL PROTECTED] I asked the guy who supplied me with this about the single line system, and he said that he couldn't think of any serious application for that. Modern Scottish snare drumming and the Swiss Basel style from which it derives both use the single-line system which Jack Campin described. See http://www.fastlane.net/~rbeckham/basl2.html http://hjem.get2net.dk/aapd/drummers_archive/trommenoder.htm for examples. cheers, e. To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Extended Repeats
John Chambers [EMAIL PROTECTED] wrote: Here's a brief description of the repeat/ending syntax that I've implemented in my jcabc2ps clone of abc2ps. This isn't a solution to all the world's repeat problems, but it does handle at least 95% of what you see in print. [snip] There were suggestions that the allowed chars include '+' and 'x', and I did include them in my implementation. I don't remember what the 'x' was supposed to mean; does anyone know? Andrew Baker and I had proposed a syntax in which xN meant to play a particular block of material N times *within* a repeat. Thus you could have |: AA |[1x2,3x5 BB :|[2x3 CC || This would be truly useful if we could get away from the idea that conditional material occurs only in endings. In piobaireachd, a section which plays | AA | AA | BB | AA | BB | BB | AA | BB || is generally put on the page as |:: [twice first time AA] | [twice second time BB] ::| i.e. |:: [1x2,2,3 AA] | [1,2x2,3 BB] ::| I've also been contemplating solving the need for random text such as last time under an ending bracket. This obviously needs quotes, and has syntax problems after a bar line. What I think would work is to say that you must use the '[' in this case, and you can then write |: CEC DED |1-3 EGE FAF :|2,4 EFG FED :|[last time EFG ABc :| This looks like it would be intuitively obvious to a naive reader, and it doesn't seem to have any obvious syntax problem. The last time is not an accompaniment chord, because the chord notation can't immediately follow a bracket like this. The bracket isn't the start of a [CEGc] type chord, because such chords can't start with a double-quote char. It takes a while to verify that it works, but I think it does. The description then would say that the actual ending syntax is: [text This would be followed by saying that the quotes may be omitted if the text contains only the characters 0123456789,-, and the bracket may be omitted immediately after a (single) bar line '|'. In the usual cases, the bracket and quotes will be omitted; the full ending syntax is expected to be rare. Again, I think it would be better not to try to mix the flow control and the arbitrary text functions. Why not say that the flow control stuff is mandatory, and generates some default display text, but that text may be added to replace this? Thus ... |: CEC DED |1-3 EGE FAF :|2,4 EFG FED :|[5last time EFG ABc :| cheers, e. To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Extended Repeats
Buddha Buck [EMAIL PROTECTED] wrote: At 07:39 PM 04-18-2002 +, John Chambers you wrote: I've also been contemplating solving the need for random text such as last time under an ending bracket. This obviously needs quotes, and has syntax problems after a bar line. What I think would work is to say that you must use the '[' in this case, and you can then write |: CEC DED |1-3 EGE FAF :|2,4 EFG FED :|[last time EFG ABc :| I'm one of the people that feels that ABC should be able to be used to unambiguously describe a piece of music without the need for human intelligence to interpret it. As such, for the case of last repeat has a special variant, I don't think an arbitrary text string method is the right solution (it may be right for other things, but not for information on how to play the music). I would suggest that there be a special code used for things like that, such as a repeat-number beginning with '0x', (like 0xlast, 0xfirst, etc) that could be used to indicate alternate endings under special cases. Done right, it could be extensible to newer repeat patterns as needed in the future. I agree - keep the flow control characters mandatory and add a separate 'funky text' mechanism. cheers, e. To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Extended Repeats
John Chambers [EMAIL PROTECTED] wrote: But this does remind me of Yet Another Extension that I've been thinking of proposing. The problem is that there's no way to mark the end of an ending. A possible solution that's backwards compatible and wouldn't break any current abc is to say that ']' may be used to terminate endings. If there isn't a matching ']', then the first :| or any sort of double bar terminates the ending. This would allow the ']' to be omitted for all the normal cases with endings of equal length. Then you could write: |: ... | ... |[1 ... ]:|[2 ... | ... ]| I guess I don't understand why there's a problem with endings of different lengths. Why do you need to mark the end of [2 here? Once past the :|, the player will just keep on going regardless, no? BUT, I am very excited by the proposal that ends of sections be markable with ']' because this is necessary to get away from the idea that conditional material only occurs at the *ends* of repeated sections. There are quite a few Highland pipe tunes in which a single bar in the middle of a repeated section is varied the second time around. This is usually notated by a mid-repeat [1 ][2 ] sort of contruct. Given a closing bracket, we could do this in abc also. So if the tune is: | AA | BB | CC | DD | | AA | BB | AC | DD | one could write: |: AA | BB | [1 CC][2 AC] | DD :| or even |: AA | BB | [1C][2A]C | DD :| % ie., a section need not be a whole bar cheers, e. To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] abcb2ps on Linux?
Jean-Francois Moine [EMAIL PROTECTED] wrote: On Wed, 26 Dec 2001 02:14:53 +, Jack Campin [EMAIL PROTECTED] wrote: Has anybody ported Eric Mrozek's abcb2ps (the bagpipe variant) to Linux? I just added: #include sys/stat.h in subs.h for compiling. | http://moinejf.free.fr/ JEF neglects to mention that his abcm2ps now supports K:HP and K:Hp with stem-down melody notes and 32nd gracenotes. Yay! -- Ewan Macpherson To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] something really simple
Frank Nordberg wrote: My favorite tempo indication is A little too fast ;-) Which beats mine, which is: So rasch wie möglich e. -- Ewan Macpherson [EMAIL PROTECTED] To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] possible abctab2ps extensions
Christoph Dalitz [EMAIL PROTECTED] wrote:
Ewan A. Macpherson wrote:
? (In the case that `grace' is not specified we could fall back to,
e.g., a standardized default of `grace=1/8'.
Except for K:Hp or K:HP, where the default should be 1/32 .
Was this the default in the old standard?
It is in Eric Mrozek's Highland-pipe-friendly version of abc2ps:
http://www.eecs.umich.edu/~mrozek/abc/abc2ps.html#bagpipe
which AFAIK is the only tadpole-producing abc software which implements
all the desired special behaviours which should invoked by K:Hp and
K:HP. The standard unfortunately doesn't mention the gracenote length
issue associated with K:HP, only the key sig and stem directions, but I
think this would be a reasonable default. K:HP is for Highland pipe
music specifically, and we like our gracenotes short (and slash-free)!
The standard itself doesn't say anything about how gracenotes should be
displayed. In the V1.6 standard, it says Grace notes have no time
value and so expressions such as {a2} or {ab} are not legal.
In the draft standard we have, Although nominally grace notes
have no melodic time value, expressions such as {a2} and {ab} can be
useful and are legal although some packages may ignore them.
cheers,
Ewan Macpherson
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] possible abctab2ps extensions
Christoph Dalitz [EMAIL PROTECTED] wrote:
2) rhythm of grace notes
abc supports grace notes, which are printed by abc2ps as eigth notes in
reduced size. A single grace note is printed as an eigth note with an
oblique stroke (ie. a short appogiatura in 19th century context).
While doing some transcriptions of viol sonatas, I need grace notes
which are not eigth notes. The straightforward implementation (allowing
rhythm factors in braces: {a//g//f//a//}) has a compatibility issue:
according to the old abc standard (or its interpretation that was
implemented in abc2ps), grace notes without a rhythm factor are of the
length 1/8 rather than that of the L: field.
Any suggestions?
The draft standard includes the idea that grace notes should have
modifiable lengths just like regular notes, and suggests that the
software package should set the default length, although it might be
more prudent to add this info to an extended L: field or create a new
field so that all the info is in the tune. This length should
definitely *not* be derived from the standard L: field itself. One
shouldn't have to change the way grace notes are indicated based on
changes in L:, and I defintely don't want to have to write a Highland
pipe jig (typical grace = 1/32) like:
L:1/8
K:HP
{g//}A{d//}A{e//}A {g//e//f//}e2 f | {g//}ec{G//}c {g//e//f//}e2
instead of the much more legible
L:1/8
K:HP
{g}A{d}A{e}A {gef}e2 f | {g}ec{G}c {gef}e2
cheers,
Ewan Macpherson
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] possible abctab2ps extensions
Anselm Lingnau [EMAIL PROTECTED] wrote:
How about
L:1/8 grace=1/32
K:HP
{g}A{d}A{e}A {gef}e2 f | {g}ec{G}c {gef}e2
Seems reasonable. Or maybe just
L:1/8 {1/32}
? (In the case that `grace' is not specified we could fall back to,
e.g., a standardized default of `grace=1/8'.
Except for K:Hp or K:HP, where the default should be 1/32 .
Within a tune, the
`grace' attribute should probably persist across `L:' changes that don't
introduce a new `grace' setting, for convenience.)
Indeed!
cheers,
Ewan Macpherson
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] free Finale
Mark Vandenbroeck [EMAIL PROTECTED] wrote: Is there any documentation on the Finale format (text or binary). I might give this abc2finale a try. There's a thesis on reading the the Enigma format at: http://linux.csn.ul.ie/~cahillm/thesis.html also see here (URL should be all on one line): http://www.s-line.de/homepages/ gerd_castan/compmus/notationformats_e.html#ETF e. -- Ewan Macpherson [EMAIL PROTECTED] WWW Bagpipe Index http://www-personal.umich.edu/~emacpher/pipes.html To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
