Hacker Newsnew | comments | ask | jobs | submitlogin
JonnieCache 649 days ago | link | parent

I'm sure lots of bigger places do use it. In the world of music, there are studios everywhere that have maybe a dozen staff, making a lot of money and producing a lot of output, where version control is an unheard of concept. No audio production software that I'm aware of has any provision for version control.

I was kindof assuming that it would be the same for mid to smaller sized movie/tv studios as well, but at the same time I wouldn't be surprised to learn that you can get a plugin for Premier or whatever that does it.

I know for a fact that there are many largish advertising agencies out there who have fileservers with hundreds of ProjectName01, ProjectName02 etc style directories.

Why do you think apple brought "Versions" or whatever its called in with lion?



megrimlock 649 days ago | link

Thanks for clarifying. I agree there are many environments that would benefit from version control but that lack the technical resources to make it happen with existing tech.

Versions (and Time Machine history) are good steps to part of this, in that they are easily available and understandable, but they don't solve the collaboration aspect. How do you diff and merge your local changes into the NEW_final_v2_UPDATED.xls that was emailed to you? I'd summarize the problems as:

- identfying & organizing versions of the same document in ways manageable by normal humans (i.e. not a set of variably-named files spanning email attachments and shared folders, nor a graph of nodes identified by 20-byte hashes, nor a rigid interface to a versioned-file server)

- diffying & merging non-text document types (images, audio, spreadsheets)

I agree this would be a valuable problem to solve well!

-----

esonderegger 649 days ago | link

I use Sequoia (http://pro.magix.com/en/sequoia/overview.527.html) and I'm very happy with the 'Save Project Copy' function. When I start a new project, I create a 'history' folder and the project copies go in there, named as project_name-timestamp.VIP. I do that every time I'm a stopping point, much like how I use 'git commit' on a code project.

That doesn't mean there isn't huge room for improvement in this arena. An approach like this (or OSX's versions) doesn't allow you to do anything like 'git diff' to see what's changed from version to version. I can imagine this is a very difficult problem for binary data, however. Also, distributed version control on media production software could allow for multiple users to be editing a project simultaneously.

Unfortunately, I don't really see GitHub being able to help much here. For example, any work done to make ProTools files git-friendly wouldn't also work on Photoshop files. I'd love to be wrong about this, but I suspect seeing version control in media production software would require redesigning the application's file format from the ground up, and would be a task for each software company to do on their own.

-----




Lists | RSS | Bookmarklet | Guidelines | FAQ | DMCA | News News | Feature Requests | Bugs | Y Combinator | Apply | Library

Search: