Hmm. So i tried typesetting a single page of piano music that I had put together in Sibelius (amounted to seventeen none-too-complex bars; probably should have picked something with some dynamics
). It took about two hours (maybe a little more) from when I started up the package to input the notes, with maybe three more hours after that just spent fiddling about trying to figure out what I could change.
The approach to notation (not the internal syntax, but the output) seems to be a lot more "professional" than that of some other applications (as seen by the examples on the page I linked to above). The openness by which they document their methods of type-setting (is that the right word?) is really refreshing.
Having to input all the notes name by name can be a bit of a pain, but it does have it's upsides. But I would never write an extended work in it unless I thought that it was going to be performed by several different performers. I was also hoping to us it for input/output of programs I was writing, but that didn't quite work out (for reasons not entirely lilypond's fault, I must say).
So here are two bars for comparison. Lolipop to whoever can guess which is Sibelius 4, and which is Lilypond 2.something
and
There are problems with both of these that I could have fixed manually, but this is pure, unadulterated default output (except maybe that I had to manually drag the bars apart in Sibelius to stop the notes on the upper staff from overlapping in the lower staff).
I found the remark about the even-position of notes with staffs naer one of the pages linked to above to be very interesting (
http://lilypond.org/web/about/automated-engraving/typography-features) , and was wondering if any of the people who use time-space notation would care to offer some views about it?
My partner uses this programme regularly and is very fond of it due to the standards it uses (i.e. it produces scores similar to plate-engraved music which are therefore better-looking and easier to read than other well-know notation problems).
Programs=problems, eh? Tell me about it!
Not having used Lilypond, I probably shouldn't pontificate, but before finally settling with abcPlus notation I read my share of reviews. A lot of people seemed to think that the changes to the input file structure with various new releases of Lilypond made the whole business of music engraving more complicated. If you're happy with a system that requires you to input a text file to generate the output, why not use something like MusicTeX, which seems to be more stable, or possibly MusicXML (which seems to be almost impossibly long-winded)?
MusicXML seems mainly a (messy) notation data format from a quick glance. Can't say it looks very good. Hmm. Of course, lilypond, as well as abcplus, both have graphical editors which should in theory make things a lot easier. (One nice thing about the text editor for lilypond was that clicking on a note in the rendered file brought you to the code for that note in the source). The ABC notation seems to differ very little from that of lilypond, and some of the graphical editors But lilypond seems to have a few more things to do polyphonic writing. It might be worth quoting the following form their website
User-interfaces and syntax are what people see and deal with most. They are partly a matter of taste, and also subject of much discussion. Although discussions on taste do have their merit, they are not very productive. In the larger picture of LilyPond, the importance of input syntax is small: inventing neat syntax is easy, writing decent formatting code is much harder. This is also illustrated by the line-counts for the respective components: parsing and representation take up less than 10% of the code.
That is to say, type-setting is their main concern more than input. I think I do prefer a lot of things about lilypond's type-setting to Sibelius' (I've not tried Finale ever I think). And given that it's free, I think I'd go with it as a renderer of scores in principle in a lot of cases (I haven't had a chance to check out the quality of the abcPlus renderer in detail, but I suspect it is not as feature-full as lilypond's
).