Photoshop Key Github

0 views
Skip to first unread message

Chris Richard

unread,
Aug 4, 2024, 12:21:45 PM8/4/24
to inmholavxai
I've had great success with git, version controlling, sharing and collaborating on my programming projects, and would love to do the same with photoshop .psds, illustrator .ais and maya projects. Maya, as you may know, is a brilliant 3D modelling and rendering kit, but its projects are saved sort of like a programming framework, with various directories for source images and textures and the like.
Obviously all files are just numbers, so in theory git would be fine only updating the parts of the .jpegs or maya binaries that have changed, but do you think in reality this would this cause data corruption and tears? Like I say, I'd like to do the same with photoshop and illustrator files.
Most of the people I know who use Maya or similar software, keep their work on a network mounted drive to share with just a couple of collaborators. When a version is ready for release, it is rendered and hosted on a ftp site.
I've had this issue for a long time as well. Done quite some research and there are a few options for you to version control your graphical assets. Some of them require your own server (some requires you to specifically run Windows server) and some can be hosted on a third party server. My favorite (although not completely satisfactory) was Timeline from Pixelnovel.
In my experience, you should make sure that all your collaborators are using the same version of the software (both Timeline and PS/AI/Maya), older versions of PS requires you to run an older version of Timeline which doesn't handle the working tree the same way as in more up-to-date versions.
I've also version controlled large graphical assets with regular Subversion (no GUI) and I found it wasn't all that bad if you're OK with using the terminal. Of course, things like merging, conflicts etc. isn't possible with binaries but at least you get a neat version management with a structured log. Also, with SVN you can lock a file while working with it (which Timeline does for you).
In terms of versioning, there aren't great products out there for that. Adobe used to have a product (maybe still does) but nearly all code versioning systems can't deal with tracking changes in binary files. They're really designed for text based documents.
As for sharing work in terms of open sourcing it or public domaining your work, I'm not aware of a central web site for that. It's a good idea, though. There are a variety of places you can use for different types of works.
Have you tried GitLab for tracking and collaborating on graphic projects? It's like github but downloadable and installable on your serrver. It's about coding but maybe there is some sort of plugin/extension to customize it to the graphic world.
Also there is versioning and file sharing available with Adobe Creative Cloud. The advantage in Adobe CC is that you can actually view the file before you download it, and you can see individual layers (at least I know you can do that with Illustrator files. I haven't looked at my PSDs there to know if layers are individually viewable)
3a8082e126
Reply all
Reply to author
Forward
0 new messages