← All ideas
  • Published 28 Mar 2024

Improved render output filename 📂

There's this limitation in Blender that is so frustrating, and it has to do with saving your renders. You simply CANT save your render in an organized manner, you may think I'm wrong cause you render your files in a very organized manner but let me prove you wrong.

🔸 Currently in Blender

If you ever rendered more than one image, say a castle 🏰, you had theses 3 views you liked, for each of them a different camera, you bound each camera to a frame and just rendered 3 frames as a sequence and you put in the output "castle_#" Then the renders files you get are castle_1/castle_2/castle_3. Then you manually renamed the renders to castle_front/castle_side/castle_top. It's manual work but it's not a big hassle.

Now if you have 100 different views, different scenes different viewlayers, you start to do this huge frankenstein setup for your renders with file output nodes in the compositor, do different scenes but it's all cumbersome, and you're limited you can't make it automatic no matter what, it's PAIN for managing renders in production.

🔸 Actual proposal

Why instead of "castle_#" where the # is the frame number, you would write "castle_<camera>" ? Then you render your sequence and it's just 3 images with no frame number! This feature exist in other 3D softwares but in blender for some reason it doesn't.

Data that the output could support : [camera] [scene] [viewlayer] [focal_length] [sensor_size] [date] [marker] and other data

Think of the possibilities you could include the date in the render automatically it sounds useless but in production it's insanely useful, I know there's metadata but it's not the same.

100%

Development Status: Open

Upvote 5 Downvote 0
costa
28 Mar 2024

1 Comment

Lauloque

Hi, there are already a few proposals in the same lines:

You can use Oscurat Tool's render tokens addon that gives some of that.
There's also the Blender Loom addon that adds such a system.

2