alt Hacker NewsI'm not a programmer and I don't use Git, but I am a record producer and it's not clear to me what advantage this provides.
When I start a DAW session I simply prepend the session file name with the date (YYMMDD). If I make a significant change to the session and might want to recall the older version I 'Save as' my session and update the date - or I add a version number if I make more than one new version in the same day.
For example:
250820 Song Title
250821 Song Title
250821 Song Title 1.1
250822 Song Title
At the end of each day I render the current project as a stereo audio file using the same naming conventions:
250820 Song Title
250821 Song Title
250822 Song Title
If I need to "merge" an older version of a session with a newer session my DAW (Ableton Live) allows me to drag tracks from the previous session. A few edits later and I've successfully imported the older asset that I wanted.
That's it. That's all of the version control that I need. All of my assets are saved in the project folder, I have an easy to parse chronological record of my project's development, and I always know the most recent version.
What if you want to experiment with something but you don’t know if it will work out or not? How do you keep track of what was before the experiment so you can roll back to that if it doesn’t go well? How do you collaborate with other people? If someone has a change they want to make, is there ever a more senior person who needs to check if the sound is up to standard before it becomes an accepted change to the track? Those are some examples I can think of that might be relevant. Not rhetorical questions, I am curious if those don’t apply somehow - I’m a developer with some hobbyist production experience and it seems like those would be nice things to have.