Your standard "shot" will contain 10s or hundreds of versions of animation, lighting, texturing, modelling & lighting. Not to mentions compositing. They are often interdependent too.
A movie like shrek will have literal billions of versions of $things.
> Does anybody knows how that works?
This changes by company, but everyone tends to have an asset database. This is a thing that (should) give a UUID to each thing an artist is working on, and a unique location where it lives (that was/is an NFS file share, although covid might have changed that with WFH)
Where it differs from git et al is normally the folder tree is navigable by humans as well so the path for your "asset" will looks something like this:
/share/showname/shot_number/lighting/v33/
There are caveats, something like a model of a car, or anything else that gets re-used is put somewhere else in the "showname" folder.
Now, this is all very well, but how do artists(yes real non linux savvy artists) navigate and use this?
Thats where the "Pipeline" comes it. They will make use of the python API of the main programs that are used on the show. So when the coordinator assigns a shot to an artist, the artist presses a button saying "load shot" and the API will pull the correct paths, notify the coordination system (something like ftrack or shotgun) and open up the software they normally use (maya, zbrush, mari, nuke, etc etc) with the shot loaded.
Once the artist is happy, they'll hit publish.
The underlying system does the work of creating the new directory, copying the data and letting the rest of the artists know that there are new assets to be pulled into their scene as well.
Then there are backups. Again this is company dependent. Some places rely on hardware to figure it out. As in, they have a huge single isilon cluster, and they hook up the nearline and tape system to it and say: every hour sync changes to the nearline. every night, stream those to tape.
Others have wrapped /bin/rm to make sure that it just moves the directory, rather than actually deletes things.
Some companies have a massive nearline system that does a moving window type sync, so you have a 12 hourlys, 7 dailies and 1 monthly online at once. The rest is on tape. The bigger the company, the more often the fuckup, the better the backups are tested.
Your standard "shot" will contain 10s or hundreds of versions of animation, lighting, texturing, modelling & lighting. Not to mentions compositing. They are often interdependent too.
A movie like shrek will have literal billions of versions of $things.
> Does anybody knows how that works?
This changes by company, but everyone tends to have an asset database. This is a thing that (should) give a UUID to each thing an artist is working on, and a unique location where it lives (that was/is an NFS file share, although covid might have changed that with WFH)
Where it differs from git et al is normally the folder tree is navigable by humans as well so the path for your "asset" will looks something like this:
/share/showname/shot_number/lighting/v33/
There are caveats, something like a model of a car, or anything else that gets re-used is put somewhere else in the "showname" folder.
Now, this is all very well, but how do artists(yes real non linux savvy artists) navigate and use this?
Thats where the "Pipeline" comes it. They will make use of the python API of the main programs that are used on the show. So when the coordinator assigns a shot to an artist, the artist presses a button saying "load shot" and the API will pull the correct paths, notify the coordination system (something like ftrack or shotgun) and open up the software they normally use (maya, zbrush, mari, nuke, etc etc) with the shot loaded.
Once the artist is happy, they'll hit publish.
The underlying system does the work of creating the new directory, copying the data and letting the rest of the artists know that there are new assets to be pulled into their scene as well.
Then there are backups. Again this is company dependent. Some places rely on hardware to figure it out. As in, they have a huge single isilon cluster, and they hook up the nearline and tape system to it and say: every hour sync changes to the nearline. every night, stream those to tape.
Others have wrapped /bin/rm to make sure that it just moves the directory, rather than actually deletes things.
Some companies have a massive nearline system that does a moving window type sync, so you have a 12 hourlys, 7 dailies and 1 monthly online at once. The rest is on tape. The bigger the company, the more often the fuckup, the better the backups are tested.