> Have you reversed engineered the Ableton project format? I'm not sure I'd call it "reverse engineer" even, you'd do something like: $ mv DefaultLiveSet.

> Have you reversed engineered the Ableton project format? I'm not sure I'd call it "reverse engineer" even, you'd do something like: $ mv DefaultLiveSet.als DefaultLiveSet.xml.gz $ gunzip DefaultLiveSet.xml.gz $ cat DefaultLiveSet.xml | head <?xml version="1.0" encoding="UTF-8"?> <Ableton MajorVersion="5" MinorVersion="10.0_370" Creator="Ableton Live 10.0d150" Revision=""> <LiveSet> <NextPointeeId Value="17335" /> <OverwriteProtectionNumber Value="2560" /> <LomId Value="0" /> <LomIdView Value="0" /> <Tracks> <MidiTrack Id="12"> <LomId Value="0" /> There isn't much more to it :) It wouldn't say it's the best structure/design, but it's all there in plain-text basically, so pretty easy to just read through it or search. > currently LLMs tell me "Live updates break things constantly". Are my fears oversold? Just stick with the same Ableton version for the duration of your work on those tracks, it's basically what you wanna do regardless of how complicated your project/setup is, as things do change between versions. But FWIW, none of the projects I've manually edited have broken, at least when I last moved from 11 to 12. > I was trying to control all the parameters of Ableton native synths which was a headache. For that you'd go for MIDI, but if you truly need 100 project files to run one by one, then generating those XMLs with whatever, changing the file-name and opening up in Ableton with the midi afterwards feels like it shouldn't be too hard.