4 ms·

It's strange. We have so many widely available tools to keep a collaborative code history, but when it comes to art assets (images/music/sound/3D models/videos)

It's strange. We have so many widely available tools to keep a collaborative code history, but when it comes to art assets (images/music/sound/3D models/videos) the general consensus is just dumping everything into a central repository (svn/perforce) or use some kind of large file extension which does basically the same thing. Visualising changes, multi-checkouts and merging is impossible. Seems ripe for disruption? Or will this stay an unsolved problem forever?

hellofunk 11y ago
Is it because code is text and assets are usually binary? How do you do a diff reliably on a binary file?
- ndepoel 11y ago
  That depends on the file type. Several version control clients can already detect image files for example and show a visual diff between revisions. There is still a lot of room for improvement and standardization however.
  - orecht 11y ago
    The main problem is not diff but merge. You currently can't merge changes to images, textures etc. The whole advantage of DVCS like git is that it allows to work in parallel and merge effortlessly. The day we can merge photoshop, maya and 3D studio files central repository for art files will not make sense any more. But that day has not come, yet AFAIK.
    - craigjb 11y ago
      What kind of artist work can you practically distribute between multiple people and merge? Most things like this are broken into pieces and each piece is tracked separately and assembled later. I think this is a big mistake programmers make when trying to create VCS for other industries. A lot other fields with binary files don't care about merge as much. Like electronic design automation: track every part's history and even every module on a board or die layout. But, practically it's difficult to have two people productivly work on the same small piece simultaneously. [edit] I also think a bunch of the reasons programmers require merge are because code is organized into files. Organization into files is arbitrary and often doesn't correlate particularly well with logical structure.
paddi91 11y ago
My startup tried to solve exactly this problem in the Electronic Design Automation domain. We provided VCS and compare functionality focused on the needs of this industry. We pivoted. The main issue we faced is the way the electrical engineers work and how difficulty it is to change this. It was incredible hard the explain these people how to properly use a VCS. We focused on a simple interface and tried to optimize on the way electrical engineers work. No chance! Obviously the same applied to LayerVault [1]. [1] http://thenextweb.com/apps/2015/03/11/layervault-the-version-control-app-for-designers-is-shutting-down/ http://thenextweb.com/apps/2015/03/11/layervault-the-version...

hellofunk 11y ago

Is it because code is text and assets are usually binary? How do you do a diff reliably on a binary file?

ndepoel 11y ago
That depends on the file type. Several version control clients can already detect image files for example and show a visual diff between revisions. There is still a lot of room for improvement and standardization however.
- orecht 11y ago
  The main problem is not diff but merge. You currently can't merge changes to images, textures etc. The whole advantage of DVCS like git is that it allows to work in parallel and merge effortlessly. The day we can merge photoshop, maya and 3D studio files central repository for art files will not make sense any more. But that day has not come, yet AFAIK.
  - craigjb 11y ago
    What kind of artist work can you practically distribute between multiple people and merge? Most things like this are broken into pieces and each piece is tracked separately and assembled later. I think this is a big mistake programmers make when trying to create VCS for other industries. A lot other fields with binary files don't care about merge as much. Like electronic design automation: track every part's history and even every module on a board or die layout. But, practically it's difficult to have two people productivly work on the same small piece simultaneously. [edit] I also think a bunch of the reasons programmers require merge are because code is organized into files. Organization into files is arbitrary and often doesn't correlate particularly well with logical structure.

paddi91 11y ago

My startup tried to solve exactly this problem in the Electronic Design Automation domain. We provided VCS and compare functionality focused on the needs of this industry. We pivoted. The main issue we faced is the way the electrical engineers work and how difficulty it is to change this. It was incredible hard the explain these people how to properly use a VCS. We focused on a simple interface and tried to optimize on the way electrical engineers work. No chance! Obviously the same applied to LayerVault [1]. [1] http://thenextweb.com/apps/2015/03/11/layervault-the-version-control-app-for-designers-is-shutting-down/ http://thenextweb.com/apps/2015/03/11/layervault-the-version...