bloke wrote: ↑Mon Aug 26, 2024 3:10 pm
' too bad there's no "open source" (as with OpenOffice/LibreOffice).
There is
LilyPond. I have the impression that's sophisticated enough to qualifiy as "engraving", but of course the learning curve is intimidating, and I don't know if anyone ever gets real fast at it. I fiddled around with it some, on a much less ambitious level just out of curiosity. I might have kept up with it, but circumstances. I think it may depend a great deal on how your brain works, it isn't for everyone.
Because LilyPond is open source, it provides a look at what's going on under the hood. There are three computer programming languages involved: 600,000 lines of C++, 140,000 lines of Scheme and 120,000 lines of Python. This has something to do with why these applications' lives come to an end. The revenue doesn't support the hours of skilled labor they require. Even if it's pretty well engineered to start with, the accumulation of features and fixes over the years, while trying to maintain backward compatibility, naturally tend to make it a dusty horror inside. People who understood it retire, etc.
There's another kind of open -ism involved here, too. Like your OpenOffice has to be able to take apart "Word" documents, anyone who would try to bring OpenFinale would have to grapple with Finale's application data files, and I assume the format thereof is not public knowledge. In some contrast to LaTex, and LilyPond, where the text document is both data file and user interface. Neither is a sold guarantee of immortality, but the proprietary files are more obviously a dead end in that respect.
I see some references to a LilyPond accessory that might partially translate some version of Finale files (maybe .musx, don't know that for sure.) This isn't likely to make anyone real happy at this point, but as the circumstances have changed, it could be something of greater interest now. Maybe the nice people at MakeMusic are getting ready to publish the data format (ha ha.) Having the format document is the first step, then someone has to figure out how to translate that properly into an open format, if that's even possible.
I use Lime. The developers are, as far as I know, some academics, so it's a relatively low budget enterprise, and when Apple dropped support for 32 bit applications, it stopped working on MacOS and it looks like they're never going to do anything about it. So my Macbook is running a 7 year old OS, but that's no big problem. (It's likely batttery problems that will be the end of MacOS for me.) They have a paid user key, but it's good forever, transferable to whatever computer you're using, etc. But some day, it will end, and my stuff will have to come out of those Lime files. Luckily it's trivial enough that little will be lost in translation to XML or whatever. I actually tried Dorico. Bleah. I'm sure there were some things I failed to understand, but I have a vague memory of incredible missing functionality, like it had all the dancing babies and stuff but couldn't walk and chew gum at the same time. Maybe it's just that learning curve.