Re: [abcusers] Dynamics
The draft standard has some standards for dynamic markings between the !...!, as a modifier on a chord much like the chord symbol (which is enclosed in quotes). It's also possible to 'abuse' the chord notation ("...") to place dynamics below notes, but that doesn't really do it for things like crescendos. (fwiw iabc will eventually honor both these.) abc2midi honors some proprietary midi volume notations in comment lines. See the rendition of Beethoven's 7th on the abc homepage for examples.
RE: [abcusers] Dynamics
Title: RE: [abcusers] Dynamics Quit sending me this crap. -Original Message- From: Starling [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 09, 2002 1:55 PM To: [EMAIL PROTECTED] Subject: [abcusers] Dynamics Sorry, having a bit of trouble with the documentation. Does anybody know how to do dynamics in abc, such as crescendos, decrescendos, markings like forte, mezzoforte, and those nifty alligator clips used to indicate short cresc(and decresc)endos. Starling To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics (was)
Gianni Cunich wrote: I won't let your offensive emails drive me away... Do you actually wish to ask Toby making this a censored list? Not a bad idea actually. Why don't we take a vote on expelling Gianni from the list? Phil Taylor To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics (was)
On Friday 02 November 2001 04:31, Phil Taylor wrote: Gianni Cunich wrote: I won't let your offensive emails drive me away... Do you actually wish to ask Toby making this a censored list? Not a bad idea actually. Why don't we take a vote on expelling Gianni from the list? Phil Taylor Well, at this point Gianni has earned himself the sad distinction of being the only individual whose posts I have filtered, on any list, ever. If/when I see responses from other list members that indicate he's actually contributing something constructive, I'll consider removing my filter. In the meantime I refuse to be distracted by someone who contributes little to nothing positive and consistently derides everyone else's efforts. Wendy To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics (was)
Just for the record: I've just set up an e mail filter to autmotacially remove all messages with the subject Re: [abcusers] dynamics (was). Can smeone tell me when this is over? Frank Nordberg http://www.musicaviva.com To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics (was)
On Fri, 2 Nov 2001, Wendy Galovich wrote: Well, at this point Gianni has earned himself the sad distinction of being the only individual whose posts I have filtered, on any list, ever. Same here. Likewise, a first. If/when I see responses from other list members that indicate he's actually contributing something constructive, I'll consider removing my filter. If anybody's left reading them, to notice it. -- Richard Robinson The whole plan hinged upon the natural curiosity of potatoes - S. Lem To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics (was)
Richard Robinson said - On Wed, 31 Oct 2001 [EMAIL PROTECTED] wrote: .. Richard Robinson and others have argued that the development of the abc standard should be associated with a software project. I have reviewed all my postings to this thread, since Laura's comments and before. I can't find any such statements. Well that's what I've been talking about and you have been arguing against me. What did you think we were talking about? I don't see a conflict, actually. A spec. "should" describe how software behaves, software "should" behave as described, and wouldn't it be nice if the thousand flowers could converge on a single description ? Writing code and writing documentation are not unrelated, but they're not identical skills either; lots of people are better at one than the other, and lots of people _are_ invloved, in whatever way is accessible to them. Even if it be arguing the toss about priorities on the mailing list ... I think that's a fair summary of what I've been saying. My feeling is that things are likely to go better when people are scratching the itches that they actually feel. If somebody proposes that they might write some code, I presume they have thought for themselves about what they could do, and that that is what they think best, and I prefer to accept that rather than getting upset because they're not scratching whatever itch I'm feeling. The problems arise when, having scratched their itch, they don't share that comfort with other people (an innovation doesn't pass into general use) or two people are scratching the same itch without knowing it (two different, and possibly incompatible, solutions appear to the same problem). We are all scratching the same body. I'm sorry. This metaphor is getting slightly disgusting. I think John's comments, yesterday, sum things up pretty well, as regards software and/or specification. John is talking a lot of sense but still seems slightly ambiguous about whether the documentation should be associated with one software development or not. I shall respond to his posting separately. Bryan Creer
Re: [abcusers] dynamics (was)
Wendy Galovich said- A Wiki page? See http://www.usemod.com/cgi-bin/wiki.pl?WhatIsaWiki What I'm thinking here is that if an editable page - say, a table listing abc applications against each detail of the standard specifications, was publicly available, a sizeable group of contributors could work on it, and the task of updating it wouldn't have to fall to one designated person. Looks interesting. It will depend heavily on goodwill between users. I'll investigate it further. Bryan Creer
Re: [abcusers] dynamics (was)
- Original Message - From: Richard Robinson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, October 30, 2001 6:33 PM Subject: Re: [abcusers] dynamics (was) But silly is not the main point. I lost my temper, yes. For the second time since this list was started. I am seeing Brian, and Gianni, making remarks which I consider to be really offensive, about an undefined number of other people on this list. And, to borrow Laurie's phrase, it gets my goat. To quote Alessandro Manzoni, our national novelist, which was in turn quoting an old popular Italian saying: chi è è in difetto è in sospetto! A complimentary translation for non Italian native speakers: who knows to be guilty of something, reacts when when anybody talks about it. If, as a number of other subscribers to this list, you'll find hard to grasp the meaning of my posting(s), this is an idot proof English native speaker broad summary: The one you blamed for being offensive were, actually, replying to messages that where offending them. Blame it on the other members of your gang, not on us! In other words: if you think we are offensive just beacuse we don't change our minds when you, the self appointed Demigods of the abc, stated we should have... well,you can go to Hell (and possibly remain there!). And if you think that we - or to say better, I - should be NICE when someone keeps offending us - well: SEE ABOVE...AND, PLEASE, FOLLOW MY SUGGESTION... Otherwise, you might discover that the word offensive might show a number of hidden meanings you have never even dreamed about in you worst nightmares... yes, I'm TIRED TO BE INSULTED BY *** LIKE YOU... and the next time I will post to this mailing list I will feel entitled to avoid using asterisks! WOWW! Given this: I'm not Bryan (Creer) - I'm not necessarily sharing Bryan's opinions - I actually think he's wasting his time to try to discuss with *** like you! And I actually have taken the decision to replay, stroke for stoke, to the kind of messages you, and the likes, are posting. ABC is not perfect. A number of people have tried, and put work into, a number of approaches to improving things. A number of improvements have been made, even if not the ones that some people hoped for. To abuse people for doing the work they have done seems to me, as I said before, unfair, counterproductive, and just plain wrong, even if it has not handed everybody everything they would like. Particularly, the way that every time a new poster appears here, they are informed that this is a no-good bunch of people, an arrogant self-selected clique who are bound not to listen to them ... it does no good. It makes agreement harder to reach instead of easier, it drives people away instead of including them, and I object to it. And I intend to continue doing so, from time to time ... I don't think it's true, either ;) Actuall, YOU ARE in fact an arrogant self-selected clique who are bound not to listen to them. And so what? I won't let your offensive emails drive me away... Do you actually wish to ask Toby making this a censored list? No regards Gianni To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics (was)
Laurie Griffiths said - There was a move - and I was part of it - to try to make some sort of progress on the standard. Part of the thinking was that the fewer people involved the quicker we might agree. Part of the thinking was that if we enhanced the standard, even if we didn't do it the way some people would have liked, it would still be progress and still good for everyone because something is almost always better than nothing. and Richard Robinson said- ABC is not perfect. A number of people have tried, and put work into, a number of approaches to improving things. A number of improvements have been made, even if not the ones that some people hoped for. whereas Laura Conrad recently said - The discussion convinced everybody after a couple of months that there was no point in putting work into a standard in the present development environment. Which I think means it was a productive discussion, which produced the right answer. to which Phil Taylor responded - I have to dissent somewhat here. I personally was not convinced that the task was pointless, and was quite prepared to continue. As far as I remember, the discussion petered out without any decisions being taken, and I rather thought that it would be taken up again. There seems to be some confusion here. Has the standards committee decided anything or not? Could we have a clear statement from the committee (rather than individual members) on what it has achieved and its current status? Bryan Creer
Re: [abcusers] dynamics (was)
On Wed 31 Oct 2001 at 05:17AM -0500, [EMAIL PROTECTED] wrote: There seems to be some confusion here. Has the standards committee decided anything or not? Could we have a clear statement from the committee (rather than individual members) on what it has achieved and its current status? I don't think you'll ever get the standards committee to speak as one person with a unified voice. My opinion is similar to Phil's. I took the approach of identifying all the new features in the new draft standard and seeing which ones were universally approved and which ones were not. This seemed like a good way to make progress, and I got the impression that disagreement was restricted to relatively minor features and obscure options of major features. However, the thread petered out without any definite conclusions; people were either not interested in this approach or distracted by other projects. It is still possible for someone who cares about an abc standard to help the process along; get hold of every abc program you can, go through them carefully and then document the compatibilities and incompatibilities carefully on the web. If you do this carefully and comprehensively enough it be a valuable resource to guide any new abc developer on interpreting the more subtle aspects of abc. James Allwright To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics (was)
On Wed, 31 Oct 2001 [EMAIL PROTECTED] wrote: In a posting a few days ago, Laura Conrad spoke first of the difficulties of achieving agreement on a standard and then spoke of the sort of the sort of open-source project that she would like to see. I took these as one topic reflecting more of the same association of standard and software project and used my now notorious outlaw reference. She then said that she was simply making two separate points in the same email and I (if you recall) apologised. I may have been a little premature in doing so as, since then, Richard Robinson and others have argued that the development of the abc standard should be associated with a software project. I have reviewed all my postings to this thread, since Laura's comments and before. I can't find any such statements. I don't see a conflict, actually. A spec. should describe how software behaves, software should behave as described, and wouldn't it be nice if the thousand flowers could converge on a single description ? Writing code and writing documentation are not unrelated, but they're not identical skills either; lots of people are better at one than the other, and lots of people _are_ invloved, in whatever way is accessible to them. Even if it be arguing the toss about priorities on the mailing list ... My feeling is that things are likely to go better when people are scratching the itches that they actually feel. If somebody proposes that they might write some code, I presume they have thought for themselves about what they could do, and that that is what they think best, and I prefer to accept that rather than getting upset because they're not scratching whatever itch I'm feeling. I think John's comments, yesterday, sum things up pretty well, as regards software and/or specification. -- Richard Robinson The whole plan hinged upon the natural curiosity of potatoes - S. Lem To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics (was)
I had hoped that we could make progress on some of the things which are already implemented here and there (and in fact the implementations are not totally incompatible). From memory (if any of these are in actually the standard then forgive me) w: to specify words v: to specify voices Some way to specify clefs (implementations use k: and v:) There are of course plenty of other things to do and to argue about. This is not the Voice Of The Committee, just me. Laurie - Original Message - From: James Allwright [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, October 31, 2001 11:32 AM Subject: Re: [abcusers] dynamics (was) On Wed 31 Oct 2001 at 05:17AM -0500, [EMAIL PROTECTED] wrote: There seems to be some confusion here. Has the standards committee decided anything or not? Could we have a clear statement from the committee (rather than individual members) on what it has achieved and its current status? I don't think you'll ever get the standards committee to speak as one person with a unified voice. My opinion is similar to Phil's. I took the approach of identifying all the new features in the new draft standard and seeing which ones were universally approved and which ones were not. This seemed like a good way to make progress, and I got the impression that disagreement was restricted to relatively minor features and obscure options of major features. However, the thread petered out without any definite conclusions; people were either not interested in this approach or distracted by other projects. It is still possible for someone who cares about an abc standard to help the process along; get hold of every abc program you can, go through them carefully and then document the compatibilities and incompatibilities carefully on the web. If you do this carefully and comprehensively enough it be a valuable resource to guide any new abc developer on interpreting the more subtle aspects of abc. James Allwright 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] dynamics (was)
On Sat, 27 Oct 2001 [EMAIL PROTECTED] wrote: There doesn't seem to be much point in being involved in an open-source project coded in a language you don't understand. Sorry, but that's absurd. Coding is not the only way to contribute to a software project, and I would argue that it is not even the most important way. Probably 75% of the people on my team at work have never even seen our product's source code. And there are plenty of SourceForge members who can't program in *any* language. I think an open-source project *could* be an appropriate venue for working on the abc standard, as long as it's open to input from anyone. I don't understand why you think a project contributor would have to know C or any other programming language in order to provide input on the standard. Coding would follow the standard, not the other way around. I'm not saying this is what libabc should be, or even could be, but I don't understand why you are singling it out for criticism over any other implementation. It seems like a huge leap to say that there is a danger of it becoming synonymous with the future of abc, let alone in some way that would exclude your input. All that aside, based on the present standardization efforts (or lack thereof), abc *has* no forseeable future. I don't think that should stop someone from writing a useful tool. And since it hasn't stopped *you*, I assume you would agree. To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics (was)
- Original Message - From: Eric Mrozek [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, October 28, 2001 3:41 AM Subject: Re: [abcusers] dynamics (was) [EMAIL PROTECTED] wrote: [ time for a new approach, preferably one involving as much of the abc community as possible not just a self chosen clique ] Do you have a positive suggestion ? Certainly, but before I do, could I have your assurance that you will give my suggestions proper consideration, rather than opposing them on principle just because they come from me, and that you will restrict your reponses to what I actually say rather than your own wild speculations about things you think I might say (as you have done twice in this thread alone)? Bryan Creer Bryan, this is an open list - you won't get anyone to agree to your personal terms. You'd be best off to just post your thoughts and don't mind the critique, whether it's meant personally or not. Eric Actually (even if my English might be a bit rusty), as far as I've been able to understand the meaning of what Bryan wrote, he wasn't asking for somebody to agree about any kind of personal terms. He was rather, I guess, talking about prejudices, which are a rather different thing than what you call critique. Even if you aren't able to grasp the difference, it's quite a concrete one! Gianni To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics (was)
Hello, reading all this dynamic messages, I want to ask for a bit of moderation, since things do not get better by breaking down bridges which have to be rebuilt afterwards anyway. Abc as it is is working right now and whether there is a further developement for the standard and/or the programs, abc is of some use for many people. It is true that everybody including me has whishes about extentions to the existing possibilities, but in effect nothing is as important than improoving the actuall programs or new programms to fit to the actuall standard, at least not to loose backwards and cross program file compatibility. regards Simon Wascher To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics (was)
Eric Mrozek said - Bryan, this is an open list - you won't get anyone to agree to your personal terms. You'd be best off to just post your thoughts and don't mind the critique, whether it's meant personally or not. Well, some of the critique has been extremely personal. Of course I'm going to post my ideas as to what should be done; give me a few days to collect my thoughts. I was just having a dig at Richard Robinson who, twice in this thread, had said things along the lines of "I expect you would say..." followed by an absurd statement bearing no resemblance to anything I ever have said or ever would say. He is an intelligent chap who knows what he is doing and is simply trying to score debating points. I can't be bothered to waste my time on that sort of thing. During my time on this list I have seen several people arrive bright eyed and bushy tailed, full of enthusiasm and ideas only to retreat in exasperation a few weeks later after a tirade of "Well, what about..." and "That won't work..." and "We like it the way it is." and "Well, I don't need it so I won't implement it in my software." from the establishment who seem to think they own abc. If that sort of thing doesn't work, they are quite prepared to resort to personal abuse or use such refined techniques as ignoring the content of a posting while picking up on the spelling mistakes (I have deliberately left a few in this email for those who like that sort of thing). They have the ultimate response for irrefutable arguments or awkward questions. They ignore them. I have never known anyone say to anyone "OK. You have convinced me. You are right." From comments made by Laura Conrad, it would appear that this attitude continues in the inner sanctum of the standards committee which explains why it has failed to achieve anything. So here is my first proposal - Members of this list will commit themselves to treating other people's ideas with respect and answering them in a rational way no matter how much they disagree with them. Let's try and raise the level of debate out of the school playground. You never know; it might just work. Bryan Creer
Re: [abcusers] dynamics (again)
Jack Campin said - Programs like abc2win only let you output ABC they can interpret. abc2win has come under considerable critiscism on this list for its deviations from the standard. After not inconsiderable effort on my part, abc2nwc now accepts abc2win tunes without much trouble. This was essential given the large quantity of abc2nwc tunes there seem to be out there. I have not managed the same with abc tunes produced using BarFly (avoiding calling it 'output') because some of its extensions are incompatible with other implementations; notably the V: command. Surely the ideal to work towards is that the input/output from all software should be mutually comprehensible. if I need a feature in ABC to represent a piece of music in front of me I'll invent it and let the programmers catch up when they can. Why should they if it isn't in the standard? How can they be sure of getting it right without a formal definition? What do they do if someone else has come up with a different solution to the same situation? What do they do if your syntax conflicts with somebody else's solution to a completely different problem? By cooperating at the definition/specification level, all that would be avoided and you would get what you want. It's fine for an application to report that it can't figure such stuff out, or to say that it doesn't meet some agreed standard, but that doesn't mean it shouldn't be there. But some of the information you wished to convey is lost to the recipient. Hardly satisfactory. Bryan Creer
Re: [abcusers] dynamics (was)
[EMAIL PROTECTED] wrote: [ time for a new approach, preferably one involving as much of the abc community as possible not just a self chosen clique ] Do you have a positive suggestion ? Certainly, but before I do, could I have your assurance that you will give my suggestions proper consideration, rather than opposing them on principle just because they come from me, and that you will restrict your reponses to what I actually say rather than your own wild speculations about things you think I might say (as you have done twice in this thread alone)? Bryan Creer Bryan, this is an open list - you won't get anyone to agree to your personal terms. You'd be best off to just post your thoughts and don't mind the critique, whether it's meant personally or not. Eric P.S. In the spirit of developing cross-platform tools... I currently typeset music using abc2ps and abcm2ps, but usually convert the postscript to PDF when sharing the files with others. Because the Unisys compression patent expires soon, I have considered building a library of PDF writing functions similar to the ones in abc2ps so that I could generate PDF files directly. Would any of the developers here be interested is using such a thing? One issue that causes me to hesitate is that compressed PDF output would not be as compact as the postscript (ps allows macros which is a huge advantage when you have lots of shapes - i.e. note heads - repeated many times on a page). Another is that GhostView makes postscript viewing/printing easy enough that PDF doesn't seem necessary. To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics (was)
Eric == Eric Mrozek [EMAIL PROTECTED] writes: Eric P.S. In the spirit of developing cross-platform tools... I currently Eric typeset music using abc2ps and abcm2ps, but usually convert the Eric postscript to PDF when sharing the files with others. Because the Eric Unisys compression patent expires soon, I have considered building a Eric library of PDF writing functions similar to the ones in abc2ps so that Eric I could generate PDF files directly. Would any of the developers here Eric be interested is using such a thing? One issue that causes me to Eric hesitate is that compressed PDF output would not be as compact as the Eric postscript (ps allows macros which is a huge advantage when you have Eric lots of shapes - i.e. note heads - repeated many times on a Eric page). Another is that GhostView makes postscript viewing/printing Eric easy enough that PDF doesn't seem necessary. And when it is, ps2pdf does a pretty good job, so I'm not sure the effort of maintaining an abc2pdf utility makes sense. -- Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ ) (617) 661-8097 fax: (801) 365-6574 233 Broadway, Cambridge, MA 02139 To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics
On Fri, 26 Oct 2001 [EMAIL PROTECTED] wrote: Richard Robinson said - Consider the possibility that a separately-maintained ABC library, open-source bug-fixed by anybody that cares to take part, linked into your front-end code, might make your life easier too ? I'm sorry, as a non-VB programmer I don't know how VB links to a C library, but I imagine it must be possible by now. I expect that would be possible but would only give me a passive involvement without the opportunity to take part in bug fixing or adding my own innovations. Adding innovations would involve discussion, certainly. Is that a bad thing ? I thought you were in favour of having standards and against people innovating off their own bat ? I'd have thought an open-source function library would facilitate this rather than hinder it. As for bug-fixing - if you're using functions out of a library in your own code, you will be the first to discover any bugs. They'll bite you, in your development, before they bite any users of the finally-developed result. You have the source so you can see exactly what's going on, know just how that code is interacting with your own, be able to discuss the situation with the library maintainers and find the best solution. And so will anybody else making use of that library, so they'll get the benefit of having bugs fixed that you've spotted, and vice versa. What could be _less_ passive or opportunity-denying than that ? That's more like it! Open documentation would be of much more general use than open source. Open documentation _is_ useful, yes. Very. That's how ABC has got to where it is; people are free to read how it's supposed to work, so they can go off and write code to make it happen like that. Code's useful too. In theory, someone could just read the documentation, and then write their abc in pencil on the back of an envelope, but in practice most of us do use some software from time to time. Laura Conrad said - Several other people are non-voting members by virtue of being on the mailing list by invitation of the members. I would be willing to resign in favor of someone with more enthusiasm for the project than I have at the moment. What on earth gives you the right to turn abc into an exclusive club? We could all do with a standard. This is an attempt to reach one. Laura's trying to help that. It seems unfair and wrong and counterproductive to put people down for trying to do things for us. -- Richard Robinson The whole plan hinged upon the natural curiosity of potatoes - S. Lem To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics
I'm probably going to have to provide an abcfix program that attempts to standardize non-compliant abc files. I'd like to see how that handles BarFly output. BarFly doesn't *have* output; it's a text editor, it doesn't enforce any ABC dialect any more than Emacs does. I've used it to write ABC that no version of the program itself could play or print. While I'd like to see a bit more interoperability, I'd be more interested in functionality - there are still lots of musical features that could be fitted into ABC without drastic upheaval but which no ABC implementation yet does right. There is no way ABC is going to take off in any genres beyond those it's got to already unless some extensions are made available; why should users with divergent specialist needs (rehearsal marks, editorial annotations, microtonality, lead sheets, text in two-byte character sets...) have to wait until *every* application implements them? One problem with using a common library: turnaround time for bugfixes. Some of the most-used ABC applications out there get updated no more than yearly, others get fixed within days of having a bug reported. If a bug is discovered in a library, this adds a new source of delay; the library maintainer will need to work fast to keep up with the quickest application developers. For some specialized library functions the open-source model might not help all that much as there might only be one developer in the group who understands what the code is supposed to do. On the other hand, a common specification (a real one, rather than the handwaving in the current documents or purely syntactic stuff like Henrik's BNF) would benefit everybody without introducing new problems like this. What formalisms would all the developers find readable? === http://www.purr.demon.co.uk/jack/ === To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics (again)
Jack Campin said - BarFly doesn't *have* output; it's a text editor, it doesn't enforce any ABC dialect any more than Emacs does. Don't text editors have output? I am not a Mac user so I have no direct experience of the nature of BarFly, but I do know that a number of people have posted tunes in abc generated by using BarFly. From where I'm standing these are BarFly output. They appear to have various characteristics which make them incompatible with the abc software available to me. Do these not arise from the use of BarFly, or is it just that all BarFly users are working to a different definition of the abc standard? On the other hand, a common specification (a real one, rather than the handwaving in the current documents or purely syntactic stuff like Henrik's BNF) would benefit everybody without introducing new problems like this. What formalisms would all the developers find readable? Excellent! Keep pushing at that idea. Bryan Creer
Re: [abcusers] dynamics (again)
[EMAIL PROTECTED] wrote: I am not a Mac user so I have no direct experience of the nature of BarFly, but I do know that a number of people have posted tunes in abc generated by using BarFly. From where I'm standing these are BarFly output. They appear to have various characteristics which make them incompatible with the abc software available to me. Do these not arise from the use of BarFly, or is it just that all BarFly users are working to a different definition of the abc standard? BarFly follows the standard (ABC 1.6) pretty well, but all abc applications differs when it comes to various extensions. abc2ps seems to be the dominating application here in the abcusers community (though not necessarily among abc-users in general!) so people tend to regard that program's use of extensions as the standard. Frank Nordberg http://www.musicaviva.com To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics (again)
BarFly doesn't *have* output; it's a text editor, it doesn't enforce any ABC dialect any more than Emacs does. Don't text editors have output? I am not a Mac user so I have no direct experience of the nature o BarFly, but I do know that a number of people have posted tunes in abc generated by using BarFly. From where I'm standing these are BarFly output. They appear to have various characteristics which make them incompatible with the abc software available to me. Do these not arise from the use of BarFly, or is it just that all BarFly users are working to a different definition of the abc standard? Programs like abc2win only let you output ABC they can interpret. BarFly lets you write any text you want and never modifies it without you asking it to. There's a built-in incentive to write stuff that BarFly can print or play, but no more than that. Quite a bit of the stuff in the modes tutorial on my website gives horrible staff-notation output when BarFly typesets it; I regarded source legibility as more important. You could use it as a C++ programming editor if you wanted to. I've occasionally written email messages with it before copying them to my mail client. I have stacks of poems and bibliographic references originally copied with it. When I'm using a laptop with very limited memory it helps if I can work with only one text-editing application running and have it do the whole job. I don't expect it to make musical sense of a letter describing an 18th century riot. I don't confine myself to the subset of ABC it implements; if I need a feature in ABC to represent a piece of music in front of me I'll invent it and let the programmers catch up when they can. This is part of ABC's inheritance from similar paper notations - the user is in control - and it's something that shouldn't be lost. Given the basic idea of ABC - that it's tunes notated in text files which may contain other material - no more restrictive attitude makes sense. If the other material in a tune file can be any text, that text can be an arbitrarily close approximation to valid ABC. It's fine for an application to report that it can't figure such stuff out, or to say that it doesn't meet some agreed standard, but that doesn't mean it shouldn't be there. === http://www.purr.demon.co.uk/jack/ === To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics (again)
Funny how a thread subject can drift so far from the original and yet still remain appropriate. Frank Nordberg said - BarFly follows the standard (ABC 1.6) pretty well, but all abc applications differs when it comes to various extensions. Yes, I think it does. (If it's only a text editor why does it need to conform to an abc standard?). However, it is the extensions, which hold the future of abc, that are important. If each implemetation follows its own path then abc will fragment and be the poorer for it. You have been known to post separate versions of tunes for BarFly and the rest. abc2ps seems to be the dominating application here in the abcusers community (though not necessarily among abc-users in general!) so people tend to regard that program's use of extensions as the "standard". That is precisely what I am trying to argue against. This is the abcusers' list, not the abc2ps users' list. One software implementation should not be allowed to dominate the standard. Phil Taylor (BarFly), Laurie Griffiths (Muse) and my humble self (abc2nwc) are active participants in this list and one person (who used to be high profile but doesn't seem to have been heard of for a while) even argued that compatibility with abc2win was the main criterion for new extensions. Jim Vint (abc2win) doesn't participate in the debate but given the bad press he gets here, who can blame him. Bryan Creer
Re: [abcusers] dynamics
On Tue, 23 Oct 2001, Taral wrote: This is exactly my intent with libabc. If all goes well, I'll probably go and put it on sourceforge somewhere. two sites are already set up for you: 1) http://abc.sourceforge.net - standard ABC 1) http://abcplus.sourceforge.net - ABC with extensions for classical music Please consider contributing to both projects... please! Later, Guido =8-) -- Guido Gonzato, Ph.D. gonzato at sci . univr . it - Linux system manager Universita' di Verona (Italy), Dipartimento Scientifico e Tecnologico Ca' Vignal II, Strada Le Grazie 15, 37134 Verona (Italy) Tel. +39 045 8027990; Fax +39 045 8027958 --- Timeas hominem unius libri To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics
Laura Conrad said - What we need is a developer who is going to: Use open source, so that anyone can fix bugs. Roll contributions from other people into the source. Implement the standard as written. Clearly label any extensions to the standard used by the program. Write code that can be worked on by multiple people. The fact that abc2ps isn't written this way is probably one of the major reasons for the situation described above. Excellent except for the first and the last. Do you intend to outlaw independant implementations such as BarFly, abc2win, Muse or my own humble abc2nwc? I don't see abc as being defined by any software implementation but to be a standard (or, perhaps, a protocol would be better) for the exchange of musical information regardless of the use to which that information is put. Bryan Creer
Re: [abcusers] dynamics
Taral said - I'd also like to announce that I will be making the following amendments to the standard in libabc: I'm not sure about unilateral declarations of changes to the standard but nobody from the standards committee seems to have complained. The trouble is, you have no way of enforcing your standard on anybody. If they don't like it, they'll ignore it. I'm probably going to have to provide an "abcfix" program that attempts to "standardize" non-compliant abc files. I'd like to see how that handles BarFly output. I'm going to implement 100% of the draft standard, so I think that should cover a lot of bases. I'll also cover a good number of the abcm2ps extensions because I use them. Do you intend to exclude all versions of V: which has no single standard? You will come up against a lot of opposition there. Good luck. The abc developers community consists of a lot of people who are more committed to their own software than the broader concept of abc and are generally hostile to the concept of a standard. This is why the standards committee set up earlier this year has failed to produce any results and appears to have completely foundered. Bryan Creer
Re: [abcusers] dynamics
[EMAIL PROTECTED] wrote: Laura Conrad said - What we need is a developer who is going to: Use open source, so that anyone can fix bugs. Roll contributions from other people into the source. Implement the standard as written. Clearly label any extensions to the standard used by the program. Write code that can be worked on by multiple people. The fact that abc2ps isn't written this way is probably one of the major reasons for the situation described above. Excellent except for the first and the last. Do you intend to outlaw independant implementations such as BarFly, abc2win, Muse or my own humble abc2nwc? I don't see how an open source abclib can have any influence on, let alone be a threat for these projects. What exactly do you mean? I don't see abc as being defined by any software implementation but to be a standard (or, perhaps, a protocol would be better) for the exchange of musical information regardless of the use to which that information is put. I heartily agree. -- bert van vreckem If Bill Gates had a nickel for every time Windows crashed... Oh wait! He does! To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics
Bert Van Vreckem said - I don't see how an open source abclib can have any influence on, let alone be a threat for these projects. What exactly do you mean? I don't see abc as being defined by any software implementation but to be a standard (or, perhaps, a protocol would be better) for the exchange of musical information regardless of the use to which that information is put. I heartily agree. and Laura Conrad said - I'm not proposing outlawing anything. I write personal computer programs myself, and they're very useful to me. I was just saying what I would need to see to get excited about a new implementation. I am sorry if I have misunderstood Laura's meaning here. The first part of her posting discussed the problems of reaching agreement between different developers on the standards committee. I thought she was offering this approach as the solution to that problem. I am concerned that there is a danger of thinking that the sourceforge project IS abc. When it was launched, I seem to recall that one of its initial tasks was identified as formalising and developing the abc standard. I do not think that any one development path should usurp that task; it is the property of all - developers and users alike. Richard Robinson said - You're going to start explaining to us why open-source is wrong, now ? Why on earth should I do that? I am merely pointing out that open-source is one of several approaches to development all of which are perfectly legitimate. Please restrict your criticisms to what I've actually said rather than speculating on what I might say and condemning me for that. Do you intend to outlaw bugfixing ? No, but I don't intend to devote much time to bug fixing abc2ps or its clones any more than I'd expect James Allwrightto bugfix BarFly or Phil Taylor to bugfix abc2nwc (bug reports always welcome of course). Or collaboration ? As the sorry tale of the standards committee shows, collaboration on abc is sadly lacking and I would like to see a great deal more. I just don't want to see collaboration on one particular software implemetation being seen as collaboration on abc to the exclusion of other developments. Brian, what's being talked about here is a library. You know ? A set of useful functions that can be included in other peoples' programs, right ? The only possible use for a library is to _help_ people to write their own programs. Given a suitable "open-source" license, of course ... Rather than talking down to me, perhaps you would like to offer me some advice on how as a Windows/Visual Basic programmer I can participate in this process. Bryan Creer
Re: [abcusers] dynamics
taral == taral [EMAIL PROTECTED] writes: Good luck. The abc developers community consists of a lot of people who are more committed to their own software than the broader concept of abc and are generally hostile to the concept of a standard. This is why the standards committee set up earlier this year has failed to produce any results and appears to have completely foundered. taral Who is on this committee? Here is a list of the official members: James Allwright [EMAIL PROTECTED] Robert Bley-Vroman [EMAIL PROTECTED] John Chambers [EMAIL PROTECTED] Laura Conrad [EMAIL PROTECTED] Laurie Griffiths [EMAIL PROTECTED] Phil Taylor [EMAIL PROTECTED] Several other people are non-voting members by virtue of being on the mailing list by invitation of the members. I would be willing to resign in favor of someone with more enthusiasm for the project than I have at the moment. -- Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ ) (617) 661-8097 fax: (801) 365-6574 233 Broadway, Cambridge, MA 02139 To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics
On Wed, 24 Oct 2001 [EMAIL PROTECTED] wrote: Brian, what's being talked about here is a library. You know ? A set of useful functions that can be included in other peoples' programs, right ? The only possible use for a library is to _help_ people to write their own programs. Given a suitable open-source license, of course ... Rather than talking down to me, perhaps you would like to offer me some advice on how as a Windows/Visual Basic programmer I can participate in this process. Consider the possibility that a separately-maintained ABC library, open-source bug-fixed by anybody that cares to take part, linked into your front-end code, might make your life easier too ? I'm sorry, as a non-VB programmer I don't know how VB links to a C library, but I imagine it must be possible by now. -- Richard Robinson The whole plan hinged upon the natural curiosity of potatoes - S. Lem To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
RE: [abcusers] dynamics
Have you looked at Denemo (http://denemo.sourceforge.net)? The Web page hasn't been updated in a while but the development is very active, and there's ABC export (not import) in 0.5.6. It is not a text editor; rather, it is a graphical editor that can import/export multiple formats, rather like Note Edit, it seems. I'll probably be adding ABC import at some point, but I haven't bothered yet. (Usually my composition/transcription process is: write the main body of the piece in Denemo, export to ABC, tweak as appropriate.) - Eric -Original Message- From: Aaron Newman [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 23, 2001 4:09 PM To: '[EMAIL PROTECTED]' Subject: RE: [abcusers] dynamics Thanks, I re-read the abc2midi and I found the dynamics with the other markings. My application will be an interactive GUI text editor that also displays the notes graphically. So it will use ABC as input instead of Midi or the point/click method like most programs do. Thanks for pointing me to Note Editor. I don't think I can use it, but I may use TSE3 for the MIDI input/output. I don't think a parsing library would be helpful to me; I don't think parsing the ABC language is the difficult part. This app is not based on any of the x2ps ones, but I did convert some of the PS drawing routines for clefs, note heads and such. The first version will probably be available in the spring and will run under Windows. But I am using WxWindows so a Linux port will be easy enough. The emphasis will be on extensibility and portability at first, and on features (like different input/output formats) later on. -Original Message- From: Guido Gonzato [mailto:[EMAIL PROTECTED]] Sent: Monday, October 22, 2001 2:58 AM To: '[EMAIL PROTECTED]' Subject: Re: [abcusers] dynamics On Sat, 20 Oct 2001, Aaron Newman wrote: I read in the FAQ that there is no way now to do dynamics in the official ABC language. How are people handling this? the FAQ should be updated. In actual fact, many ABC applications support dynamics; abcm2ps, jaabc2ps, abc2midi, to name but a few. Please check out the ABC draft, http://www.gre.ac.uk/~c.walshaw/abc/abc-draft.txt I am working on a (yet another) free ABC music editing and display program, and for some reason I overlooked this originally. that's very good! What kind of application are you writing? I hope it's not yet another abc2ps clone... in that case, it would probably be a better idea contributing code to existing programs like abcm2ps or jaabc2ps. Also: have you checked out Note Editor, http://tan.informatik.tu-chemnitz.de/~jan/noteedit/noteedit.html ? It's an astounding graphical music editor, but it lacks ABC export. If you're a talented programmer, you might consider helping that project. Also, I would also like the language to be able to handle jazz, so I would be adding some additional note ornaments ('doits', falls), how is this recommended? I can't help you here. It looks like most ABC programmers add their own extensions to ABC to make it suitable for classical music or else, so adding decos for jazz would be just fine. (IMHO.) It breaks the standard, though. Ciao, Guido =8-) -- Guido Gonzato, Ph.D. gonzato at sci . univr . it - Linux system manager Universita' di Verona (Italy), Dipartimento Scientifico e Tecnologico Ca' Vignal II, Strada Le Grazie 15, 37134 Verona (Italy) Tel. +39 045 8027990; Fax +39 045 8027958 --- Timeas hominem unius libri 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 To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
RE: [abcusers] dynamics
taral == taral [EMAIL PROTECTED] writes: Write code that can be worked on by multiple people. The fact that abc2ps isn't written this way is probably one of the major reasons for the situation described above. I think this is true of a lot of free software. From: Wendy Galovich ... Would such a non-platform-specific documentation method be of any value in helping developers using a variety of platforms and development tools to sort through the details? It would! How about a framework with UML documentation, class heirarchies, sequence diagrams and a design that lends itself to parallel development. There aren't many net projects like this but I think its do-able. Also, I'd think that creating a standard would be less frustrating if there was a working prototype that implemented the standard and also did lots of useful stuff. -Original Message- ... To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics
Hello, if possible please not the and characters, I use them for indicating the positions of the handle of the hurdy gurdy. I would recomend some other not singable standard keyboard character anyway: @ or# or $ . The Idea to tie it to the L: could have its merits, especially if one could use an L: field directly bevore the w: field like: X:1 L:1/4 M:3/4 K:C abc/a/ | bca | L:1/2 w:left# right# left# Just a sugestion. Simon Wascher - Vienna, Austria Taral wrote: How about a w: character that means move to next beat? e.g. w: left approach right together We already have a move to next measure. (I'm not recommending using the symbol, I just couldn't think of anything else at the moment.) We could even tie it to L: so that the beat specification can be separate from the meter specification. To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics
On Mon 22 Oct 2001 at 06:05PM -0500, Taral wrote: On Mon, Oct 22, 2001 at 06:14:17PM -0400, Laura Conrad wrote: I think what's being proposed is that: a-a is two tied notes a--a is two notes tied with a dashed tie a-.a is two notes died with a dotted tie a-.a currently means an ordinary a tied to a staccato a. You need to find a different notation to make this unambiguous. (ab) is two slurred notes .(ab.) (or maybe some other syntax) is two notes with a dotted slur. -(ab-) is two notes slurred with a dashed slur. This looks like the a and the b are tied to other notes. I think you need to change the notation to make this unambiguous. James Allwright To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics
Laura Conrad wrote: ... I think what's being proposed is that: ... a-.a is two notes died with a dotted tie We can't use that one. That particular syntax is already used in abc for something else. Taral wrote: ... Try putting the . before the notes: (.a.b.c.d) This one too. Generally anything that puts a dot before a note is already accounted for in the abc syntax. Frank Nordberg To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics
On Mon, 22 Oct 2001, Taral wrote: On Tue, Oct 23, 2001 at 01:30:30AM +0100, Richard Robinson wrote: Which, doesn't your abc2ps produce dotted notes ? Odd thing, though. My (a.b.c.d.) above ought, surely, to produce staccato notes with a slur over them ? In fact, the first note doesn't appear to have the dot. And (AB.)(c.d.) only produces a dot over the d. I suppose it's my own fault for going out the pub earlier. Try putting the . before the notes: (.a.b.c.d) Duh. Okay, so it was. -- Richard Robinson The whole plan hinged upon the natural curiosity of potatoes - S. Lem To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics
taral == taral [EMAIL PROTECTED] writes: taral On Mon, Oct 22, 2001 at 06:14:17PM -0400, Laura Conrad wrote: I agree, but what I want to hear is not so much about new features but a willingness to consider non-standard behavior as a bug (except for documented extensions), and a willingness to fix bugs even if they only affect other people's music. taral Explain? Some not-so-ancient history: We had (have?) a standards committee, composed primarily of developers of widely-used ABC applications. When discussing the addition of relatively minor new features, some of them said I wouldn't ever use that. Some of them said, That's OK, you don't have it implement it just because it's in the standard. One of them, when faced with a situation where his code clearly behaved differently from the specification of the current standard, provided a %% statement (not even a command line option) which would cause the behavior to be correct, so as not to break the ABC of people relying on the previous incorrect behavior. Also, there are several bugs in abc2ps which I've been reporting for several years now. I have yet to see a report of any of them being fixed in any relative of abc2ps. So I refuse to get excited about an ABC application just because it implements new, potentially useful features. What we need is a developer who is going to: Use open source, so that anyone can fix bugs. Roll contributions from other people into the source. Implement the standard as written. Clearly label any extensions to the standard used by the program. Write code that can be worked on by multiple people. The fact that abc2ps isn't written this way is probably one of the major reasons for the situation described above. taral libabc is going to be quite strict, especially about taral headers. I'm probably going to have to provide an abcfix taral program that attempts to standardize non-compliant abc taral files. Is this what you mean? It's a start. In my opinion, there should also be a --strict option which disabled any extensions. -- Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ ) (617) 661-8097 fax: (801) 365-6574 233 Broadway, Cambridge, MA 02139 To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics
On Tue, Oct 23, 2001 at 08:30:17AM -0400, Laura Conrad wrote: So I refuse to get excited about an ABC application just because it implements new, potentially useful features. What we need is a developer who is going to: Use open source, so that anyone can fix bugs. Roll contributions from other people into the source. Implement the standard as written. Clearly label any extensions to the standard used by the program. Write code that can be worked on by multiple people. The fact that abc2ps isn't written this way is probably one of the major reasons for the situation described above. This is exactly my intent with libabc. If all goes well, I'll probably go and put it on sourceforge somewhere. -- Taral [EMAIL PROTECTED] This message is digitally signed. Please PGP encrypt mail to me. Any technology, no matter how primitive, is magic to those who don't understand it. -- Florence Ambrose PGP signature
Re: [abcusers] dynamics
Richard Robinson writes: Taral writes: and operators: The operator will be used for splits into 2 voices in a single measure, thus: |F2A2BcF2c2bc| Is this the same syntax that abc2mtex used to use ? And, is there much abc out there that uses it ? I used to have a few, I _think_ I've migrated them all to use the newer and easier V: - being 2-part all the way. This coud well make it easier to drop an extra voice in for just a few measures, but backwards-compatability issues can be a pain ... I'm also curious as to whether this was ever used enough to raise any worries about backward compatibility. Abc2mtex does use this syntax to write multi-staff music. I think it was just an experiment, and as far as I know it was never part of the standard, and was never adopted by another program. I tried it once or twice, and it worked on the very simple stuff I fed it, but I found it hard to use, and, above all, *very* difficult to proofread and correct. The problem is that one often needs several 's in a measure, especially with more than two staves, and it gets quite finicky to disentangle the abc in order to figure out which staff a given note is supposed to be on, or to find a note which needs to be corrected. I thought it would be much easier if one had a pre-processor which would take the present abc multistaff notation and put in the ampersands to feed to abc2mtex. This would give it a more user-friendly multi-staff capability, and avoid the need to write 's in the abc. Cheers, John Walsh To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
RE: [abcusers] dynamics
Thanks, I re-read the abc2midi and I found the dynamics with the other markings. My application will be an interactive GUI text editor that also displays the notes graphically. So it will use ABC as input instead of Midi or the point/click method like most programs do. Thanks for pointing me to Note Editor. I don't think I can use it, but I may use TSE3 for the MIDI input/output. I don't think a parsing library would be helpful to me; I don't think parsing the ABC language is the difficult part. This app is not based on any of the x2ps ones, but I did convert some of the PS drawing routines for clefs, note heads and such. The first version will probably be available in the spring and will run under Windows. But I am using WxWindows so a Linux port will be easy enough. The emphasis will be on extensibility and portability at first, and on features (like different input/output formats) later on. -Original Message- From: Guido Gonzato [mailto:[EMAIL PROTECTED]] Sent: Monday, October 22, 2001 2:58 AM To: '[EMAIL PROTECTED]' Subject: Re: [abcusers] dynamics On Sat, 20 Oct 2001, Aaron Newman wrote: I read in the FAQ that there is no way now to do dynamics in the official ABC language. How are people handling this? the FAQ should be updated. In actual fact, many ABC applications support dynamics; abcm2ps, jaabc2ps, abc2midi, to name but a few. Please check out the ABC draft, http://www.gre.ac.uk/~c.walshaw/abc/abc-draft.txt I am working on a (yet another) free ABC music editing and display program, and for some reason I overlooked this originally. that's very good! What kind of application are you writing? I hope it's not yet another abc2ps clone... in that case, it would probably be a better idea contributing code to existing programs like abcm2ps or jaabc2ps. Also: have you checked out Note Editor, http://tan.informatik.tu-chemnitz.de/~jan/noteedit/noteedit.html ? It's an astounding graphical music editor, but it lacks ABC export. If you're a talented programmer, you might consider helping that project. Also, I would also like the language to be able to handle jazz, so I would be adding some additional note ornaments ('doits', falls), how is this recommended? I can't help you here. It looks like most ABC programmers add their own extensions to ABC to make it suitable for classical music or else, so adding decos for jazz would be just fine. (IMHO.) It breaks the standard, though. Ciao, Guido =8-) -- Guido Gonzato, Ph.D. gonzato at sci . univr . it - Linux system manager Universita' di Verona (Italy), Dipartimento Scientifico e Tecnologico Ca' Vignal II, Strada Le Grazie 15, 37134 Verona (Italy) Tel. +39 045 8027990; Fax +39 045 8027958 --- Timeas hominem unius libri 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] dynamics
On Sat, 20 Oct 2001, Aaron Newman wrote: I read in the FAQ that there is no way now to do dynamics in the official ABC language. How are people handling this? the FAQ should be updated. In actual fact, many ABC applications support dynamics; abcm2ps, jaabc2ps, abc2midi, to name but a few. Please check out the ABC draft, http://www.gre.ac.uk/~c.walshaw/abc/abc-draft.txt I am working on a (yet another) free ABC music editing and display program, and for some reason I overlooked this originally. that's very good! What kind of application are you writing? I hope it's not yet another abc2ps clone... in that case, it would probably be a better idea contributing code to existing programs like abcm2ps or jaabc2ps. Also: have you checked out Note Editor, http://tan.informatik.tu-chemnitz.de/~jan/noteedit/noteedit.html ? It's an astounding graphical music editor, but it lacks ABC export. If you're a talented programmer, you might consider helping that project. Also, I would also like the language to be able to handle jazz, so I would be adding some additional note ornaments ('doits', falls), how is this recommended? I can't help you here. It looks like most ABC programmers add their own extensions to ABC to make it suitable for classical music or else, so adding decos for jazz would be just fine. (IMHO.) It breaks the standard, though. Ciao, Guido =8-) -- Guido Gonzato, Ph.D. gonzato at sci . univr . it - Linux system manager Universita' di Verona (Italy), Dipartimento Scientifico e Tecnologico Ca' Vignal II, Strada Le Grazie 15, 37134 Verona (Italy) Tel. +39 045 8027990; Fax +39 045 8027958 --- Timeas hominem unius libri To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics
On Sat 20 Oct 2001 at 05:41AM -0700, Aaron Newman wrote: I read in the FAQ that there is no way now to do dynamics in the official ABC language. How are people handling this? abc2midi uses !p! !pp! !f! !fff! and so on. I am working on a (yet another) free ABC music editing and display program, and for some reason I overlooked this originally. Also, I would also like the language to be able to handle jazz, so I would be adding some additional note ornaments ('doits', falls), how is this recommended? I suggest you use whichever of H-Z are not already being used elsewhere. James Allwright To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics
Richard == Richard Robinson [EMAIL PROTECTED] writes: Richard On Mon, 22 Oct 2001, Taral wrote: I'll take this time to announce that I am working on a libabc that eventually will handle abc file parsing so that development of new abc applications is easier. Richard If this can find its way into general acceptance, it would be a Good Richard Thing. I agree, but what I want to hear is not so much about new features but a willingness to consider non-standard behavior as a bug (except for documented extensions), and a willingness to fix bugs even if they only affect other people's music. .- and -- operators: Dotted and dashed ties (not sure about these two) Richard As a shorthand for (ab.), do you mean ? What's this supposed to do? I just did a quick test on abc2ps, and it looked exactly like (ab) to me. I assume Taral wants a tie that isn't a solid line, but rather a dashed or dotted one. This is useful in vocal music because if some verses have more syllables than others, you may want to indicate that a given note is sometimes sung on one syllable and sometimes on more (dashed or dotted tie), or is sometimes sung on the same syllable as the next note and sometimes not (dashed or dotted slur). .(...) operator: Dotted slurs (not sure about this one) Richard like (a.b.c.d.) ? Again, abc2ps doesn't do anything different with this than with (abcd). Richard I wonder if these are worth it ? Or do I misunderstand ? I assume so. If you were trying to set vocal music, you would understand why someone wanted them. I think what's being proposed is that: a-a is two tied notes a--a is two notes tied with a dashed tie a-.a is two notes died with a dotted tie (ab) is two slurred notes .(ab.) (or maybe some other syntax) is two notes with a dotted slur. -(ab-) is two notes slurred with a dashed slur. -- Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ ) (617) 661-8097 fax: (801) 365-6574 233 Broadway, Cambridge, MA 02139 To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics
On Mon, 22 Oct 2001, Taral wrote: On Mon, Oct 22, 2001 at 08:56:15PM +0100, Richard Robinson wrote: |F2A2BcF2c2bc| Is this the same syntax that abc2mtex used to use ? And, is there much abc out there that uses it ? I used to have a few, I _think_ I've migrated them all to use the newer and easier V: - being 2-part all the way. This coud well make it easier to drop an extra voice in for just a few measures, but backwards-compatability issues can be a pain ... I'm mostly foregoing backwards compatibility in the case of new features like this. I'll check on abc2mtex. It used a syntax with a '' to separate 2 voices, before the V: was suggested. Looked pretty much like what you're saying, but involved something extra in the K: line, iirc, which no-one else really adopted. Backwards compatability generally ... tricky issue. There's a lot of ABC out there by now, I'd think that the more of it a library could handle, the more likely that library woud be to get accepted. Or maybe all the developers just want to write their own, I don't know. I don't really rate as a developer, but a certain amount of that old ABC is mine :) I've always fiddled about with my own perl filters stuff to make things work the way I want, but have always shied away from writing an abc parser. big job, and imho there are plenty already, with their associated incompatabilities, which I don't want to increase. If a well-separated-out library looked like getting at least some acceptance I might want to look into the perl/C interface, by way of getting a perl parser without writing one. Good luck with it. .- and -- operators: Dotted and dashed ties (not sure about these two) As a shorthand for (ab.), do you mean ? .(...) operator: Dotted slurs (not sure about this one) like (a.b.c.d.) ? I wonder if these are worth it ? Or do I misunderstand ? No, no, these aren't syntactic sugar. I need ties where the curved line which is drawn is made of dots or dashes to indicate that the two notes in question are not always tied together (different voices/verses, for example). Ah, right, I see. -- Richard Robinson The whole plan hinged upon the natural curiosity of potatoes - S. Lem To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] dynamics
On Mon, Oct 22, 2001 at 11:56:27PM +0100, Richard Robinson wrote: It used a syntax with a '' to separate 2 voices, before the V: was suggested. Looked pretty much like what you're saying, but involved something extra in the K: line, iirc, which no-one else really adopted. From what I saw, it looked like it used to separate the case where you had two joined staves (e.g. piano music). Backwards compatability generally ... tricky issue. There's a lot of ABC out there by now, I'd think that the more of it a library could handle, the more likely that library woud be to get accepted. Or maybe all the developers just want to write their own, I don't know. Well, I'm going to implement 100% of the draft standard, so I think that should cover a lot of bases. I'll also cover a good number of the abcm2ps extensions because I use them. -- Taral [EMAIL PROTECTED] This message is digitally signed. Please PGP encrypt mail to me. Any technology, no matter how primitive, is magic to those who don't understand it. -- Florence Ambrose PGP signature
Re: [abcusers] dynamics
On Tue, Oct 23, 2001 at 01:30:30AM +0100, Richard Robinson wrote: Which, doesn't your abc2ps produce dotted notes ? Odd thing, though. My (a.b.c.d.) above ought, surely, to produce staccato notes with a slur over them ? In fact, the first note doesn't appear to have the dot. And (AB.)(c.d.) only produces a dot over the d. I suppose it's my own fault for going out the pub earlier. Try putting the . before the notes: (.a.b.c.d) -- Taral [EMAIL PROTECTED] This message is digitally signed. Please PGP encrypt mail to me. Any technology, no matter how primitive, is magic to those who don't understand it. -- Florence Ambrose PGP signature