Page MenuHome

Proposal: Animated Render Border Attributes
Closed, InvalidPublic

Description

While developing this Add-on to extend the Render Border functionality, I noticed that Blender checks the render border attributes (min x, max x, min y, max y) only once per render execution. By the help of the linked Add-on, animating the values is working fine in the Viewport and also when rendering a single frame (http://i.stack.imgur.com/tCoxp.gif), but unfortunately this isn't working for rendering animations at the moment. It seems that blender is using the current viewport render border attributes for each frame, although the render border scene attributes are driven correctly by the add-on values:


I have no idea about how difficult this is to implement, but what about updating render border attributes for every frame while rendering animations? Or allowing to animate the render border attibutes in the outliner at least? If this is an easy task, it could rapidly improve render workflows and finally speed up the rendering process.

For Add-ons we can use python handlers to overwrite the scene attributes (of course), but wouldn't it be nice (also for upcoming projects) to check this attributes by default for every frame?

Details

Type
Design

Event Timeline

Aaron Carlisle (Blendify) changed Type from Bug to Design.
Aaron Carlisle (Blendify) raised the priority of this task from Normal to Needs Triage by Developer.
Dalai Felinto (dfelinto) closed this task as Invalid.
Dalai Felinto (dfelinto) claimed this task.

Design tasks are reserved for developers willing to implement a feature. This is not the case. It's a feature request in fact, which we don't accept in the bug tracker even though that is a nice feature request (along side with "multi-border" render). That said, Blender read those values at render init to prevent crashes coming from users change the data (e.g., render border) while rendering is happening.

Thanks @Dalai Felinto (dfelinto). I posted that as a proposal, because I wasn't sure whether someone else noticed that behavior - realized later that something like this is bad practice. I'm sorry.