Post
by Antigone » Fri Dec 23, 2016 9:30 am
@chepelier fou : sorry I didn't see your message earlier.
The idea is to develop "Ableton CI" - for Continuous Integration.
The workflow would be something like:
- you work on your project within ableton live
- you (of course) regularly save your work
- each time you save your work, a little program looks out for your changes (and tries to summarize them in a phrase, a easily understandable "changelog")
- each of these changes are committed to a git-like local repository (with possible branches, etc)
- they can be pushed on a distant repository, and cloned elsewhere (given you have the needed VST, for instance)
* pause : all of this is already pretty easily doable. I would work on it, if it would interest the community. Now comes the cool part :
- since Ableton CLI (command line interface : this is the feature I am looking for) can export from a command line, you can still work on your project while you export another (or the same) project (on the same machine, another local machine, on in the cloud)
- you can automatize this step and generate exports each time you "merge" your work in a certain branch, for instance
- you can "test" your exports with some rules
- you can automatically push your exports (artifacts) somewhere - this artifacts could be the whole song, or stems, or whatever your decide
* bonus benefits
- you can work with several people at the same time on the same project. The changes are merge automatically (and the conflits are detected)
... That's pretty much it.
What do you think ? Would you use it yourself ?
Maybe I should do a full and dedicated post about this.
Again, I have all the required knowledge to develop this, and I am more than ready to work full time on this, if I had Ableton (and the community) support.
