 We tested it.
50,000 musical objects: 14.5KB total on disk. Not megabytes. Kilobytes. That's not even 0.3 bytes per note. MusicXML equivalent: ~50MB. That's 3500x larger. Save/load time: about 250ms on a crappy 2017 MacBook Pro. These are just the core musical objects - pitches, rests, chords, articulations. A complete score adds instruments, parts, staves, layout data, and more. But the efficiency gains indicate what's possible when you eliminate redundancy at the foundation. The venerable technique hash-consing (1958, from LISP and symbolic computation) works. Of course it does – and how! Article on implications coming.
6 Comments
Scott Lannie
28/9/2025 01:32:45
Peter those measurements / numbers are truly astounding!
Magnus Johansson
1/10/2025 09:57:02
Hello! Igor Engraver can be run on MacOS and Linux via CrossOver; see https://www.codeweavers.com/compatibility/crossover/igor-engraver-17
Scott Lannie
29/9/2025 01:53:33
Hi Peter, I started a thread on a composers forum about Ooloi, it’s an interesting thread, and may benefit from your input 29/9/2025 09:12:03
Hi, Scott! I'll be joining soon. I can already see several misconceptions about Java, the JVM, compression, the server/client relationship and why and how this could ever get any attention ;) There are answers to all of those, but people need to read my blog a little more carefully.
Scott Lannie
29/9/2025 09:34:27
Thanks Peter, I have studied everything you have written regarding the development of Ooloi but because I don’t have any experience with programming languages I can only comment on your results so far. 30/9/2025 09:50:27
I did a similar search on Grok, and you're right – there's certainly a lot of detail there, most of it very accurate. I'm impressed! Leave a Reply. |
AuthorPeter Bengtson – SearchArchives
January 2026
Categories
All
|
RSS Feed