: Version Control for Designers / Alternative to Version Cue I've just been searching around the net for version control that has some support for graphic/Photoshop files. We're currently using BitBucket

@Cugini998

Git isn't just for non-binary files. A simple, local (i.e., not necessarily web-based)* GUI frontend for Git (SourceTree seems good) can handle binary files very well, and Git can even do version control on EXIF metadata, among many other things. Git repositories do not have to reside on a central, web-based server; this is the power of Git: it's a decentralized version control system (DVCS).*(Git does allow "pushing to remotes" if you want to push your local changes to a web-based service.)

Learn Git here,* or read the excellent introductory Pro Git book.*(This uses the command-line version to teach you, but the same ideas apply to the GUI version.)

Vote Up Vote Down

@Kristi927

So far I can see this is a bit outdated topic, but we ran into issue of version control for design. Since we're developing digital assets management solution (I'm one of the makers) we decided to add this functionality right into our product. Right now it allows to control versions of design files, comment over them and put visual marks over the designs. The product is integrated with Slack chat, so it delivers notifications about the comments/new versions/new files instantly. Here is page that explains about version corneal for design - pics.io/design
I will be happy to get comments about the feature right here or in PM.

Cheers!

Vote Up Vote Down

@Debbie163

Here a video showing Auto File Versioning and comment process in Photoshop and InDesign :

Vote Up Vote Down

@Welton168

I was looking around for alternatives myself ... and ran into this one:
sparkleshare.org/
... but I haven't tried it out yet.

Vote Up Vote Down

@Rivera951

Alternative for Version Cue is any Digital Asset Management system that can provide an Adobe Drive integration. Adobe Drive provides basically the following features:


A mounted drive of your file repository
Ability to browse your versioning system's repository via Bridge, Mac Finder or Windows Explorer.
Ability to automatically Check-out files from within Adobe Creative Suite as soon as you make changes to the file.
Ability to check-in files from the File menu of Creative Suite.
Ability to see who has a file checked-out or if you have the latest file or not.
Ability to see previews of files in Bridge as well as metadata.


Adobe has its own Digital Asset Management system that was formerly built by Day Software and now called CQ5 and it does have the Adobe Drive integration. However, it is an enterprise level system and provides many other features and therefore, it is pretty expensive (probably need 0K to start with it).

The cheaper alternatives are out there with different levels of Adobe Drive integration. One that is pretty good is Elvis DAM. You can see the Adobe Drive integration in this video.

Some of these products also have additional features for review and approval workflows allowing users to share files and provide comments and feedback.

Vote Up Vote Down

@Kevin459

You may want to take a look at the Evolphin Zoom product. They specialize in versioning for graphics and have CS plugins.

Vote Up Vote Down

@Connie430

I think this does what you want plus much more. They just made it free a couple of months back.
www.southpawtech.com/tactic/

Vote Up Vote Down

@Ravi4787994

Version Cue, in my experience, is garbage. I have two systems for two different teams going right now.

SVN via Cornerstone
I've been running a large volume of creative work through SVN via Cornerstone for Mac for over a year now. It's a very slick and easy to use app that makes VC seem easy. It doesn't provide visual previews of the files like I believe PixelNovel does but our detailed change notes have been more than adequate. Cornerstone has been a very robust solution for the localized team I work in.

Git via SourceTree
I also just began coordinating a remote team via Bitbucket.org using SourceTree. Git has a little steeper learning curve at first but it's working well for us. We're essentially following the same principles as the SVN set-up, ie detailed change logs.

The differences
Git operates under the model that each user downloads the whole repository (history and all) to their machine. To keep this manageable, it's best to have a separate repository for each project. It's nice to have a repository that's easy to archive and retire when the project is over.

SVN, on the other hand, allows the user to checkout the latest version of a directory within a repository. If you want to roll back to a previous version you must connect to the server. This is a good system for a centralized repository that contains all the projects under way. I prefer it for a high volume environment where many simultaneous and often interconnected projects are underway.

Vote Up Vote Down