There’s a grace note in the first bar, the first “c” in the second section is marked natural not sharp, and, though I didn’t change this the four eighth notes in the first full bar of the second section would seem to me to be under a single slur rather than 2 shorter slurs. I put in the two extra bars, but I don’t like the spacing much (and note the “L” is not needed). I’ll play around with that a bit.
Don’t know what I was thinking with the sharp, of course it is a natural, good catch, same with the grace note I missed. For the most I was trying to show the minor proofreading I have to do with the original piece. Beats per measure, clarity, etc. I’m still trying to find the line I want to draw between transcribing and interpreting. Even at that I have to be conscious of my lack of music knowledge and copy error rate. I am sure I’ll have to give the whole document a thorough proofreading when I am done.
I’ll have to look into EasyABC, the big thing I am missing is the ability to print several tunes on one page. Eventually I would like to figure out a way to set it up as an HTML so I don’t know how useful .ps format will be in the long run, but that is a long way into the future.
Downloaded EasyABC, about the same interface as another program I have used, but less buggy and over all it is much more polished, and seems to handle errors better and can play midis with things like trills. It will be a useful tool. Now if only I could change the default midi instrument from piano...
The wiggle at the end of the first line simply means “there is another line coming”. You don’t need to notate it in ABC.
The tapering parallel lines at the end are simply the end of the tune, with the same meaning as a thin-thick double bar. They DO NOT mean an immensely long rest. Just write “|]”.
It’s more important to get the ABC readable (so that beats align between lines when displayed monospaced) than to try to reproduce semantically irrelevant typographic details. If the ABC is readable you’re less likely to make transcription mistakes.
There is an ABC forum at http://abcnotation.com/forums . Not very active. I dropped out of the ABC forum after Toby Rider dropped it - some people went off to Yahoo, but no way was I ever going to subscribe to a forum run by that bunch of spamming arseholes.
Yep, I know that, but if I could preserve that aspect in ABC, I would.
That is true, but same as before. It is a moot point since the four bar thing is not an option.
I think we have a difference in opinion here. I copied about 20 pages of index, terms, and examples that are pretty much useless to anyone that just wants to play the tunes. In reality, if all I wanted was to preserve the tunes, I could skip well known tunes like Rural Felicity and The Rakes of Marlow. Easier yet, I could just be content with the PDF.
Basically I saw the book referenced several times but couldn’t find a modern reprint of it. So, for now I am just trying to reproduce most of it with slight editing in places where it is absolutely needed, but leaving the harmless quirks and redundancies where possible. The most important thing is that I like what I am doing, otherwise, I couldn’t bring myself to do any of it. The logic in many ways is probably lacking…
I’ll have to check out the yahoo group.
I’ll just add I’m greatful for the pointers I have recieved so far. Thanks all.
Well, I don’t quite agree Jack. The wiggle, if properly done, indicates the pitch of the coming note on the next line. You certainly don’t need it, but there may be a way.
Jack, you misread my comments about the long rests. Using the long rests is a way to get the kind of bar the OP wants. It certainly has nothing to do with actually meaning rests. Though, in passing, since they come after the end of the tune the rests would not interfere with the playing of the tune unless you were looping it.
In EasyABC you can select a tune and choose “Align Bars” in the edit menu and it will line up things nicely (it uses a monospaced font for abc display). Quick, neat, and as Jack says helpful for proofing.
To change the playback sound of the melody go to “ABC Settings” in the settings menu. In the dialog window that opens up you’ll see a field where you can change the sound. I’'m not sure exactly what you may see there. It probably depends on the sound generating device in the PC. On a Mac no problem. No way to change the sound of the “boom-chick” chord accompaniment, but you can turn it off and probably don’t need it anyway for the book you are working on.
Finally, you misunderstand Jack’s comments about spacing the abc I think. He’s talking about spacing out the ABC itself NOT the resultant music.
I was trying to use the I: function to choose instrument code 73 or 74 (really anything but piano). It seems that the instrument standards for midi are fairly standardized. I should have been able to do this by adding %%MIDI voice instrument=73, but changing the program default is a better solution.
If there is a standard I’d probably conform to it. One consistency thing I realize I have has to do with how I break up quarter note and eighth notes. Sometimes I use dfg2fd other times df g2 fd. I try to save screen space because for me it makes things easier to compare, but sometimes break it up in the way I would two strings of eighth notes. For me the text wraps around the page and doesn’t come close to the spacing of the notation I am coping from, so It doesn’t really matter if they are additional spaces to line things up better.
I guess there are two ways to use ABC notation, one as music notation itself, in which case I would strip out everything except the bare essentials, and another where it is used as an input to create sheet music. I am concentrating on the latter but to make it “legible” removing the +segno+, +trill+, etc. seems trivial, especially compared to going back to insert those marks for sheet music.
would have worked. You just had the syntax wrong. The I: is an information command in the header and abc2MIDI will ignore it.
As to spacing: aside from barring of notes by not leaving spaces between them there is no standard. I usually write things as compressed as possible when entering music, but then spacing things out afterwards will make it much easier to correct.
The point about making the ABC source legible is that it provides a check on correctness of transcription. If what you’ve written doesn’t look right there’s a good chance it isn’t right (either your mistake, or maybe there was a mistake in the original that requires editorial intervention).
I normally use BarFly for transcription. That gives me four different kinds of correctness check, and I use them all on every tune:
viewing the staff notation
listening to a playback
aligning the ABC source
built-in error checking, e.g. for consistent bar lengths
The last will not work if you deliberately introduce nonsense like rests for purely graphical effect, and if you put in stuff that can’t play right, the playback won’t tell you anything.
“+trill+” is silly. “T” has been standard notation for trills in almost all ABC software for 10 years now.
I don’t think Barfly is cross platform, so I cannot check to see how it differs from EasyABC. Easy ABC seems to have the same checks and doesn’t seem to have problems with redundancies. +trill+ may seem like a pain, but If I ever wanted to change it I can simply do a find>replace function to either change it to “T” or delete it completely. With plain “T” replacement for the document would cause problems because it would cause titles to be changed too. For general use though, I can see how “T” would be preferred.
As for the rests being used for a graphical element, that would be put in last (if at all) with a simple replacement of |] with whatever else, but that is not what I would be going for. The document doesn’t use the modern thin-space-thick line, so basically it is like the :S: or quarter rest symbols, a different font. A better example is the titles. Chances are I will not be able to find a simple way to render the things with the same script as the book, and I’ll end up with something like Times New Roman.
If you use standard ABC, other software can process it. Playback programs can interpret a “T” as some sort of macro and do the appropriate (in BarFly you can redefine it to suit the idiom). “+trill+” is an archaic idiom that only generates staff notation.
No … +trill+ (or now officially again !trill!) and the entire redefinable decoration mechanism is a current idiom, not archaic at all, and supported since at least the 1.7.3 standard (1999). Any compliant app should recognize it for either printed rendering or playback. T is simply a default assignment - but yes, it should be recognized by compliant apps as well.
Click on “Making Music with ABCPlus” and then download abcplus_en-2011-03-31.zip. Unzip the file and take a look at the big pdf file. It will tell you more than you want to know about using abcm2ps (what EasyABC wraps around), format files, changing fonts etc. etc. Jack is correct that there are some somewhat silly extensions of things here, but still that manual will tell you lots and show you the results of various things.