p2or/blender-loom

File Path Variables apply automatic

gitingwar opened this issue · 5 comments

Realy nice addon, Thx!

I propose to introduce the ability to automatically save the render (F12) to the path specified using global variables.
Now path in compositor->output_node after pressing F12 leads to saving the file in C:$BLEND$CAMERA\ (OS: windows) without replacing global variables in path-string
image

I understand that you can press the button "Bake Globals" ( bpy.ops.loom.globals_bake(action='APPLY') ), but in Scene more cameras and I would like to have this function to replace global variables by default or optionally included in the settings of the scene or addon.

Blender versions: 2.92, 3.1, 3.3

Thanks! Igor

p2or commented

Hi @gitingwar,

thanks for your feedback. But the replacement works when you render using Loom (CtrlShiftF12), right? If this does not work, please let me know. In my tests, everything has worked so far.

In general I would not like to change regular operations like F12 which interfere with Blender if there is no good reason for it. I'm worried that this might confuse the user and you would have to disable the add-on in case you want to use the old regular F12 function instead of Loom. But you are right of course, there should be at least a hint or a popup appear when variables are used like in this case and an option to use Loom. If you have an idea of what this might look like, please let me know, all ideas are welcome.

Cheers,
Christian

Hi! Ctrl+Shift+F12 work correctly.
I`m about this: in standart output property insert checkbox, who enabled looms globals in all paths with F12 render
image

In our pipline has local works, local network works and network-render by local network. Globals vital for almost any scene in tuning scenes and production by net-render

p2or commented

Hi @gitingwar,

good to know this works and thanks for your quick mockup. Just to make sure I understand your request correctly:

  • The file path must be baked because you are rendering on a (custom) render farm on which Loom can not be installed? Did you already tried Loom's batch render functionality on your farm?

  • Or would you like to have the functionality on the regular hotkey because you are afraid that employees will accidentally press F12 instead of CtrlShiftF12? If so, have you already tried to map the shortcut to F12? Does that work for you?

    Screenshot 2022-11-25 at 16 16 04

Cheers,
Christian

The beauty of using global variables is not to bake any paths. My workflow for my net-render:

  1. create scene, in standart output path write path with looms globals (standart output save jpg for prev)
  2. in compositor use fileoutput (exr) with path string: $DEF_OUTPUT_PATH (variable added in Loom preferences)
  3. save net-task for my net-render (many computers in local network without phisic access). i`m added into net-render Looms globals

And yes, the idea of replacing the CTRL+F12 key is quite working.
Thanks for you time!

p2or commented

Ez, glad I could help.