Has anyone tried Git style versioning with .ALS files?

[RedPillTaker]

Even if you don't reap the benefits of text file comparison... being able to save your file locally but not commit a change and the features of branching/tagging is huge. Only drawback might be space. Haven't run the numbers on that.

[Gotek]

I am interested in trying this out!! anyone else?

[jbaylies]

I've been doing this for an ableton project that I use with a max project but TBH it hasn't proven to be super useful... https://github.com/jbaylies/sousastep/c ... 20Live.als

[LoopInfinitum]

Very related, I just wrote a tool that tracks the underlying XML in real time, so it would work for logical git versioning (as opposed to tracked revisions of binary files, but no meaningful diff or history on them). Check it out:

https://www.youtube.com/watch?v=mulwc2U11o8

[LoopInfinitum]

.

[Gral]

I use Git on my own server. My Ableton projects are all on a compupter, specially set up for this purpose, in the Music directory. I regularly push this directory, including everything in it. I don't bother about the disk space required for this.

My idea is that in the event of a problem, I can check out the Music directory again and get the last status back. For test purposes, I renamed my local Music folder and then checked out the Git-Repo Music. Had no problems. Everything was great.

You can also create cool branches. For example, I have some projects from the early days that I have stored in a branch callecd "First Try". I deleted them locally, so they no longer bother me. However, they can be retrieved at any time if necessary.

Another advantage I see is the history function. If you commit regularly, you have a nice overview of when you did what.

Is there anything against this approach?