Re contemporary notation, I disagree with this. I work professionally on
New Complexity School scores, and every composer has their own notation
and preferences and idiosyncrasies. Other contemporary schools all have
their own individual styles. We are nowhere near standardisation of the
sort that applies to Common Era music. I have a Scheme library of code
for my engraving that took fours years to develop in conjunction with my
composer colleague. It's completely meaningless for anybody else. I
don't know of many composers settling on Lachenmann notation, and
indeed, many composers refuse to settle on a standard as part of their
entire aesthetic. I think this is why the contemporary notation project
has stalled - there is no and will not be any uniformity to make it
worthwhile.
I'd suggest you look at other aspects of LilyPond to work on, sincerely.
Maybe something really practically useful like MusicXML work.
I thought MAX is not open source, but a quite expensive commercial
program from Cycling74?
https://cycling74.com/shop
Does not really fit the open source world of LilyPond, even though one
library project may be open source.
Or you could fix Issue 34!
Andrew
On 21/11/2020 5:00 am, 98123981293 1293812397123 wrote:
Ok; the project concerning contemporary notation looks interesting and like
it may leverage my background; per that problem description, re: specific
composers: Helmut Lachenmann's notation is becoming widespread, so perhaps
it would be worthwhile to engrave an entire score by this composer and
develop custom Scheme extensions for doing so. Also, thank you for the
Gitlab link and tip on "Frog" problems; I'll get set up there and start
watching for things I can help on.
