File organization for animated short film?

[potus98]

Interested in your feedback, warnings or better ideas about how I’m laying out my .blend files for a short film. The film needs 4 sets, 5 characters, various props and a small boat. The film will probably have around 100 shots.

My goal is to rough out the sets and characters while making my animatics. Then gradually refine the details while fine tuning each shot. For example; one set might need some rocks on the ground, but I’ll start with stand-in cubes while I focus on character animation. Once I’m satisfied with the timing of a character jumping over the “rocks”, I’ll replace the stand-in cubes with basic rock models. Same for trees, furniture, etc. Start off with primitive stand-ins, but refine over time.

Planning to use a separate blend file for each set. For example; the opening scene in the dungeon cave would include the cave tunnel, rocks, spider webs, and torches along the wall.

Each shot would have its own blend file. Using 2.81, this file would include links to the set, characters and props needed for the scene. Animation posing, camera and lights would be local to each shot file.

A blend file for each character with rigging.

A blend file for all props. Granted, a character’s backpack is likely to be modeled as part of the character itself, but the treasure chest found by the heroes may be its own prop since it’s dragged from scene to scene.

With this approach, I think I can refine the stand-in cubes into nice rocks in one place: the blend file for that particular set, then re-render any shots with the rocks in view.

I’ve tested this approach with 1 set, 1 character and a few shots and it seems supported in 2.81, but I’m not sure if I’ll run into problems when importing across many files. Am I creating a future nightmare by using a seperate blend file for each shot? Other pitfalls?

If this is the wrong forum, please recommend alternative for workflow questions. Thx!

[sozap]

That’s sound pretty solid and in the lines of how things should be done !

I’ll start with stand-in cubes while I focus on character animation. Once I’m satisfied with the timing of a character jumping over the “rocks”, I’ll replace the stand-in cubes with basic rock models.

Just in case, but I’m sure you’ve figured out : This stage is called Layout , you must stick to very basic animation to get the timing and framing right. Don’t push animation until you get the final set (especially for interactions between characters and sets) .

A blend file for all props

You can do that, generally on collaborative projects 1 file per props is more easy to manage, but if you’re alone that’s not that much of a difference. All in the same .blend allow you to share materials and prevent props having wrong scale at least .

Each shot would have its own blend file. Using 2.81, this file would include links to the set, characters and props needed for the scene. Animation posing, camera and lights would be local to each shot file.

You can link collections of lights just like set or props, this way you can tweak globally the lighting without having to copy-paste over all the shots. Latter you can make them local to fine tune them on a per shot basis.
You can also use “Light in assets” when that makes sense as stated here : https://www.expandedcinematography.com/industrialised-cinematography.html#how

One thing that you may consider is , is it really worth to have one .blend per shot ?
In fact it’s how it’s generally done, but you’ll have to make a lot of back and forth and re-rendering between your 100 files.
You can group shots bettween 1 to ~10 shots and use stuff like “bind camera to markers” when that makes sense. At least as long as your are on the Layout phase. Latter you can split them into individual shots for final animation and lighting. That will give you names like SHOT_045A_V010.blend, SHOT_045B_V010.blend…

but I’m not sure if I’ll run into problems when importing across many files

I don’t see what the issues could be ?
One thing that’s good to know is some nasty defaults in blender.
Let’s say you’ve animated or added a linked props in a shot_01. Now you need to propagate that to shot 02. One good solution is to append the linked object and his proxy from 01 to 02.
But keep sure that at appending time Localize All is uncheck, or it will make all the appended stuff local and you won’t be able to change the props and have the result propagated to all shots that’s using it.

If it’s uncheck it will do basically what you need, you will be able to animate the props in shot_02, and if
for instance you tweak the props’s material eveything should propagate nicely to both shots.

A last bit of advice, starting by blocking models , make shots and refine assets is a clever way to go.
The only thing I would try to iron out from the start is the character rig. You can always add bones during production and let the changes propagates in the shots, but there are some settings that can be lost in the process. Bones settings like Rotation order, or some constraints can be hard to get back in the shots you’ve already made.

So all in all you’re good to go, feel free to poke me if you have other questions and I’ll make my best to answer them.

[potus98]

Thank you for all of the great feedback and information. I do have a follow-up question about propagation further below.

Having only used single .blend files in the past, moving into a project with many interlocking blend files is new. As a part time python developer, the approach seems intuitive, but I just don’t know how well the concepts of libraries, configuration files, etc. translate into a Blender animation project. Hearing from others is so helpful!

