Re: [abcusers] spam
On Thu, 2 Sep 2004, Bert Van Vreckem wrote: > Hello all, > > I got a message from Toby that he would try to clean up things. However, I > don't see much improvement as of yet... The problem is that the argyll.wisemagic.com mailserver acts as an open relay which tranfers any incomming spam message to the subscribers of this e-mail list. In the meanwhile, I managed to block the spam by using the following .procmailrc file: << MAILDIR=$HOME/mail LOGFILE=$HOME/procmail.log LOGABSTRACT=yes :0 * ^Received: from argyll.wisemagic.com * !^Subject:.*\[abcusers\].* /dev/null :0 $MAILDIR/in.box >> Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* ABC Standard: http://abc.sourceforge.net/standard/ Chazzanut Online: http://www.chazzanut.com/ Synagogue Choir: http://www.ask-choir.org/ Business: http://www.amsterdamhotelspecials.com/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] Copyright Issues addressed (fwd)
-- Forwarded message -- Date: Thu, 22 Jul 2004 09:00:02 -0400 From: George Robinson <[EMAIL PROTECTED]> To: World music from a Jewish slant <[EMAIL PROTECTED]> Subject: Copyright Issues addressed Pardon the cross-listing but since questions about copyright come up frequently on this list, I thought I'd direct your attention to this: Copyright Term and the Public Domain in the United States http://www.copyright.cornell.edu/training/Hirtle_Public_Domain.htm A reference chart to help you to determine the copyright status of a given work Best, g -- [EMAIL PROTECTED] -+ Hosted by Shamash: The Jewish Network, http://shamash.org/ a service of Hebrew College, which offers online courses and an online MA in Jewish Studies, http://hebrewcollege.edu/online/ To unsubscribe email [EMAIL PROTECTED] and have your message read: unsubscribe jewish-music -- [EMAIL PROTECTED] -= To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Mailing list archive
On Tue, 15 Jun 2004, Guy Gascoigne - Piggford wrote: > BTW is there an archive of this mailing list anywhere? You may find the mailing list archive here: http://www.mail-archive.com/[EMAIL PROTECTED]/ Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* ABC Standard: http://abc.sourceforge.net/standard/ Chazzanut Online: http://www.chazzanut.com/ Synagogue Choir: http://www.ask-choir.org/ Business: http://www.amsterdamhotelspecials.com/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] Re: BUS. OPP
On Thu, 3 Jun 2004, Wilson Li, Marketing Dept. (Skygain) wrote: > SKY GAIN has been approved by the ISO 9002 > certification. I guess this is the first ISO 9002 certified SPAM mailing I have ever received... I thought I honourable mail list admin would do something against these kind of messages... Groeten, Irwin Oppenheim ~~~* ABC Standard: http://abc.sourceforge.net/standard/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] something that ought to work...
On Fri, 16 Apr 2004, Neil Jennings wrote: > I will also have to add backquote as a separator. > Just a thought - are the text spacers supposed to > have any effect on the score, or just space the abc > listing? The backquote spacers are defined in ABC 2.0; They should have no effect at all on the score. See section [4.7. Beams]. > Is there any other source of abc definition apart > from draft 2.0? Things like merge do not seem to be > in there. In ABC 2.0, the merge feature is provided by the %%score directive, see section [11.1. Voice grouping]. The merge keyword is a BarFly extension. Note that ABC 2.0 specifically refers to these extensions in section [1. Introduction]: << Still, when using ABC it is good to be aware of the existence of such extensions. The extensions that were implemented by the major ABC packages have been described here: http://abc.sourceforge.net/standard/abc2midi.txt http://www.barfly.dial.pipex.com/bfextensions.html http://abc.sourceforge.net/standard/abcm2ps.txt http://www.lautengesellschaft.de/cdmm/userguide/userguide.html >> I hope that this answers your questions. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* ABC Standard: http://abc.sourceforge.net/standard/ Chazzanut Online: http://www.chazzanut.com/ Synagogue Choir: http://www.ask-choir.org/ Business: http://www.amsterdamhotelspecials.com/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] File Conversion
On Wed, 31 Mar 2004, Don Parrish-Bell wrote: > so my next question for all of you is does anyone > know of a program that will record a MIDI stream that > is being played through the sound card and store it > into a MIDI file. Connect your sound card to a keyboard that can record a Midi stream onto a floppy disk. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* ABC Standard: http://abc.sourceforge.net/standard/ Chazzanut Online: http://www.chazzanut.com/ Synagogue Choir: http://www.ask-choir.org/ Business: http://www.amsterdamhotelspecials.com/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] ABC and MusicXML
On Thu, 25 Mar 2004, Richard Robinson wrote: I concur: musicxml is a wondeful development, which will finally make it feasible to exchange scores between different music processing software, without loosing too much information. > http://www.qualmograph.org.uk/musicxml/ There's a small error in the example files on your webpage: the DOCTYPE tags refer to local file:// URLS, which won't work on other computers. > Are many ABC programs currently capable of generating MusicXML ? There's > a command-line Windows/Linux abc2xml There's also BarFly (Mac) and Noteedit (Linux). Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* ABC Standard: http://abc.sourceforge.net/standard/ Chazzanut Online: http://www.chazzanut.com/ Synagogue Choir: http://www.ask-choir.org/ Business: http://www.amsterdamhotelspecials.com/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Optional breath mark?
On Thu, 11 Mar 2004, Jeremy Cowgar wrote:
> but is it possible to create an optional breath mark? (') ... paren's
> around it?
Unfortunately, this seems not to be possible with
standard ABC. Either you could write some Postscript to
define your own special symbol, or you could use a
different symbol instead, like +plus+ to designate
optional breaths.
Groeten,
Irwin Oppenheim
[EMAIL PROTECTED]
~~~*
ABC Standard: http://abc.sourceforge.net/standard/
Chazzanut Online: http://www.chazzanut.com/
Synagogue Choir: http://www.ask-choir.org/
Business: http://www.amsterdamhotelspecials.com/
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Re: ABC 1.x continuations
On Sun, 14 Mar 2004, Phil Taylor wrote: > It's a pretty outrageous example. I don't think that parsers should > have to deal with continuations in the middle of inline fields, let > alone an example with another (non-inline) field inserted in the > middle. In ABC 2.0, continuations and ordinary comments will typically be dealt with by the scanner, before the parser even sees them. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* ABC Standard: http://abc.sourceforge.net/standard/ Chazzanut Online: http://www.chazzanut.com/ Synagogue Choir: http://www.ask-choir.org/ Business: http://www.amsterdamhotelspecials.com/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] voice overlay
On Mon, 15 Mar 2004, Tom Satter wrote: > The reason that I chose '(&' for start and '&)' for > end is that they are not ambiguous > > Having a single '&' mean "reset to last '(&' if given or to last > barline if not" would make sense to me. These remarks make sense. Maybe Jef could look into changing the abcm2ps syntax from (&... &... ) to (&... &... &) Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* ABC Standard: http://abc.sourceforge.net/standard/ Chazzanut Online: http://www.chazzanut.com/ Synagogue Choir: http://www.ask-choir.org/ Business: http://www.amsterdamhotelspecials.com/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Re: ABC 1.x continuations
On Fri, 12 Mar 2004, Steven Bennett wrote:
> So... If it can only occur on tune and lyric lines, and it can only occur
> where a staff break or lyric line break would be valid, then that is why I
> suggested a definition along the lines of:
>
> "A backslash ("\") at the end of a line means do not break the staff or
> lyric line at this point if that's what would happen because of the
> following line ending."
Steve,
I think you've made a thorough and clarifying analysis
of the actual 1.* backslash semantics. Now I understand
and appreciate what you've been trying to say.
I think your restatement of the 1.* backslash
rule is brilliant!
I will add a note about it to the backward
compatibility section of the ABC 2.0 draft.
Thank you for this\
contribution.
Groeten,
Irwin Oppenheim
[EMAIL PROTECTED]
~~~*
ABC Standard: http://abc.sourceforge.net/standard/
Chazzanut Online: http://www.chazzanut.com/
Synagogue Choir: http://www.ask-choir.org/
Business: http://www.amsterdamhotelspecials.com/
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] voice overlay
On Fri, 12 Mar 2004, Tom Satter wrote: > Voice overlays. Currently there is an error in the standard. >g4 f4 | e6 e2 &\ >(d8 | c6) c2 > w: ha-la-| lu-yoh &\ >lu- | -yoh > > However, while this looks nice, it will not work correctly > since the & will only back up to the barline, not to the > beginning of the line. Bingo! You found a bug in the standard. Thank you very much for reporting this. As you suggested, the example should have been something like: << g4 f4 &\ (d8| e6 e2 &\ c6) c2 w: ha-la- &\ lu-| lu-yoh &\ -yoh >> I will correct this shortly. > I would like to propose that we introduce three new > symbols: > > (& - start a voice overlay > && - reset time back to previous start point > &) - end a voice overlay I will follow this thread with interest; all suggestions will be considered for future revisions of the draft. I just would like to point out that Jef Moine has already implemented a similar extension in his excellent abcm2ps program. See his notes at: http://abc.sourceforge.net/standard/abcm2ps.txt Your proposed syntax seems to be better, though. > Which is still mighty peculiar and gets very, very ugly > if there are more than three measures with voice overlays > in one line. I also would like to note that the present voice overlay feature is precisely intended for handling short fragments of 2-3 measures; larger fragments can better be notated as an extra [V:] voice. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* ABC Standard: http://abc.sourceforge.net/standard/ Chazzanut Online: http://www.chazzanut.com/ Synagogue Choir: http://www.ask-choir.org/ Business: http://www.amsterdamhotelspecials.com/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Making a book, how?
On Fri, 12 Mar 2004, Jeremy Cowgar wrote: > But one question, is abc2mtex still supported? Does it support the newer > standards? What about multivoice extensions, etc??? Unfortunately, the author of abc2mtex stopped its development. There is no support for any of the new ABC extensions. > P.S. Ewan... I would still like to see some sample code. I am familure > with Abcm2ps and know that it is currently developed. Abcm2ps generates beautiful output and can certainly be used to make music books. It might be helpful to read the tutorial at http://abcplus.sf.net Another possibility is to use Lilypond (www.lilypond.org) which ships with an ABC converter. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.chazzanut.com/ Synagogue Choir: http://www.ask-choir.org/ Business: http://www.amsterdamhotelspecials.com/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] ABC 2.0 draft
On Fri, 12 Mar 2004, Manuel Reiter wrote: > I imagine this could be useful for > - mid-line changes of key or meter This is now handled by [K: ] and [M: ] > - mid-line program-specific directives e.g. for abcmidi This is now handled by [I: ] > Maybe someone could state shortly why distinguishing between 'music' > and 'other' lines for continuation is a bad idea? This is exactly what ABC 1.6 tried to do, and it was found to be overly complex and unclear in practice. The [...] syntax is a much cleaner and clearer way for achieving the same effect. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* ABC Standard: http://abc.sourceforge.net/standard/ Chazzanut Online: http://www.chazzanut.com/ Synagogue Choir: http://www.ask-choir.org/ Business: http://www.amsterdamhotelspecials.com/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Continuation Lines
On Thu, 11 Mar 2004, John Walsh wrote: > As I remember, the real problems with the > continuation---apart from the incompatibility of 1.6 > and 2.0---come when there was a mixed bag: several > staves, lyrics, etc. The bottom line of that discussion was, that continuations are of not much use in complex scores: in scores with multiple voices, it is not feasible to spell out the complete line formatting in the ABC file; instead the software should take care of it. To explicitly force the software to introduce a line break at some places, ABC 2.0 adopted the !-character. In general, the ABC 1.6 continuation mechanism was found to be overly complex, so ABC 2.0 replaced it with a more straightforward and simple mechanism. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* ABC Standard: http://abc.sourceforge.net/standard/ Chazzanut Online: http://www.chazzanut.com/ Synagogue Choir: http://www.ask-choir.org/ Business: http://www.amsterdamhotelspecials.com/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] ABC 2.0 vs. ABCPlus 2.0
Dear Tom, > Looking around, I found ABCPlus and started working > toward that specification. Today I saw the post by > Irwin about ABC 2.0 So, my question is - Are there > really two competing specs? No, these are not competing specs, but rather two documents which serve different goals. ABC Plus (http://abcplus.sourceforge.net/) is a very useful tutorial, i.e. a descriptive document directed at end-users, that explains how to use the specific ABC packages abcm2ps and abcmidi as they are right now, and suggests workarounds to overcome incompatibilities between these ABC packages. Other ABC implementations such as BarFly are not dealt with. This document was written by Guido Gonzato. On the other hand, ABC 2.0 (http://abc.sourceforge.net/standard/abc2-draft.html) is a specification, i.e. a normative document directed at software developers, that suggests how new ABC parsers should be built. This document took all available ABC packages and extensions into account, and specifically tried to overcome certain design mistakes and ambiguities in the preceding ABC standard. The document is the outcome of extensive discussions between users and developers on this mailing list, and contains contributions by many list members, including Guido Gonzato. The editing was done by yours faithfully. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* ABC Standard: http://abc.sourceforge.net/standard/ Chazzanut Online: http://www.chazzanut.com/ Synagogue Choir: http://www.ask-choir.org/ Business: http://www.amsterdamhotelspecials.com/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] ABC 2.0 draft
On Wed, 10 Mar 2004, Steven Bennett wrote: > I'm in the process of writing Yet Another ABC Parser > as part of a larger project I've been working on for > a while. Hi Steve, As the person responsible for the ABC 2.0 draft spec, I find it great that you are investing time in the development of ABC. Unfortunately, since last August I haven't had much time to work on the further clarification of the spec. (I'm afraid this will have to wait for summer again...); basically all I've been doing is lurking this list and taking notes for my todo list. Although the current draft is clearer and more comprehensive than 1.7.6, I'm the first to admit that there are still quite a lot of things in the draft that need to be ironed out. One of the main issues that need to be dealt with is an detailed analysis and determination of the allowed syntactical groupings in ABC. For example: should it be possible to have multiple voices [V:] within one part [P:], or should it be possible to have multiple parts in one voice? Personally I would opt for the first grouping, but the draft says nothing about it at present. Maybe Henrik Norbeck would still be willing to give some help in this part of the job? Furthermore, feedback from people (like you) who are writing a grammar for a real-life ABC parser would be very useful. Other things on the todo list: - proper definition of technical terms used (someone noticed that I never specified what I meant with the term "note group") - explicitly stating the differences between s: and w: lines (symbols can be aligned with barlines and rests, words cannot). - editing the section on stylesheets - editing the examples at the end of the spec > The quirk I'm wrestling with today is Continuation Lines, which seems to be > the biggest single area (and the biggest can of worms on the list archive) > where the 1.6 & 1.76 specs seriously conflict with the 2.0 draft spec. This is very true; conversely it was one of the biggest improvements in clarity of 2.0 over 1.76 > So I'm going to implement both and allow the user to decide which to > use via a runtime switch. This seems to be the only feasible option. > And this too %%and this isn't an xcommand %%-style commands may only appear at the start of a line, i.e. on a line by themselves. > % But is this a comment? If you display > % the history field, is it included? > % I believe the answer should be No... Correct. > And what about this? X \ > Would this appear on the same line as the "X" \ > If the history was displayed to the user? (IMHO, Yes) It would form one logical line. How the logical line is formatted on the display is up to the program. > And here's the real challenge: \ % oh boy > O: Is this the Origin or part of the History? > > I think it's part of the history myself > And that *this* line is the last line of the history. > O: This is the real origin... Both correct. > As for the 1.6 and 1.7.6 specifications, regardless of what program X, Y, or > Z does, the written spec is awfully vague. I have several possible > approaches to different elements of this, but the basic concept appears to > be that "\" at the end of a line isn't so much a continuation, but a "don't > break the staff here if you would normally". No. In 1.* it basically meant: continue on the next line of the same type. (Whereas in 2.0 it means: continue on the next physical line, regardless of the context) > The question becomes how to deal with comments. I saw plenty of discussion > of whether the "\" is ignored if it follows a comment, or whether it's > invalid if it isn't the very last character on the line. I guess it depends > on whether you look for the "\" first or the comment first. Is there any > consensus out there as to which is the proper approach when you are parsing > files using pre-2.0 continuations? (Or should I make *that* a user switch > as well...) The 2.0 spec is quite clear about this: first remove any end-of-line comments and whitespace, than look if there is a "\" at the end of the line and handle it. On the other hand, the 1.* spec did not allow anything to appear between the "\" and the end-of-line; it is not clear if it would allow a comment to appear before the continuation mark. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* ABC Standard: http://abc.sourceforge.net/standard/ Chazzanut Online: http://www.chazzanut.com/ Synagogue Choir: http://www.ask-choir.org/ Business: http://www.amsterdamhotelspecials.com/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] MusicXML 1.0 released - info from Slashdot
On Wed, 28 Jan 2004, Stephen Kellett wrote: > However given that this is the intended > "final solution" for music rendering, I thought folks may be interested. > I lifted this from Slashdot (http://www.slashdot.org). Stephen, thank you for drawing our attention to this slashdot feature. The whole discussion, in which ABC is also mentioned, can be followed here: http://slashdot.org/article.pl?sid=04/01/27/2051238&mode=thread&tid=141&tid=188 Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ ABC Standard: http://abc.sourceforge.net/standard/ === http://www.amsterdamhotelspecials.com/ === To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Could anyone help me installing abcm2ps?
On Tue, 16 Dec 2003, Emma wrote: Beste Emma, > d:\muziek\abcm2ps\abcm2ps.exe %1 -O d:\temp\Out.ps >> d:\muziek\abc2psLog.txt > d:\muziek\ghost\gsview\gsview32.exe d:\temp\Out.ps > > If I run the file, I get the message that there was no input file > specified. You should run the .bat file with the name of the input file as argument, thus: test.bat d:\muziek\test.abc Succes ermee en laat me weten of het nu wel goed gaat :-) Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ === www.amsterdamhotelspecials.com === To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Clarification wanted on abc draft standard 2.0 (fwd)
On Thu, 2 Oct 2003, Barry Say wrote: > > Under what circumstances would you want a word or > > symbol in the lyrics to align with a rest? > I have seen this in the case where words are spoken > are shouted or indications such as (clap) (stamp). > I think the question is why should it be forbidden? To maintain compatibility with existing ABC software and ABC music files. Currently, syllables will be aligned with the notes following a rest. Your suggestion to use percussion notes instead of rests for purposes like these, seems cleaner. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* The ABC Standard http://abc.sourceforge.net/standard/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] Clarification wanted on abc draft standard 2.0 (fwd)
-- Forwarded message -- Date: Sun, 28 Sep 2003 20:46:58 +0100 From: Neil Jennings <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Clarification wanted on abc draft standard 2.0 Hi, I write and distribute a shareware music program (HARMONY) whose main object was originally the addition of chords to tunes. One of the import formats I support is abc, and I would like clarification regarding aligned lyrics. In most cases, lyrics are NOT wanted on rests, but I have seen some files which DO use lyrics on rests. There is obviously no indication as to which is intended when reading a file. The abc standard (draft 2.0) says nothing about lyrics on rests, but the need DOES occur in some circumstances. Is it possible to state, and include in the standard, what should be done? Thanks Neil Jennings To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Linux: NoteEdit: export MusicXML
On Wed, 24 Sep 2003, Joerg Anders wrote: > Version 2.3.2 of the cost free ABC music exporting musical score > editor NoteEdit is available: > > http://rnvs.informatik.tu-chemnitz.de/~jan/noteedit/noteedit.html > > New features: > > - export MusicXML Wow, that is great news. You're program is getting better and better! Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* The ABC Music Project: http://abc.sourceforge.net/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Accented Characters
On Mon, 15 Sep 2003, Jon Freeman wrote: > I'd not want to be adding code to convert every post > in a thread (most of which don't contain abc) each > time the thread is opened. No, that's not a good idea. > I suppose I could look to converting from abc to HTML > when a post is made That is exactly what I would do; I would also insert a link to the original ABC file, where appropriate. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Accented Characters
On Mon, 15 Sep 2003, Jon Freeman wrote: > the dissapearing backslash would be a real headache, You mean that you have to type \\'a to get \'a ? That would be a bug in the script that you use to process the user input. > plus the lyrics of the song still need to display as > HTML. It is quite simple to write a script that converts e.g. \'a to รก in case you would like to display the ABC file as HTML. > Before I made my suggestion, Dave had said he > intended to use ALT-0224 style which appears to work > with our abcmps/pdf output, ABCMUS and with HTML. > There are doubts about how it would work with other > programs or platforms. This will only work reliably with ABC programs that have implemented the charset feature from the draft standard. Unfortunately, I don't think that this feature has been implemented so far. To make a long story short: currently the only way to go is to use \'a style accented letters and to fix your scripts so that they will deal with it correctly. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] ps viewer on windows?
On Thu, 28 Aug 2003, [iso-8859-1] Forgeot Eric wrote: > you can d/l eventually only GhostScript, GhostView is not really > needed, but it's much more conveniant to use in addition to GS. Strangely enough, the English word "eventually" has not the same meaning as the French word "eventuellement." In English, "eventually" is a synonym for "in the end". "Eventuellement" is best translated as "if you wish". Since the Dutch word "eventueel" means the same thing as the French "eventuellement", I've often made the same mistake in English myself. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] ps viewer on windows?
On Wed, 27 Aug 2003, Jon Freeman wrote: > There is a user interface called gsview available for > Windows but it just makes life easier. GSview is indeed the "official" name of the Ghostview package for windows, but in the real world everybody still calls it ghostview. So if you want to view PS files on windows, install these packages: 1. Ghostscript: ftp://mirror.cs.wisc.edu/pub/mirrors/ghost/AFPL/gs811/gs811w32.exe 2. Ghostview: ftp://mirror.cs.wisc.edu/pub/mirrors/ghost/ghostgum/beta/gsv441w32.exe The postscipt files will be associated with ghostview after it gets installed, so all you'll need to do to be able to view these files, is to click on them. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] ps viewer on windows?
On Tue, 26 Aug 2003 [EMAIL PROTECTED] wrote: > I tried installing ghostscript, but it doesn't work. > All I want to do is see the postscript files > generated by abcm2ps You need to install both ghostscript and ghostview. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] ABC as Tablature
On Thu, 21 Aug 2003, Frank Nordberg wrote: > So sorry, Eric. Although I suppose many of the > programmers here will disagree, I wouldn't say an > application is available for the average user unless > there is a ready-made and *tested* version of it for > the OS he/she is using. You claimed in your first e-mail that the application in question wasn't portable, upon which Eric pointed out that the application can be compiled on many platforms. Whether or not the application is easy to use for "avarage" users, is a completely different question, and has nothing to do with portability. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] ABC 2.0 avoiding line breaks
On Thu, 21 Aug 2003 [EMAIL PROTECTED] wrote: > I was wondering how I would encode the following in > accordance with 2.0 to avoid any linebreaks. Simplest solution: precede the example with a line %%continueall 1 otherwise, you would have to do the following: [V: 1] |:z4 |z4 |f2ec |_ddcc|\ cAB2 |cAAA |c3B|G2+fermata+Gz e4| etc. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] The abc Home Page
The page http://www.gre.ac.uk/~c.walshaw/abc/ is working again. Probably some admin made an error. Irwin On Sun, 17 Aug 2003, Peter Yarensky wrote: > I haven't seen anything about it since the notice that Chris Walshaw's abc > home page had disappeared, which I verified for myself. However, I was just > at John Chambers' abc site and clicked on the link for Chris Walshaw's > web-wide abc index to see what would happen. I was taken right to it, and > along with it, to the intact abc home page. So it still seems to be there, > even though it's not accessible in the usual fashion. > > Peter > > To subscribe/unsubscribe, point your browser to: > http://www.tullochgorm.com/lists.html To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] ties over alternate endings
You can send your bug reports to <[EMAIL PROTECTED]>, the maintainer of the abcm2ps program. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Re: backslashes
On Tue, 5 Aug 2003 [EMAIL PROTECTED] wrote: > 1/ Ignore comments except pseudo comments > 2/ Combine lines > 3/ Parse the resulting logical line > 4/ Parse pseudo comments I think the easiest solution would be to allow pseudo comments _only_ on a line by themselves. Then we could use the following scheme: A/ If the line starts with "%%", interpret the line as a pseudo comment, and go to the next line. ELSE: B1/ Treat everything starting from the first occurrence of "%" till end-of-line as white space. B2/ Combine lines. B3/ Parse the resulting logical line. This would allow: A,B,C \ % a line of music DEF But would not allow: %% MIDI voice P\ instrument=1 Wil (and others), would that be acceptable? Any other comments on the standard? Irwin To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] Changelog
The latest changes to the standard http://www.joods.nl/~chazzanut/abc/abc2-draft.html to reflect the discussion of today: 2.1. Remarks A '%' symbol will cause the remainder of any input line to be ignored. It can be used to add remarks to the end of an ABC line. Alternatively, you can use the syntax [r: remarks] to write remarks in the middle of a line of music. 2.2. Continuation of input lines If the last (non-space, non-remark) character on a line is a backslash (\), the next line should be appended to the current one, overwriting the backslash and any spaces or remarks that follow it, to make one long logical line. If the user would like to have a space between the two half lines, he should either type one before the backslash, or at the beginning of the next half line. Example: gf|e2dc B2A2|B2G2 E2D2|.G2.G2 \ % continuation GABc|d4 B2 w: Sa-ys my au-l' wan to your aul' wan\ Will~ye come to the Wa-x-ies dar-gle? There is no limit to the number of lines that may be appended together. 11. ABC Stylesheet specification An ABC stylesheet consists of directives which are interspersed in a normal ABC file, or collected in an ABC Header file (see section Include field). These are lines that _start_ with '%%', followed by keywords that give indications to typesetting or player programs. Some examples could be: %%papersize A4 %%pagebreak %%loudness 0.3 Alternatively, the directives may be contained in an I: (instruction) field: I:papersize A4 I:pagebreak I:loudness 0.3 There may be given only one directive per I: field. The inline field notation may be used to give a directive in the middle of a line of music: CDEFG[I:loudness 0.3]ABc If a program doesn't recognise a directive, it should just ignore it. === As always, your feedback is welcomed. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] P: and V:
Issue up to discussion. What should be the meaning of the following fragment: P:A [V:V1] C G C [V:V2] E B E P:B [V:V1] A E A [V:V2] C G C Or differently put: How, according to you, should P: and V: interact? Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] bass clef and transposition
Thank you for the tip. I changed it as you suggested. Irwin On Thu, 7 Aug 2003, Martin Tarenskeen wrote: > Found it. I would suggest to slightly change the section about the > defaults for each clef, to improve readability and avoid confusion. I > would change the following html code > > Defaults are treble: B, alto: C, > tenor: A,, bass: D, ; ... > > into: > > Defaults aretreble: B ; alto:C > ; tenor:A, ; bass:D, ; ... To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] man
On Wed, 6 Aug 2003, Phil Taylor wrote: > $ apropos backspace > Nothing found > > There probably is a keyword that will get it, but I couldn't find one. $ apropos filter which does the same thing as: $ man -k filter But the best solution is to go to: http://www.rocketaware.com/search.htm It has an engine that can do a full text search on all man pages. You can also install such an engine on your own computer: http://www.oac.uci.edu/indiv/ehood/man2html.html I use it all of the time. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] \ line continuation (was: Re: Changelog)
On Thu, 7 Aug 2003, Jeff Bigler wrote: > > 2.2. Continuation of input lines If the last (non-space, non-remark) > > character on a line is a backslash (\), the next line should be > > appended to the current one, overwriting the backslash and any spaces > > or remarks that follow it, to make one long logical line. > It breaks some other existing parts of the standard, including: >b) \,c (for c-cedille) and other commands that give accented > characters According to the ABC standard, end-of-line remarks start with the character '%'. So something like "\,c" or even "\ x y z" cannot possibly be interpreted as a continuation construct. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] Indiana Univ. sheet music online
The Indiana University Library has a website with online copies of a number of song cycles by the great 20th century composers, and even more... they have a section with complete Opera scores, Orchestral and Choral scores, Chamber music scores, Piano sheet music, etc. etc... http://www.dlib.indiana.edu/variations/ Quite interesting project. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] gchordfont and alternate repeats
On Wed, 13 Aug 2003, Christian Schnarrr wrote: > I tried to use abc2ps with > gchordfont Helvetica 20.0 > in my *.fmt file. > But the chords are now touched by the line of > [1 ... [2 ... :| > Is there a possibilaty to move the line of the repeat a little bit higher? Please download the latest version of abcm2ps (3.7.1) from abcplus.sf.net and everything will be fine. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Page break formatting
On Wed, 13 Aug 2003, Richard Robinson wrote: > The 2 situations, tune and page, have to be kept separate somehow, > it seems to me, they're on different levels. Yes. A newpage directive is only useful for applications that can deal with entire tunebooks, such as abcm2ps and potentially lilypond. Application that operate on the level of individual tunes, can better ignore it. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] gchordfont and alternate repeats
On Thu, 14 Aug 2003, Richard Robinson wrote: > Is the "[" repeat a bracketed construct ? - ie is the closing "]" > necessary ? Nope. abcm2ps introduced ] to indicate the end of a repeat section. It is not necessary. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] Linux: noteedit-2.3.0: score layout (fwd)
-- Forwarded message -- Date: Fri, 8 Aug 2003 20:34:57 +0200 (CEST) From: Joerg Anders <[EMAIL PROTECTED]> To: Texmaillist <[EMAIL PROTECTED]> Subject: [TeX-music] Linux: noteedit-2.3.0: score layout Version 2.3.0 of the cost free MusiXTeX exporting musical score editor NoteEdit is available: http://rnvs.informatik.tu-chemnitz.de/~jan/noteedit/noteedit.html New features: - score layout : braces (piano staffs), brackets (staff groups), continued/discontinued bar rules. Note! NoteEdit does its best to export the score layout. But depending on your typesetting system the score layout possibly changes (see below) - Hungarian GUI translation (thanks to Peter Breuer <[EMAIL PROTECTED]>) - end bar - multi repeats Note! The multi repeat influences the replay but the signature is only exported to MUP. (Perhaps some gurus can sometimes explain to me how to export this into to different typesetting systems). - UTF8 text coding in "*.not" files. This sould enable correct restore of Russian (Cyrillic), Greek, Hebrew, ... texts. Note! It does not mean it exports Russian, (Cyrillic), Greek, Hebrew, ... texts to MusiXTeX, LilyPond, ABC music, ...! I'm afraid I'd need a native language speaker with some C++ programming knowledge to solve this. Note further! This implies a small version incompatibility if you wrote lyrices and titles containing non-ascii characters :-( Please correct them on NoteEDit score and store them again. Note futher! I'm not quite sure whether this disturbs the KDE-2.x/Qt-2.x compatibility. - the # --> B / B --> # tool influences only the selected part (if any) this is especially usful after Midi import if the score has some B and some # parts. - bugs fixed, among them: + correct replay of dal segno al coda + correct MusiXTeX export of ending repeat close symbol + cleanup rests works (again) Problems exporting score layout === MusiXTeX actually accepts either completely continued or completely discontinued bar rules. If you specify a mix of partial continued and partial discontinued bar rules NoteEdit produces some statements of the musixdbr.tex package by Rainer Dunker. NoteEdit produces a warning and gives advice to install this package. Otherwise MusiXTeX will fail. PMX is a preprocessor to MusiXTeX and therefore the same problems apply. ABC music cannot deal with nested braces in brackets. NoteEdit will warn you. LilyPond can deal with braces and brackets. It changes the staff rules according to some LilyPond inherent rules. I was told it is possible to break these rules. But I assume they are there for good reasons. NoteEdit will warn you if a LilyPond rule will change the staff rule policy. MUP has no limitations. -- J.Anders, Chemnitz, GERMANY ([EMAIL PROTECTED]) ___ TeX-music mailing list [EMAIL PROTECTED] http://sunsite.dk/mailman/listinfo/tex-music To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Page break formatting
On Tue, 12 Aug 2003 [EMAIL PROTECTED] wrote: > The draft revision > -> http://www.joods.nl/~chazzanut/abc/abc2-draft.html > specifies %%pagebreak in 11. ABC Stylesheet specification That were only some hypothetical examples. I will take them out, since they are confusing. > and %%newpage in 11.4.5. Text That is the correct one. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] gchordfont and alternate repeats
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 |. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Page break formatting
On Tue, 12 Aug 2003, Martin Tarenskeen wrote: > A similar question: are %%staves (abcm2ps) and %%score (ab2-draft) > identical ? They are definitely not identical; the staves directive had some subtle problems, that made it necessary to introduce a new directive, as has been discussed on this list. > Which program uses %%score ? Currently the new features of the standard are not yet implemented; that will take some time. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Basel drum notation (was: abcm2ps and 'extras')
On Thu, 14 Aug 2003 [EMAIL PROTECTED] wrote: > K:perc basel > or something like that, and it will give me the staff I want. abcm2ps already supports [K:perc middle=B] if I'm not mistaken. So you would need to do is to extend it, to support the following notation: [K:perc middle=B stafflines=1] Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] include files
On Wed, 13 Aug 2003, John Chambers wrote: > This would also go along with the abc2ps gimmick of > reading global formatting info from a *.fmt file. For this and other purposes, the *.abh include files are proposed in the new standard. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Namespacing
On Tue, 5 Aug 2003 [EMAIL PROTECTED] wrote: > The problem with the pseudocomments as they stand is > that they aren't namespaced. Without namespacing you > run the risk of two applications using the same > pseudocomment but implementing it in different ways. As I announced on the list, the ABC 2.0 standard now has support for such namespacing as was suggested by David. (the support is for %%-directives and clef line specifiers) You can always read the latest version of the standard here: http://www.joods.nl/~chazzanut/abc/abc2-draft.html On Tue, 5 Aug 2003, Phil Taylor wrote: > >I think the easiest solution would be to allow > >pseudo comments _only_ on a line by themselves. > Me too. Not only does this make parsing easier, it > also draws attention to the pseudocomment, which > otherwise gets lost in the abc. > As Bryan says, a backslash followed by a comment at > the end of a line is not ruled out by abc 1.6, and I > think it important that we keep the new standard a > superset of the 1.6 standard. Glad that there is consensus. I will adopt the rules suggested by Bryan in the standard, with the understanding that pseudo comments may only appear on a line by themselves. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] Engraving Problems
The Lilypond website has recently been totally revamped. It now contains a very useful essay on common "Music Engraving errors" and outlines some of the complexities with which Music Engraving software has to deal: http://lilypond.org/web/about/automated-engraving/ Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] gchordfont and alternate repeats
On Wed, 13 Aug 2003, Christian Schnarrr wrote: > The lines of the alternate repeats are now (with > 3.7.1-1) stopping at the next barline an don't reache > the :|[2 and |] I found this in the abcm2ps doc (features.txt): The repeat indication may be explicitly stopped with a ']'. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] P: and V:
On Thu, 7 Aug 2003, Jack Campin wrote: > P:A > [V:V1] C G C > [V:V2] E B E > P:B > [V:V1] A E A > [V:V2] C G C So, would it be correct to state that P: resets the music generator when encountered in the tune body, and that the above example should thus be equivalent to the following: P:A K:C [V:A1] C G C [V:A2] E B E P:B K:Am [V:B1] A E A [V:B2] C G C > BarFly doesn't do this correctly yet, but in effect each part needs to > be interpreted as if it were a different tune, assembled into a medley > under the control of the P: header line. There will be some funnies > if global properties like key are reassigned within a part. I must admit that I do not understand this description. How do other programs handle P:/V: interaction and in what aspects does BarFly differ? Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] P: and V:
So the question seems to be--- When combining voices and part notation, should the voices be contained in a part, in which case the following notation is correct: > >P:A > >K:C > >[V:A1] C G C > >[V:A2] E B E > >P:B > >K:Am > >[V:B1] A E A > >[V:B2] C G C Or should the parts be contained in a voice, in which case the following notation is correct: > K:C > [V:1][P:A] C G C > [V:2][P:A] E B E > % > [V:1][P:B] A E A > [V:2][P:B] C G C These two concepts seem to be mutually exclusive, so I wonder which of these two concepts should be endorsed by the standard? BarFly seems to follow concept 2. Are there any ABC applications that follow concept 1? Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] ABC Music project page
Thanks to the good work of Bert Van Vreckem, the central ABC Music project page is now completely revamped: http://abc.sourceforge.net/ >From now on, the ABC Music Standard can be found on this page: http://abc.sourceforge.net/standard/abc2-draft.html Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] ABC 2.0 Compatibility with ABC2MTEX
On Wed, 6 Aug 2003, John Walsh wrote: > So there are two examples of people who use abc2mtex for > typesetting. But why not use Lilypond, which can do anything that abc2mtex could do and more? > There is even a *possible* project to bring it at > least partially up to date. Why not spend that energy to join forces with Laura to make the ABC import of lilypond better? Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] bass clef and transposition
On Wed, 6 Aug 2003, Martin Tarenskeen wrote: > Is there any concensus about what should be the notation standard for > notes in the bass key? The abc2-draft doc only describes notation in the > treble key. Yes, and it all spelled out in section 6 (clefs) of the standard. [K:bass middle=D] will achieve exactly what you want. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Re: backslashes
On Tue, 5 Aug 2003 [EMAIL PROTECTED] wrote: > It strikes me that there are three processes to carry out - > > Remove comments > Combine lines > Parse abc notation The order that the standard implicitly assumes, is: 1/ Combine lines 2/ Parse the resulting logical line 3/ Parse pseudo comments 4/ Ignore other comments > The above order seems the logical one to me and is > what I have already implemented in Abacus. That's also a reasonable approach. But what do you do with pseudo comments? If others agree, I can change the standard to follow the order that you suggest. > An earlier example - > > > G|G2G2A4|(FEF) D (A2G) G|\ > > w:She-nei zei-tim nich-__ra-tim_ be-\ > > M:4/4 % Measure Change\ > > K:Cย ย % Key Change\ > > c2c2(B2c2)|(f2e2)e2d G| > > w:gan na-'ul_ yats-_hi-ru. Le- This example was only given to show how absurd the semantics of the 1.6 standard were. Trust me, nobody understands this mess! The 2.0 standard will not allow any of this. See section [2.2. Continuation of input lines] in: http://www.joods.nl/~chazzanut/abc/abc2-draft.html Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Page break formatting
On Wed, 13 Aug 2003, Laura Conrad wrote: > >>>>> "Irwin" == I Oppenheim <[EMAIL PROTECTED]> writes: > > Irwin> Application that operate on the level of individual > Irwin> tunes, can better ignore it. > > > Are you assuming that all tunes fit on one page? Nope. > If not, it seems like one very well might need > %%newpage or some such within a tune. Unless an application can handle a complete tunebook in a well-defined way, you will never be sure how individual tunes will be formatted on the page, and consequently you won't know what the right position will be to insert a newpage directive. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] bass clef and transposition
On Thu, 7 Aug 2003, Buddha Buck wrote: > How would you interpret: > > V:1 clef=bass middle=c 1/ The bass clef is to be moved one line up, so that the middle line of the staff is a c instead of a d. 2/ Additionally, this indicates that the tune pitches are notated two octaves too high, since the default is D, > or (perversely) > > K:Cmaj clef=bass middle=^c This has no meaning, accidentals are not allowed here. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Re: backslashes
On Tue, 5 Aug 2003, John Chambers wrote: > | I think the easiest solution would be to allow pseudo > | comments _only_ on a line by themselves. > > Of course, many users (and programmers) would interpret this to > verify that [%%MIDI ...] is valid in the middle of a line. No. The standard is quite clear: Everything from the first '%' until end of line will be ignored. This means all the parser will see is '['. An alternative is that we could reuse the old I: notation to allow [I:MIDI voice P instrument=1] to be equivalent to: %%MIDI voice P instrument=1 For remarks that are not to be printed in the sheet music nor to be interpreted as directives, we could introduce an r: field: CDE[r: This is just a remark ]FGABc Any thoughts about this? Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] P: and V:
> % Variant I > P:A > K:C > [V:A1] C G C > [V:A2] E B E > P:B > K:Am > [V:B1] A E A > [V:B2] C G C > No - there's no need to rename the voices. There is no need to change the voice IDs; I was in fact wondering if it should be legal, i.e. if the music generator should build a fresh list of the voices at the start of each new part? > % Variant II > K:C > [V:1][P:A] C G C > [V:2][P:A] E B E > % > [V:1][P:B] A E A > [V:2][P:B] C G C On Thu, 7 Aug 2003, Jack Campin commented: > you get a part label on each voice, which looks > weird. There should only be one for all voices. > (Part label placement in BarFly is strange even for > single-voice tunes). > This way of doing things makes manipulation of parts > more work than it needs to be. It should be like > cut-and-paste of paragraphs in a word-processing > document; you don't need to type something at the > start of each line to say what paragraph it belongs > in. So, Jack, I take it that you prefer variant I over variant II? PS. both examples presuppose a line like "P:AB" in the header, but since the header is not relevant to the issue we're discussing, I left it out. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] new abcuser
On Tue, 5 Aug 2003, Martin Tarenskeen wrote: > The Atari binary can be downloaded from here: > http://www.home.zonnet.nl/m.tarenskeen/download/mozabcrt.zip I wanted to have a look at it, but could not find the source code (which would be more usable to me than an Atari binary). Is it available somewhere? Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] MS-DOS...
On Thu, 7 Aug 2003, Rickard Blixt wrote: > When I write abcm2ps and press Enter (I use abcm2ps), > a lot of text would roll up. How do I get it > readable, one screen at a time? type: abcm2ps | more Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] ABC 2.0 Compatibility with ABC2MTEX
On Wed, 6 Aug 2003, Martin Tarenskeen wrote: > I have just joined this mailinglist so I could also ask: where can I find > an archive of older threads/postings ? Go to: http://www.joods.nl/~chazzanut/abc/abc2-draft.html The introduction of the standard has, among other things, a pointer to the list archive. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] ABC 2.0 changelog
http://www.joods.nl/~chazzanut/abc/abc2-draft.html#Voice%20overlay Likewise, the & operator may be used in w: lyrics and in s: symbol lines, to provide a separate line of lyrics and symbols to each of the overlayed voices: g4 f4 | e6 e2 &\ (d8 | c6) c2 w: ha-la-| lu-yoh &\ lu- | -yoh Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Re: backslashes
On Tue, 5 Aug 2003, Wil Macaulay wrote: > 1. continued lines cannot have a trailing comment > 2. pseudocomments cannot be continued The current text of ABC 2.0 does not allow either. Ad. 1: "Comments can not be included on lines that end with a backslash." Ad. 2: "A '%' symbol will cause the remainder of any input line to be ignored." Bryans alternative proposal didn't seem unreasonable, if he can clearly indicate how pseudo comments should be parsed. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Re: backslashes
On Tue, 5 Aug 2003 [EMAIL PROTECTED] wrote: > >That's also a reasonable approach. But what do you do > >with pseudo comments? > > I'm not sure what you mean by pseudo comments. Could you give an example? %%gchordfont times 14 or %%abc-copyright (C) Copyright John Smith 2003 Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] backslashes
On Mon, 4 Aug 2003, John Walsh wrote: > (I presume that "anything that follows it" refers to spaces.) Correct. > Thus neither of the following will work: > > abc def| gab CDE| % comments\ > FGA BC| ... > > abc def| gab CDE|\ % comments > FGA BC| ... Correct. %-Comments may not appear on a continued line. However, you can use inline comments instead: abc def| gab CDE| [N: comments] \ FGA BC| ... Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] braces in brackets
On Mon, 4 Aug 2003, Bernard Hill wrote:
> String parts in an orchestral work are usually bracketed together (5
> staves) and the top two then braced (1st/2nd violins) outside the
> bracket.
>
> [{Vln1 Vln2} Vla Vc DB]
Thank you for this information. I will add that to the
standard.
Groeten,
Irwin Oppenheim
[EMAIL PROTECTED]
~~~*
Chazzanut Online:
http://www.joods.nl/~chazzanut/
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] braces in brackets
On Mon, 4 Aug 2003, Joerg Anders wrote:
> Is there a possibility to place braces inside brackes
> in staff layout. I tried:
>
> %%staves [ S1 { S2 S3 } S4 | ]
That is not possible. What would be the meaning of
such a notation?
You can of course typeset:
%%staves [S1 S2] {S3 S4} [S5 S6]
Groeten,
Irwin Oppenheim
[EMAIL PROTECTED]
~~~*
Chazzanut Online:
http://www.joods.nl/~chazzanut/
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] mensurstriche
On Mon, 4 Aug 2003, Anders Wiren wrote: > We have "invisible barline" [|] and we can specify "draw barlines between > staves". We also have dotted barlines .| in ABC. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] man
On Sun, 3 Aug 2003, Jeff Bigler wrote: > Much simpler, using vi as an example, would be: > > man vi | cat > vi.txt Maybe you have a super-cat installed on your system, but my cats pass all those backspace sequences through, so the above line would be simply equivalent with: man vi > vi.txt which does not do the job. However, the simple program that I wrote takes care of it. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] ABC 2.0 rc 4
I hereby request your feedback on the 4th revision
of the ABC draft standard:
http://www.joods.nl/~chazzanut/abc/abc2-draft.html
1] Since the semantics of the %%staves directive now
differ quite a lot from the original, I decided to
rename it to %%score. This way, old code cannot be
confused with new code. The %%score directive has now
support for floating voices, and by default won't
connect the bar lines between staves:
<<
Basic syntax:
%%score ...
The score directive specifies which voices should be
printed in the score and how they should be grouped on
the staves.
Voices that are enclosed by parentheses '()', will go
on one staff. Together they form a voice group. A voice
that is not enclosed by parentheses forms a voice group
on its own, that will be printed on a separate staff.
If voice groups are enclosed by brackets '[]', the
corresponding staves will be connected by a big bracket
printed in front of the staves. Together they form a
voice block.
If voice groups are enclosed by curly braces '{}', the
corresponding staves will be connected by a big curly
brace printed in front of the staves. Together they
form a voice block. This format is used especially for
typesetting keyboard music.
If voice blocks, or voice groups are separated from
each other by a '|' character, continued bar lines will
be drawn between the associated staves.
Example:
%%score Solo [(S A) (T B)] {RH | (LH1 LH2)}
If a single voice, surrounded by two voice groups, is
preceded by a star (*), the voice is marked to be
floating. This means, that the voice won't be printed
on it's own staff; rather the software should
automatically determine for each note of the voice,
whether it should be printed on the preceding staff or
on the following staff.
Software that does not support floating voices, may
simply print the voice on the preceding staff, as if it
were part of the preceding voice group.
Examples:
%%score {RH *M| LH}
%%score {(RH1 RH2) *M| (LH1 LH2)}
Voices that appear in the tune body, but not in the
score directive, won't be printed.
When the score directive occurs within the tune body,
it resets the music generator, so that voices may
appear and disappear for some period of time.
If no score directive is used, all voices that appear
in the tune body are printed on separate staves.
>>
2] Since barFly and abcMIDI interpret the %%MIDI
program directive differently, and there was no support
yet for MIDI banks in the proposed standard, I decided
to replace this directive with a new one called %%MIDI
voice:
<<
%%MIDI voice [] [instrument= [bank=]] [mute]
Assigns a MIDI instrument to the indicated ABC voice.
The MIDI instruments are organized in banks of 128
instruments each. Both the instruments and the banks
are numbered starting from one.
The General MIDI (GM) standard defines a portable,
numbered set of 128 instruments; these are listed in
section General MIDI Instruments. The GM instruments
can be used by selecting bank one. Since the contents
of the other MIDI banks is platform dependent, it is
highly recommended to only use the first MIDI bank in
tunes that are to be distributed.
The default bank number is one.
Example:
%%MIDI voice Tb instrument=59
assigns GM instrument 59 (tuba) to voice 'Tb'.
If the voice ID is ommited, the instrument is assigned
to the current voice:
M:C
L:1/8
Q:1/4=66
K:C
V:Rueckpos
%%MIDI voice instrument=53 bank=2
A3Bc2c2|d2e2de/f/P^c3/d/|d8|z8 |
V:Organo
%%MIDI voice instrument=73 bank=2
z2E2- E2AG|F2E2F2E2|F6 F2|E2CD E3F/G/|
You can use the keyword mute to mute the specified
voice.
Some ABC players can automatically generate an
accompaniment based on the chord symbols specified in
the melody line. To suggest a GM instrument for playing
this accompaniment, use the following directive:
%%MIDI chordprog 20 % Church organ
>>
3] I made clear what to do if there are spaces before
a hyphen in the lyrics line:
<<
w: syll-a--ble is aligned with four notes
w: syll-a -ble (equivalent to the previous line)
>>
4] I clearified the placement rules for annotations
5] I introduced the datatype "ABC string" and clearly
indicated throughout the document which ABC constructs
accept such a string. The definition of "ABC string"
appears at the bottom of the standard:
<<
8.2. ABC string
The contents of ABC strings may be written using any
character set. The default ABC string character set is
Latin-1, which is convenient since it is also the
default used in webpages. If you would like to use a
different character set, such as utf-8, you may find
more information in section Charset field.
To write non-English characters in ABC strings, special
sequences of characters should be used to avoid
portability problems. These sequences start with a
backslash (\), followed by an accent and a letter.
accent example how to write it
---
grave \`A \`a \`e \`o
acute
Re: [abcusers] chords & accidental semantics
On Sun, 3 Aug 2003, Bernard Hill wrote: > >Please can we have "yes" and "no" instead of numbers that have to be > >looked up in a manual? > > 0 and 1 are universally Off and On. Check a modern radio, TV, video > recorder or other electronic device sometime. ...but the problem was that 2 was also an allowed value. So on initial suggestion by Laura, I replaced those numbers with keywords in the standard. Irwin To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Parenthesis?/"Al Coda"?
On Sat, 2 Aug 2003 [EMAIL PROTECTED] wrote:
> >>With abcm2ps, how do I put a specific note in parenthesis?
>
> >"<(" ">)" C
> Irwin, this has come up before and doesn't work as
> you expect - you get ( above >) rather than a
> parenthesis either side of the note (with 3.3.1 that
> I'm using).
This has since then been fixed. Download the latest
development edition of abcm2ps and it will work as
intended.
> Perhaps this could be rectified in the 2.0 standard,
> or at least made clearer,
I'll put it on my todo list.
Irwin
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Parenthesis?/"Al Coda"?
On Sat, 2 Aug 2003, Rickard Blixt wrote:
> With abcm2ps, how do I put a specific note in parenthesis?
"<(" ">)" C
> What is the command for inserting the text "Al Coda"?
"^Al Coda"
Groeten,
Irwin Oppenheim
[EMAIL PROTECTED]
~~~*
Chazzanut Online:
http://www.joods.nl/~chazzanut/
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Floating voices
On Fri, 1 Aug 2003, Wil Macaulay wrote: > Given Bernard's statement, and that we are proposing > incompatibilities anyway, I would propose that you > only use a line if you _DO_ want barlines between > staves. In other words, the default is not to join > staves, but you can put a line between if you want > barlines. Seems like a sensible idea. Do others agree? Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Floating voices
On Fri, 1 Aug 2003, Bernard Hill wrote:
> Shouldn't that be
>
> %%staves Solo [(S A) | (T B)] | {RH (LH1 LH2)}
>
> since the barline would interfere with any words sung. The only regular
> place that barlines *are* drawn through is in keyboard work.
You're correct. Thank you!
Irwin
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] s: syntax
On Fri, 1 Aug 2003, Jean-Francois Moine wrote: > I think an other information header should exist, which gives a > completly different syntax: > > s: \ > bracket=[on | off] \ Jef, the proposed standard already uses s: for something different: << 2.24. Symbol lines Adding many symbols to a line of music can make a tune difficult to read. In such cases, a symbol line (a line that contains only symbols) can be used, analogous to a lyrics line. A symbol line starts with 's:', followed by a line of symbols. Matching of notes and symbols follows the rules defined in section Lyrics. Example: CDEF | G```AB`c s: +pp+ | +f+ ** +fff+ >> I know that you proposed "d:" as the name of this field, but that choise had a problem. Quoting the draft standard: << Field identifiers A-G and a-g will not be permitted in the body to avoid confusion with note symbols. >> http://www.joods.nl/~chazzanut/abc/abc2-draft.html Again, I'm always open for suggestions. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] Floating voices
Dear Jef,
I have written the following in the standard about
%%staves. Please read it carefully:
<<
8.1. Voice grouping
Basic syntax:
%%staves ...
The staves directive specifies which voices should be
printed in the score and how they should be grouped on
the staves. If no special characters are used, the
voices mentioned go on separate staves. Voices that
appear in the tune body, but not in the staves
directive, won't be printed.
If no staves directive is used, all voices that appear
in the tune body are printed on separate staves.
Voices that are enclosed by parentheses '()', will go
on one staff. Together they form a voice group.
If voice groups or single voices are enclosed by
brackets '[]', the corresponding staves will be
connected by a big bracket printed in front of the
staves. Together they form a voice block.
If voice groups or single voices are enclosed by curly
braces '{}', the corresponding staves will be connected
by a big curly brace printed in front of the staves.
Together they form a voice block. This format is used
especially for typesetting keyboard music.
If voice blocks, voice groups, or single voices are
separated from each other by a '|' character, no bar
lines will be drawn between the associated staves.
Example:
%%staves Solo [(S A) (T B)] | {RH (LH1 LH2)}
When the staves directive occurs within the tune body,
it resets the music generator, so that voices may
appear and disappear for some period of time.
>>
I think that these semantics are very clear, however
the syntax does not yet provide for floating voices.
I think that the syntax can be very easily extended to
make floating voices possible. Let's add the following
rule:
<< If a single voice, surrounded by two voice groups,
is preceded by a star (*), the voice is marked to be
floating. This means, that the voice won't be printed
on it's own staff; rather the software will
automatically determine for each note of the voice,
whether it should be printed on the preceding staff or
on the following staff.
Software that does not support floating voices, may
simply print the voice on the preceding staff, as if it
were part of the preceding voice group.
Examples:
%%staves [(S A) *T (B1 B2)]
%%staves [S *A T]
>>
Jef and others, let me know what you think about this!
Groeten,
Irwin Oppenheim
[EMAIL PROTECTED]
~~~*
Chazzanut Online:
http://www.joods.nl/~chazzanut/
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] w: \
On Fri, 1 Aug 2003, Guido Gonzato wrote: > G|G2G2A4|(FEF) D (A2G) G| [M:4/4] [K:C] > c2c2(B2c2)|(f2e2)e2d G| > > the second line has 9 notes. I suspect that you probably meant to join > these two lines with \. In the mail that I sent out, (and in the example that I tested!) these two lines were one physical line! They were wrapped by some mail software in between---I suspected that you would understand that... > this typesets perfectly with abcm2ps, passably with yaps, and badly with > jcabc2ps. I tested it also with: ...abcMus, abacus, muse, skink and barFly; then I gave up. Of all those, Abcm2ps was the only app that had no problems with the \ business in all it's glory, ahum... Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] w: \
On Fri, 1 Aug 2003, Guido Gonzato wrote: > > << > > X:1 > > T:Shenei Zeitim > > M:4/4 > > K:C > > G|G2G2A4|(FEF) D (A2G) G| [M:4/4] [K:C] > > c2c2(B2c2)|(f2e2)e2d G| > > w:She-nei zei-tim nich-__ra-tim_ \ > > w:be-gan na-'ul_ yats-_hi-ru. Le- > > G|G2G2A4|(FEF) D (A2G) G|\ > > w:She-nei zei-tim nich-__ra-tim_ be-\ > > M:4/4 % Measure Change\ > > K:C % Key Change\ > > c2c2(B2c2)|(f2e2)e2d G| > > w:gan na-'ul_ yats-_hi-ru. Le- > > how can you possibly think the above works? Try and count the number of > notes corresponding syllables. Guido, I know I'm a little stupid, but I can't be _that_ stupid... If you count carefully, you will notice that both the music and the lyrics consist of 20 syllables. Note: "__" are two underscores next to each other! Furthermore, note that especially the second part of my example will cause problems with some parsers (while I noticed that the first part of the example was not understood by at least 2 parsers). Summarizing: it is a fact that the given example is not portable (while it is correct), at the same time it is my personal opinion that this continuation mechanism is overly complex, and my thesis is that too much complexity leads to incorrect parsers and unhappy users! Bottom line: let's get rid of it and replace it by something sensible (such as proposed in the upcomming standard). > > However, abcm2ps does not support the "\c c" notation > > that appeared in your table. You probably meant "\cc" ? > > oh my, I wrote the LaTeX equivalent... gonna fix it. I still prefer the forms "\,c" and "\/o" which are fully understood by abcm2ps. Anyway, thank you again for putting this reference together. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Revising the ABC standard.
On Thu, 31 Jul 2003, Barry Say wrote: > I write ABC which fully conforms to ABC 1.6.1 and use > features of TeX to customise the output. This is > useful when re-typesetting music which is already > published when a new edition is required, and it is > necessary not to disturb the layout too much. Barry, If the ABC 1.6.1 standard and abc2mtex provide in all your music typesetting needs, that is fine. Nobody on this list will take offense if you'll continue to use this program. The ABC 2.0 standard (and the software that will implement it) are for those who have different needs than you, so you should not be concerned with it. FWIW, the ABC 2.0 standard requires that all E: lines in the source code be simply ignored by complying programs. This means that is no problem to include an E field in ABC 2.0 code --- it just won't have any effect. Irwin Oppenheim To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] MAXSTAFF = 16
On Thu, 31 Jul 2003, Luis Pablo Gasparotto wrote: > Is there some reason to limit the number of staffs to 16 in abc2ps.h? No other than that it costs more memory to deal with more staves, so it's reasonable to set the default not too high. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] Changelog
Latest additions to: http://www.joods.nl/~chazzanut/abc/abc2-draft.html == Editorial accidentals may be surrounded by parentheses. Example: d _e ^f g a _b (^)c' d' == 2.24. Symbol lines Adding many symbols to a line of music can make a tune difficult to read. In such cases, a symbol line (a line that contains only symbols) can be used, analogous to a lyrics line. A symbol line starts with 's:', followed by a line of symbols. Matching of notes and symbols follows the rules defined in section Lyrics. Example: CDEF | G```AB`c s: +pp+ | +f+ ** +fff+ Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Revising the ABC standard.
On Thu, 31 Jul 2003, Laura Conrad wrote: > but where something written with a sincere desire to > adhere to the standard will have to be modified to > adhere to the new standard. The '*' for right > justification seems like an example of this, That is no problem. The standard requires that stars appearing somewhere in the music be ignored. > and midline fields with a continuation character > before them may be another. This issue is specifically noted in the standard. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Revising the ABC standard.
On Thu, 31 Jul 2003, Richard Robinson wrote: > And, I thought Henrik was involved with this original attempt, too ? Henrik is still involved. When he'll be back from vacation, he will devote some time to update the BNF specification according to the standard. Irwin To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] 8.3. Accidental directives
I have changed this section to the form that was suggested by Laura and John. Let me know if the naming could be further improved. Irwin === 8.3. Accidental directives %%propagate-accidentals When set to not, accidentals apply only to the note they're attached to. When set to octave, accidentals also apply to all the notes of the same pitch in the same octave up to the end of the bar. When set to pitch, accidentals also apply to all the notes of the same pitch in all octaves up to the end of the bar. The default value is pitch. %%writeout-accidentals When set to none, modifying or explicit accidentals that appear in the key signature field (K:) are printed in the key signature. When set to added, only the accidentals belonging to the mode indicated in the K: field, are printed in the key signature. Modifying or explicit accidentals are printed in front of the notes to which they apply. When set to all, both the accidentals belonging to the mode and possible modifying or explicit accidentals are printed in front of the notes to which they apply; no key signature will be printed. The default value is none. To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] musicXML
On Thu, 31 Jul 2003, Richard Robinson wrote: > Has anybody seen any of the XMLish schemes do anything useful, yet ? > I haven't had a look round recently, ibut whenever I have it's all looks > kind of "maybe one day"-ish. musicXML is a format that actually works. Finale can import and export it, and barFly can also deal with it. Irwin To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Announcement: "Current state of ABC" online
On Thu, 31 Jul 2003, Guido Gonzato wrote: > > While you at it, please explain to me what is the > > use of the G: field? > ooops - typo. Used by ABC database apps. Do you know which database applications use it and for what purposes? > > Barfly does not support this form: > > w: Sa-ys my au-l' wan to your aul' wan\ > > w: Will~ye come to the Wa-x-ies dar-gle? > > thanks. Too bad for barFly, it breaks 1.7.6. I'll add a note. That is to say, barFly expects this form: << w: Sa-ys my au-l' wan to your aul' wan\ Will~ye come to the Wa-x-ies dar-gle >> > > In fact, the semantics of "\" are now not portable at > > all. That was the main reason to completely redefine > > the continuation mechanism in the upcomming standard. > > that's only your opinion. That the "\" mechanism from the current ABC standard is not portable, is not an opinion but a fact. I tried the following piece of ABC: << X:1 T:Shenei Zeitim M:4/4 K:C G|G2G2A4|(FEF) D (A2G) G| [M:4/4] [K:C] c2c2(B2c2)|(f2e2)e2d G| w:She-nei zei-tim nich-__ra-tim_ \ w:be-gan na-'ul_ yats-_hi-ru. Le- G|G2G2A4|(FEF) D (A2G) G|\ w:She-nei zei-tim nich-__ra-tim_ be-\ M:4/4 % Measure Change\ K:C % Key Change\ c2c2(B2c2)|(f2e2)e2d G| w:gan na-'ul_ yats-_hi-ru. Le- >> in abcm2ps, jcabc2ps, abcMus, abacus, muse, skink, abc2midi and barFly. Some gave warning messages, some gave error messages, but anyway, most applications did not give the expected output. So I can't say it is portable. > when the new standard becomes reality, and when applications support it, > I'll modify the text. Remember: I only cover _existing_ implementations! Abcm2ps supports both "\,c" and "\/o" However, abcm2ps does not support the "\c c" notation that appeared in your table. You probably meant "\cc" ? Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] ABC standard changelog
On Thu, 31 Jul 2003, John Chambers wrote: > | %%propagate-accidentals <0 | 1> > | > Hmmm ... As others have pointed out recently, a very common > rule (except when it's not ;-) would be: > > When set to 2, accidentals also apply to all the notes of > the same pitch in all octaves up to the end of the bar. Will add that too. > (I wonder how many programs will implement all of this? I'd > think there would be a real temptation to put it off until > you need it yourself.) It is only meta information that is not part the ABC standard itself. As such programs may happily ignore all this, though the resulting output won't be optimal/ as intended by the transcriber. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Announcement: "Current state of ABC" online
On Thu, 31 Jul 2003, Guido Gonzato wrote: > I have released the first version of "Current state of ABC", formerly > known as "A proposal for ABC extensions" or what I called it. > This document _is not a standard draft_! It only deals with _implemented_ > features that are not covered in 1.7.6 Guido, thank you for putting this useful reference document together. (http://abcplus.sourceforge.net/abc-current.html) Couple of things that caughed my attention: << Field name header tune elsewhere Examples and notes I:information yesyesG:flute T:titlesecond yes yes M:3/4, M:4/4 >> I didn't find these examples very helpful... While you at it, please explain to me what is the use of the G: field? << \ continuation character; next w: field is part of the same line >> Barfly does not support this form: w: Sa-ys my au-l' wan to your aul' wan\ w: Will~ye come to the Wa-x-ies dar-gle? In fact, the semantics of "\" are now not portable at all. That was the main reason to completely redefine the continuation mechanism in the upcomming standard. << \c C \c c \O \o >> These form won't be allowed in the new standard The preferred forms are: << \,c \,C \/o \/O >> These will work both in current and future ABC implementations. !repeatbar! and !repeatbar2! are not implemented in abcm2ps, as far as I know. I would appreciate a more detailed explanation of the %% directives. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Revising the ABC standard.
On Thu, 31 Jul 2003, Bernard Hill wrote: > >Numbering sections is a very good idea indeed. > Seconded. The sections are now all numbered. http://www.joods.nl/~chazzanut/abc/abc2-draft.html Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] ABC standard changelog
Dear abcusers,
Below I will outline the most recent changes that I
incorporated in the ABC draft standard, based on
your input.
The complete document is available here:
http://www.joods.nl/~chazzanut/abc/abc2-draft.html
As always: constructive criticism is very welcome!
- Changed "Accomp. Chords" to "Chord Symbols"
- Added: programs should treat chord symbols quite liberately
- Changed "Musical Symbols" to "Decorations"
- Changed Roll to Irish Roll
- Moved Lyrics description to an appendix
- added a reference to abctab2ps:
http://www.lautengesellschaft.de/cdmm/userguide/userguide.html
- Hopefully made the "clef section" clearer:
<<
Note that the |clef|, |transpose|, |middle| and |stafflines| specifiers
may be used independent of each other.
Examples:
[K: clef=alto]
[K: perc stafflines=1]
[K:Am transpose=-2]
[V:B middle=D bass]
>>
- Hopefully made the "staves section" clearer:
<<
Voice grouping
Basic syntax:
%%staves ...
The staves directive specifies which voices should be printed in the
score and how they should be grouped on the staves. If no special
characters are used, the voices mentioned go on separate staves. Voices
that appear in the tune body, but not in the staves directive, won't be
printed.
If no staves directive is used, all voices that appear in the tune body
are printed on separate staves.
Voices that are enclosed by parentheses '()', will go on one staff.
Together they form a voice group.
If voice groups or single voices are enclosed by brackets '[]', the
corresponding staves will be connected by a big bracket printed in front
of the staves. Together they form a voice block.
If voice groups or single voices are enclosed by curly braces '{}', the
corresponding staves will be connected by a big curly brace printed in
front of the staves. Together they form a voice block. This format is
used especially for typesetting keyboard music.
If voice blocks, voice groups, or single voices are separated from each
other by a '|' character, no bar lines will be drawn between the
associated staves.
Example:
%%staves Solo [(S A) (T B)] | {RH (LH1 LH2)}
See Canzonetta.abc for an extensive example.
>>
- Introduced the following section:
<<
Accidental directives
%%propagate-accidentals <0 | 1>
When set to 0, accidentals apply only to the note they're attached to.
When set to 1, accidentals also apply to all the notes of the same pitch
in the same octave that appear after the note that they're attached to,
up to the end of the bar.
The default value is 1.
%%writeout-accidentals <0 | 1 | 2>
When set to 0, modifying or explicit accidentals that appear in the key
signature field (K:) are printed in the key signature. When set to 1,
only the accidentals belonging to the mode indicated in the K: field,
are printed in the key signature. Modifying or explicit accidentals are
printed in front of the notes to which they apply. When set to 2, both
the accidentals belonging to the mode and possible modifying or explicit
accidentals are printed in front of the notes to which they apply; no
key signature will be printed.
The default value is 0.
>>
Irwin
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] %%staves
On Wed, 30 Jul 2003, Arent Storm wrote:
> And what if I want one large { with four staves ?
You could use "%%staves [1 2 3 4]" instead,
which will place a [ before the staves, though.
We can of course consider to make the semantics of {..}
similar to [...].
I.e: %%staves {1 2 3 4} will print 4 staves with
a { before, while %%staves {(1 2) (3 4)} gives two
staves with two voices each.
Would that be a good suggestion?
Irwin Oppenheim
[EMAIL PROTECTED]
~~~*
Chazzanut Online:
http://www.joods.nl/~chazzanut/
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] %%staves
On Wed, 30 Jul 2003, Phil Taylor wrote:
> %%staves [(1 2)(3 4)]
Gives a score format: two staves, coupled with a large
"[" on the left side.
> or should that be
> %%staves ([1 2)(3 4])
No. That has no defined meaning.
> >%%staves {1 2 3} a keyboard staff with two voices in the right hand
> > and one voice in the left hand.
>
> Why two on the right and one on the left, rather than the other
> way round?
You can achieve that with:
%%staves {1 (2 3)}
> >%%staves {1 2 3 4} a keyboard staff with two voices in both hands.
>
> Or three on the right/one on the left or vice versa.
Use parentheses to make the sub-grouping explicit, eg
%%staves {(1 2 3) 4} etc.
> No, it's still both redundant and ambiguous as far as I can see.
Now clearer?
Groeten,
Irwin Oppenheim
[EMAIL PROTECTED]
~~~*
Chazzanut Online:
http://www.joods.nl/~chazzanut/
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] %%staves
Dear Phil,
> %%staves {1 2 3 4}
Will typeset 4 voices on one keyboard staff.
A keyboard staff consists of two coupled staves
that are connected with a { symbol in front of them.
> %%staves (1 2)(3 4)
Will print two separate staves, with two voices on each of them.
No { symbol will appear in front of the staves.
===
%%staves {1} a keyboard staff with only one voice in the right hand.
%%staves {1 2} a keyboard staff with one voice in the right hand
and one voice in the left hand.
%%staves {1 2 3} a keyboard staff with two voices in the right hand
and one voice in the left hand.
%%staves {1 2 3 4} a keyboard staff with two voices in both hands.
> It seems to me that the use of {} here is both redundant and
> ambiguous.
I hope it is now clear.
Groeten,
Irwin Oppenheim
[EMAIL PROTECTED]
~~~*
Chazzanut Online:
http://www.joods.nl/~chazzanut/
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Changelog of ABC 2.0
On Wed, 30 Jul 2003, John Chambers wrote: > In most cases, musicians will be following the rule that > accidentals apply in all octaves, so for them it doesn't > matter where the key-sig accidentals are drawn. You seem to forget that ABC players also should be able to make sense of the notation. I suggest the following: 1) [K:D exp _b _e ^f] will accept only lowercase accidentals that apply in all octaves. 2) [K:D oct _B,,, _e'' ^F] will accept octave sensitive key signature definitions. == Only (1) will be adopted in the standard. Programs that have need for octave sensitive key sigs may implement (2) as a private extension. Irwin To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] nobarlines
On Wed, 30 Jul 2003, Laura Conrad wrote: > %%MIDI nobarlines > > indicates that there are no barlines dividing the measures, so an > accidental applies only to the note it's on, and not to all the notes > until the end of the piece. It's really necessary to be able to > specify this. OK. I will add that. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] Arent's 2 cents
On Wed, 30 Jul 2003, Arent Storm wrote:
> * irregular compound meter: two ways of display
> 1) 3+2+2/8 displayed as is
> 2) (3+2+2)/8 displayed as 7/8
I think both should be displayed as:
3 + 2 + 2
8
If you want the semantics of 2), simply type:
M:7/8 % (3+2+2)/8
> *G: group; clarify (I still don't get its definition) or explicit allow any
> useage...
> *H:is (the only?) field that can contimue on the next line without
> repeat of the H: ?
I also don't know the details of these fields.
Can anyone comment?
> *w: to appendix
Good idea.
> * explicitly note which fields may be used in-tune.
There is a table which documents that.
> * ~ I always thought that ~ is used for a prall-trill by default.
> Hardly anybody will know what an Irish-roll is (is it eatable?)
I also do not know what a Irish roll is. But apparently, they are
the people that invented the ~ symbol.
> But as this will reraise previous discussions make a statement
> like 'programs should treat chord symbols quite liberately'
Good idea.
> * clefs:
> Is "K: Am transpose=-2 " illegal where
> "K: Am treble transpose=-2 " is not?
Both are legal. will try to make it clearer.
> state that all voices to be mentioned in the abc-body have to be declared in
> the header when using the [V:ID] syntax, where each ID will be referenced over
> and over.
Do others think this would be necessary?
> Reserve some unicode encoding scheme for future enhancements
> (forward compatibility) So characters like copyright signs, trademark
> or whatever may be used in the (near) future:
There is support for utf-8 encoding of strings
> *reserved characters
> Try to make clear where/why which characters is reserved.
> Even better: reserve characters in a specialized context.
> - global
> - within body
> - within header
> - within textstrings
> - within w: and/or W: lines
> reserved syntax would be a nice thing to have.
> Knowing which generic syntax might be used in the future will render software
> useable for a longer time.
If I'll have some time, I'll look into this suggestion.
> The draft suggests that %%staves is likely to be moved to a stylesheet.
What would be wrong with a piano tunebook starting
with the definition:
%%staves {LH RH}
V:LH bass m=d
tunes
Makes perfect sense to me.
> *special characters:
> why use = for a macron and/or stroke through
> - or _ is more logical
\- has already got a special meaning in lyrics lines!
> The oe ligature is missing (fine to me as there
> is a readable workaround for it).
I asked a couple of Frenchmen and they said they
could live without it.
> z-circumflex is not available in latin-extended-A
> (especially not as it typesetted here ;-)
Correct. It should be removed.
Groeten,
Irwin Oppenheim
[EMAIL PROTECTED]
~~~*
Chazzanut Online:
http://www.joods.nl/~chazzanut/
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] Let's move on
On Wed, 30 Jul 2003, Richard Robinson wrote: > > > K:D _b _e ^f actuall leaves also a c^. The point of the exp is to > > > *override* the normal key sig of D. > > [1] The given example actually produces 1 sharp and 2 flats, ie is > equivalent to "D exp". Nope. As I have explained earlier, "K:D _b _e ^f" is equivalent to "K:D maj _b _e ^f". If you want a key sig with only "_b _e ^f" you *must* specify "K:D exp _b _e ^f" If there are still questions about the key signatures syntax, please send them to me off-list. Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
