Giter Site home page Giter Site logo

jeinselen / vf-blenderautosaverender Goto Github PK

View Code? Open in Web Editor NEW
69.0 5.0 6.0 1.82 MB

Automatically saves a numbered or dated image after every render and can extend the Blender output path with dynamic variables.

License: GNU General Public License v3.0

Python 100.00%
automated blender blender-3d blender-addon blender-plugin blender3d file-name naming naming-conventions render

vf-blenderautosaverender's People

Contributors

jeinselen avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

vf-blenderautosaverender's Issues

Can use the File Output in the Compositing to save the file?

This plugin can only save the format files in the Output Panel , Can use the File Output in the Compositing to save the file?
I am now using another plugin that automatically names according to the rendering time. It can output multi-layer exr files, but its naming method is too simple and does not have the flexibility of your plugin. Can you combine the advantages of the two plugins?

Here is the link to that plugin:https://gist.github.com/robertguetzkow/8dacd4b565538d657b72efcaf0afe07e

Doesnt seem to be working -3.6.2

Hello,

I have installed the addon, followed all of the instructions and read the documentation. It loads up fine but does not seem to be able to read the tokens at all. I end up with {project}_{camera}_0001.png in a folder named {project} for example.

Am i doing something really stupid, or does the addon not work on newer versions of Blender?

Disable standard file Output

Ciao John,
thank you for developing this tool which is working like a charm.
On the compositor side everything is really working as expected, but I have a minor issue on the standard Output panel. In our pipeline we only need the files coming out from the compositor and I am trying to find a way not to render the default file Output.
If I leave the Output field completely blank when I render an animation Blender only renders the first frame and then stops.
As a workaround I tried to render the frames from the Output render in a tmp folder without any frame padding so every frame coming from the standard Output is overwritten as those are not useful to me (while the renders from the compositor are executed correctly). Unfortunately the frame padding is always automatically added no matter what is the file name that I set.
Examples:
test is rendered as test0001 and so on
test.0001 is rendered as test.00010001 and so on
test.0001.png is rendered as test.0001.png0001 and so on
Really hope the issue is clear.
Thx Claudio

Render Variables does not work if compositing tab "file output" node is in a nodegroup

As mentioned, I detected this bug and it will work again after ungroup the nodegroup in the compositing tab.

I use the VF_autosaveRender ver2.7.4 with blender3.6.2LTS
but this problem has always existed in previous versions

Pack compositing nodes into groups for easy import into different projects, it's a habit that improves work efficiency.
So other users may encounter similar issues.
I just want to report this tiny bug to make the addon even better, even though it already is!

Override path for existing .blend files

One of the big benefits to me from this addon is the ability to save every render to one location without having to worry about it-- the problem is that I have TONS of older blend files where opening them defaults to the project folder for saving.

It would be ideal if there were a way to override the path to always be one location, so that any and all renders save their images there. I would much rather dig through a render folder for the image I need than dig through my entire file server looking for a particular image.

Feature request: Color management identifiers

I love this addon. It would be great if it included color management identifiers (ie "View Transform") in the list of options. I specifically do render tests comparing Filmic and AGX and it would be nice if I was able to have that noted in filenames for when I check back on a render several months later.

Additionally, being able to identify the "Look" (ie. High contrast, low contrast...) would also be amazing.

Example:

--{viewtransform}--{look}--

--AgX--HighContrast--
--Filmic--BaseContrast--

Thank you for your consideration.

filename output

Hi!

Great addon! been looking for an addon like this for a while!

If I could make one request is that i would like to see the file naming options in de side tab of the compositor just like in the output properties tab.

Kind regards,
Benno

Viewport Render Animation breaks {serial} tag

If you set Output to "//Output\test {serial}/" and render Viewport Animation, it'll fail to create a folder with appropriate number
image

Also Is it possible to auto-save viewport renders too?

Possibity to save rander images in unsaved file. (Enhancement)

Hi, Thank you for creating this wonderful add-on.

Often times I just want to test out random 3d models in different light environments. And there are also other scenarios where I don't want to save blender file, but just do some quick renders for practice.

So, I would like to ask if is it possible to save render images of unsaved blender file? I am not concerned with file naming conventions. The only thing i care about is to not override image file that already exists in that location.

Additional compositor output nodes

Good morning John,
I am testing your VF-BlenderAutosaveRender and is pretty amazing. Is super stable and everything is working like a charm but I was wondering if there may be any cache to add additional compositor output nodes. Our blender pipeline is based on four compositor output nodes that render separate exr sequences for Beauty, Passes, Data and Cryptomatte. Right now artists should manually update all the output paths manually every-time they update the script to a new version which is highly risky as human errors may always occur.
Hope to hear from you soon.
Best
Claudio Falconi
VFX supervisor ProximaMilano

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.