You can link collections of lights just like set or props, this way you can tweak globally the lighting without having to copy-paste over all the shots. Latter you can make them local to fine tune them on a per shot basis.

I had not considered the idea that of starting out with linked collections then making them local towards the end of the project for final tuning. This sounds like the best of both worlds. I guess the trick is learning to wait as late as possible before making an asset local. I could imaging being in the final tweaking stages only to discover “one last global change” I’d like to make.

You can also use “Light in assets” when that makes sense as stated here : https://www.expandedcinematography.com/industrialised-cinematography.html#how

That article provides an excellent insight into the workflow methods and mindsets used on a large scale project. Just seeing how other teams arrange their assets and workflows is super helpful regardless of what specific tools they’re using.

You can group shots bettween 1 to ~10 shots and use stuff like “bind camera to markers” when that makes sense.

Ah ha! I wasn’t familiar with “bind camera to markers” but a quick Google suggests this would be very helpful. There are some scenes where I could animate a sequence, setup 3-4 cameras to catch the different shots/angles needed, and do it all in one .blend file. This seems like a more natural approach.

And again, splitting out the shots towards the end for final lighting also sounds like a good idea.

Let’s say you’ve animated or added a linked props in a shot_01. Now you need to propagate that to shot 02. One good solution is to append the linked object and his proxy from 01 to 02.

Ooooh! I didn’t think about that. So, an asset like the treasure chest could be modeled in the props file, then locally modified in shot 03 to have the lid opened, then shot 04 could link to the opened treasure chest from shot 03?

It sounds like this would allow a refinement in the original prop file to propagate through all shots with the treasure chest. For example, the original prop file is updated to add metal rivets to the chest. Those rivets would then be present in all shots with the chest. THEN, if shot 03 is tweaked so the chest lid opens wider than originally animated, the wider opened lid is propagated to shot 04 automatically.

Am I understanding this propagation correctly?

The only thing I would try to iron out from the start is the character rig. You can always add bones during production and let the changes propagates in the shots, but there are some settings that can be lost in the process. Bones settings like Rotation order, or some constraints can be hard to get back in the shots you’ve already made.

Exactly the kind of experienced tips I was hoping to learn. I’m sure I’ll find plenty of pitfalls, but maybe this one can be avoided. Thanks!

[sozap]

I had not considered the idea that of starting out with linked collections then making them local towards the end of the project for final tuning. This sounds like the best of both worlds. I guess the trick is learning to wait as late as possible before making an asset local. I could imaging being in the final tweaking stages only to discover “one last global change” I’d like to make.

Most of the time if things are done correctly you don’t need to localize things that much, but it’s best to do it as latter as you can. It will be simpler once you’ll be in the creative process to see what broad changes you need to make.

If you do some python you can do some basic scripting to re-render automatically stuff that as changed , the faster you can see change in context with all the shots next to each other, the best it will be.

Ooooh! I didn’t think about that. So, an asset like the treasure chest could be modeled in the props file, then locally modified in shot 03 to have the lid opened, then shot 04 could link to the opened treasure chest from shot 03?

You can do that, but that’s a bit dangerous… If you rename shot files (like if you split your sequences into shots) you’ll loose the links.
Basically , all props needs some simple rigs to be animated or posed. The workflow is like this :

• In the shot 03 you link the collection “Treasure” that contain all the object and the rig, from the props file.
• You make a Proxy of the rig, (in blender terms that means that you make the rig semi-local but everything else stay linked) .
• You can then open the chest, put it in the right place or animate it.
• Now instead of re-doing all this for the shot 04, you just need to append the chest and his rig from shot 03 , with Localize All deselected.
• In the shot 04 you can change the animation , or do whatever you need , just like in the shot 03. It will link stuff from the original props file instead of the shot 03, but it will append the animation and all the changes you’ve made in the shot 03.

You should look for instancing collection and proxy in video like this : https://www.youtube.com/watch?v=nHscyEeyHa4

You can go crazy and link the animation from shot 03 into shot 04 so you just need to change things in shot 03 , but in practice that’s better to avoid that. At some point you’ll loose track of were you need to change things. It’s better to look at the edit and change things on needed shot directly.

I guess it’s one of the downside of working in iteration with basic things first then refine, you spend many times opening files , do some tweaking , re-render , look at the final result and repeat…
In the end you may have some little python scripts to automate that process, but you’ll see as you go, it’s not good to over-plan stuff.