Audwio
Version control and collaboration for music production.
-
2
The version-control angle makes sense for music projects, especially when you want to revisit an earlier state without losing the current one.
I’m curious what part of the existing music workflow has been hardest to fit into a Git-style model?
-
1
Thanks for commenting!
The answer is definitely "merging" itself—the core git operation. You can't merge two peoples take on a mix, the way you merge two peoples edits to a function. :)
-
1
That’s an interesting constraint because it suggests the Git analogy breaks exactly where collaboration becomes subjective.
I’m curious whether you’re treating that as a limitation to work around, or as a signal that collaborative music needs a fundamentally different model than Git.
-
1
Neither, exactly. I just gave up trying to make the merging part work for audio, and just kept the rest of it; things like tracking history, branching, and reviewing changes. That works fine for music, just not combining two peoples edits.
The real job is giving people what they need to make a good listening decision. 🙂
-
1
That distinction is useful. It sounds like you’ve kept the parts of the Git model that actually help with creative iteration, without forcing audio into a collaboration mechanic that doesn’t fit.
I’d be interested in continuing the conversation outside the thread. What’s the best email to reach you on?
-
1
Sorry for the delay. Started my 2nd year of C# education.
Apparently I can't post my email in comments.
-
1
No worries at all — and congrats on starting your second year. You can email me at hello@beryxa.com whenever you get a chance.
-
-
-
-
-
-
Comment