Hacker News Reader

Comment by NikolaeVarius | Hacker News Reader

Why wouldn't it be possible to version control in the same way we version control other random files? Just treat it as a stream of arbitrary data.

View on HN

You'd miss out on all the goodies of version control like seeing what has changed. Ideally, version control for musicians would have the ability to show "change panning of guitar a to 0.3 and volume to 0.1" similarly to a code diff. Otherwise all you've got is just a bunch of backups, possibly with semi-informative commit messages if you really put a lot of effort into it.

I wish that there was a way of getting Logic X to output a list of changes you've made during a session. When I collaborate with my bandmate, I often struggle to describe all the changes I've made since he passed me the project. I'd also like to know the changes he's made.

My bandmate often works on our project while it's in a Dropbox folder, so I get a steady stream of notifications about impulse responses and undo files being changed; not very useful. I can tell when he's tracking because the new .aif files come over but that's about it.

I mean, Adobe Suite programs have a history feature where all your alterations to the image are listed chronologically. I don't know how that system works personally but it is a similar class of application & feature.

It would be possible if there was a change log constantly updated that was meta data to the stream. In other words, each time something is done on the audio/visual file, log what it was, and version control that.

ES/CQRS for audio editing.

This is essentially what non-destructive edits are in the photo-editing realm

Yes, but more tantalizing would be some kind of wavelet-based semantic versioning. This might allow merging.

Reply on news.ycombinator.com