On Friday 07 July 2006 4:24 am, Heikki Johannes Junes wrote: > I would like to (am going to) drop LilyPond 2.2 and 2.4 from the trunk > (1.3?) mainly for the following reasons:
> are so remarkable, that an average should be protected from the above > difficulties. LilyPond versions 2.6 and later are really professional > version, why not promote their use? I have no problem with this myself. I would argue that if someone really wants to use LilyPond 2.2 for some reason, then they can use that old software with *our* old software. I don't see any reason to maintain backward compatibility forever. While you're in there, I've been thinking about an option that I haven't had time to look at yet. Your "merge tracks with same non-zero name" is an elegant way to deal with the voice problem, and you have an option to link everything with a system bracket that also works well. What about a combination of these two ideas to merge tracks with the same non-zero names onto a grand staff, based on the initial clef in the first segment on each track? So you could have something like piano [treble, voice 1] piano [treble, voice 2] piano [bass, voice 1] piano [bass, voice 2] all come out piano [grand staff, all voices] It seems workable to me, but I haven't looked at coding it. What do you think? This would solve another one of our long-standing "Rosegarden is useless because..." problems. One of the next ones that's in a similar category would be the problem of putting a trumpet solo on top of a grand staff, all within system brackets. So I think it should be worked so the system brackets and grand staff can work at the same time, if possible. trumpet [treble, voice 1] trumpet [treble, voice 2] piano [treble, voice 1] piano [treble, voice 2] piano [bass, voice 1] piano [bass, voice 2] all come out system ___/trumpet [treble, both 1st and 2nd trumpet voices] bracket \piano [grand staff, all voices] That would cover a lot of the most common music I see in print, I think. You could use a Tiny directive to print the top part cue sized too, which would cover yet another possibility. (I understand the way to do that in hand coded LilyPond would be to pull in the trumpet voice with some size override or whatever, but I'm thinking in terms of what we could export mechanically in order to yield a similar result on the printed page, without the user having to have anything to do with the .ly file directly.) -- D. Michael 'Silvan' McIntyre ---- Silvan <[EMAIL PROTECTED]> Linux fanatic, and certified Geek; registered Linux user #243621 Author of Rosegarden Companion http://rosegarden.sourceforge.net/tutorial/ Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
