Both ingredients are valid, but i prefer mine with a zest of not letting that which i cannot control burden me, over a handful of IDGAF.

oh, wait, i forgot about all the sharecare non-pirate bears that just upload good stuff for the careshare… you know, that other 3/12 of the catalogue…

The service where they crowd sourced 2/3 of their catalogue from “sharecare” pirate bears?

There’s also SCEE available in the f-droid app repository, which is a modified version if street complete for more advanced editing.

https://github.com/Helium314/SCEE

Very good! Thank you!

Great point! what is your suggestion?

Seems like a great idea!

I’m somewhat surprised by the choice of XML, but why not?

This goal worries me a bit:

The format should be able to express the track and timeline structures of the exporting DAW as is, leaving it up to the importer to use this data and flatten it as needed.

Leaving things up to one side or the other seems like a hard way to reach any meaningful consensus. But I’m basing this on gut feelings from seeing i.e. how ActivityPub is only partially adopted by the different fediverse apps who tend to “leave it up to the importer to use the data and flatten it as needed”. I have no experience in interoperable data-structures on my own, so there are probably 6372 reasons why i am wrong here.

My main hurdle with collaboration has never been DAW data, as lossless audio + midi will get my counterparts and myself a long way. The issue has always been platform interoperability of addons.

But over all, this is music to my ears! It seems like a sane path to better interoperability and that’s exactly what i wish upon the (computer) world. 😅💜