Path Maker
The "Path Maker" add-on allows you to write tags in some output paths. Tags will be replace at render time by a string generated with a line of code, a python script or an hardcoded string.
It supports:
- The "Output Path" in the output properties panels
- The "Base Path" in the file output compositor nodes
- The "filepath" in the collection exporters (you'll have to use the Path Maker buttons to make it work though)
For example: The tag <scene> can be replace by "bpy.path.display_name_from_filepath(bpy.data.filepath)" so that an Output Path like "C:/hello/<scene>/world" will now be "C:/hello/file_name/world".
What's New
1.2.1 July 16th, 2024
Fix minor issues from last version
Probably the site will mess-up this extract of the Blender log, making it almost unreadable...
The point is that PathMaker is a great idea, very usefull in professinal production, but somehow it doesn't work as expected. Unfortunately this page and this site is not the best option for bug report and communications between users and the author. For instance, I can't even edit this comment once posted. Thus, I'll give all 5 star to this product, because I believe in its potential. But at present it's not working as intended. At least not on my Blender 4.2.
I hope the author, Thornydre, will aknowledge this comment, in order to fix the issue.
------ HERE FOLLOWS THE ERROR LOG ------ (I hope this "smart" thing will not interfere with my formatting choice, but I'm sure it will!)
Traceback (most recent call last): File "/home/user/.config/blender/4.2/extensions/blender_org/blender_path_maker/init.py", line 264, in makePathHandler replacements_dict = generateReplacements() ^^^^^^^^^^^^^^^^^^^^^^ File "/home/user/.config/blender/4.2/extensions/blender_org/blender_path_maker/init.py", line 303, in generateReplacements replacements_dict[replacement.replacement_name] = eval(replacement.script) ^^^^^^^^^^^^^^^^^^^^^^^^ File "<string>", line 1, in <module>
Love the idea, perfect tool for pipelines. But...
I have multiple tags configured, such as: <scene> EXPRESSION bpy.context.scene.name <camera> EXPRESSION bpy.context.scene.camera.name <render> PATH RENDER_FILES <linetest> PATH LINETEST
If I use the following filename pattern: //<render>/<linetest>/<scene>_<camera>.#.
I get this result (with unresolved tags): <render>/LINETEST/<scene>_<camera>.#.
In other words, only the last tag, in this case <linetest>, gets resolved.
If I change the order in the Preferences' list, I always get the same result: only the last tag.
Not sure what I've made wrong.
While the idea is great, the documentation is very lacking and only ones tag get's resolved.