dawproject

Splice[1] Studio[2] used to be version control for music software (from about 2013-2021). You could browse Ableton Live (and a few other DAWs) projects and see the tracks and rendered versions each time you saved, add metadata etc. They pivoted into the more profitable sample discovery and sales business later and dropped the less profitable studio product. I expect over the next few years that the DAWProject[3] open source protocol for exchanging between DAWs could make it possible for some of the ideas of splice come back without having to rely heavily on undocumented binary formats. [1]: https://splice.com/ [2]: https://cdm.link/splice-studio-is-free-backup-version-contro... [3]: https://github.com/bitwig/dawproject

One thing I'd like to see is native support for some notion of pitch other than 12-tone equal temperament. Looking at their example, I see this: <Note time="0.000000" duration="0.250000" channel="0" key="65" vel="0.787402" rel="0.787402"/> ...which looks like it's basically just a representation of the underlying midi. One way they could represent other pitches is for "key" to allow a floating point value rather than an integer. So, for instance, 65.5 would be a quarter-tone (50 cents) above note 65. According to their reference document, "key" is currently required to be an integer: https://htmlpreview.github.io/?https://github.com/bitwig/daw... There's other ways to support microtuning. They could apply a tuning table to the midi notes, for instance. (Ideally they should support more than the 128 notes that midi supports, because 128