The idea here is to have a system where you start off with some raw tracks in flac format or something.

Then, edits to the tracks are described using a textual description language. One can then read the edits, and use them to perform the required changes until you end up with the end result. One edit can base itself off the output of another, so you end up with a dependency tree.

The advantage here is that once everyone has the raw tracks, every change to it is super light and easy to share, merge, etc. That way people can work on a track together, collaborating, and they don't have to send a bunch of audio files back and forth.

I have an example on my laptop I haven't copied anywhere else, and it uses redo and sox to compute the end results.

This works quite well, since if I change one property it only performs the changes on the tracks that depended on it, the rest it can use from last time.

Now, editing a directory full of files is how I like to work, but a graphical tool could easily be written that just sat on top and made the editing more fancy, still doing directories and stuff in the backend for easy sharing.