Set Render Border Add-on #47267

New Issue

Christian Brinkmann · 2016-01-28T18:58:42+01:00

Christian Brinkmann commented

2016-01-28 18:58:42 +01:00

This tiny Add-on allows to set the Render Border in Camera View (pixel based):

(X) Set pixel distance between the left edge of the camera border and the left side of the render border
(R) Set Pixel distance between the right edge of the camera border and the right side of the render border
(Y) Set Pixel distance between the bottom edge of the camera border and the bottom edge of the render border
(T) Set pixel distance between the top edge of the camera border and the top edge of the render border
(Center X) Set horizontal center of the render border
(Center Y) Set vertical center of the render border
View render border dimensions
Animate the properties

Repository
https://github.com/p2or/blender-renderborder

Demo
http://blender.stackexchange.com/a/45837/3710

py-file:
render-border.py

This tiny Add-on allows to set the *Render Border* in *Camera View* (pixel based): ![Screenshot.png](https://archive.blender.org/developer/F278128/Screenshot.png) - (X) Set pixel distance between the left edge of the camera border and the left side of the render border - (R) Set Pixel distance between the right edge of the camera border and the right side of the render border - (Y) Set Pixel distance between the bottom edge of the camera border and the bottom edge of the render border - (T) Set pixel distance between the top edge of the camera border and the top edge of the render border - (Center X) Set horizontal center of the render border - (Center Y) Set vertical center of the render border - View render border dimensions - Animate the properties **Repository** https://github.com/p2or/blender-renderborder **Demo** http://blender.stackexchange.com/a/45837/3710 **py-file**: [render-border.py](https://archive.blender.org/developer/F278123/render-border.py)

Christian Brinkmann commented

2016-01-28 18:58:42 +01:00

Changed status to: 'Open'

Christian Brinkmann commented

2016-01-28 18:58:42 +01:00

Added subscriber: @p2or

Campbell Barton commented

2016-02-02 10:36:02 +01:00

Added subscriber: @ideasman42

Campbell Barton commented

2016-02-02 10:36:02 +01:00

Hi, we're wondering why would would want to do this?

If you do some operation that requires precision (splitting the render into exact tiles for eg), you would be best to use Python for this anyway (or have an add-on that handles splitting the render into tiles), so having the UI doesn't really help.

Can you give some use cases for this add-on?

Hi, we're wondering why would would want to do this? If you do some operation that requires precision (splitting the render into exact tiles for eg), you would be best to use Python for this anyway (or have an add-on that handles splitting the render into tiles), so having the UI doesn't really help. Can you give some use cases for this add-on?

Christian Brinkmann commented

2016-02-02 16:42:48 +01:00

Hi Campbell,

thanks for your reply. You are right, use cases are missing in my description, I'm sorry.

To optimize render times I'm using cycles' render border feature for preview purposes, quick renderings or even final renderings (mainly to integrate CG in live action footage) very frequently. It's a real time saver, but what I've noticed is that it's cumbersome to set up:

Using Ctrl+B to drag out the 'crop box' is very inaccurate and causes that the user is doing this 3-10 times to get the desired area (depends on the user of course)
Adjusting the render border via Outliner > Datablocks (afterwards) to (re-) render an area is almost impossible for unexpierenced users and could lead in frustration (observed my highly experienced Softimage co-worker). There are 2 main issues:

Finding the property in the Outliner takes 1-3 minutes
In some situations it's required to calculate the pixel values from the given 'linear range', which takes another 5-10 minutes

The real advantage of the Add-on (IMO) is working with pixel values instead of the 'linear range', which is more intuitve/usual to work with. Regarding to the final image the Add-on provides full control setting up the box and the user gets instant feedback about the border position and the current/final dimensions. Basically it's very similar to Nuke's Crop Node with the ability to shift the center of the box:

Note: I don't want to waste your time, I just thought it might helps to improve the render border feature and could be useful for others, too :)

Hi Campbell, thanks for your reply. You are right, use cases are missing in my description, I'm sorry. To optimize render times I'm using cycles' render border feature for preview purposes, quick renderings or even final renderings (mainly to integrate CG in live action footage) very frequently. It's a real time saver, but what I've noticed is that it's cumbersome to set up: 1. Using Ctrl+B to drag out the 'crop box' is very inaccurate and causes that the user is doing this 3-10 times to get the desired area (depends on the user of course) 2. Adjusting the render border via *Outliner > Datablocks* (afterwards) to (re-) render an area is almost impossible for *unexpierenced users* and could lead in frustration (observed my highly experienced *Softimage* co-worker). There are 2 main issues: - Finding the property in the *Outliner* takes 1-3 minutes - In some situations it's required to calculate the pixel values from the given 'linear range', which takes another 5-10 minutes The real advantage of the Add-on (IMO) is working with pixel values instead of the 'linear range', which is more intuitve/usual to work with. Regarding to the final image the Add-on provides full control setting up the box and the user gets instant feedback about the border position and the current/final dimensions. Basically it's very similar to *Nuke's Crop Node* with the ability to shift the center of the box: ![nuke crop node.jpg](https://archive.blender.org/developer/F279602/nuke_crop_node.jpg) **Note:** I don't want to waste your time, I just thought it might helps to improve the render border feature and could be useful for others, too :)

Aaron Carlisle commented

2016-02-20 19:15:07 +01:00

Added subscriber: @Blendify

Campbell Barton commented

2016-03-07 05:35:15 +01:00

Changed status from 'Open' to: 'Archived'

Campbell Barton closed this issue

2016-03-07 05:35:15 +01:00

Campbell Barton self-assigned this 2016-03-07 05:35:15 +01:00

Campbell Barton commented

2016-03-07 05:47:06 +01:00

Changed status from 'Archived' to: 'Open'

Campbell Barton reopened this issue

2016-03-07 05:47:06 +01:00

Campbell Barton commented

2016-03-07 05:47:06 +01:00

Of course if you want to enter in pixel values, its convenient exposing the settings as pixel values. But this doesn't really answer the question.

Why would you even care or want to enter the pixel values to begin with?

Of course if you want to enter in pixel values, its convenient exposing the settings as pixel values. But this doesn't really answer the question. Why would you even care or want to enter the pixel values to begin with?

Christian Brinkmann commented

2016-03-10 11:03:49 +01:00

Thanks for the reply,

Not sure I understand your question right: It's all about control. It does not matter to begin with, but it's comfortable to adjust it accurately regarding to the output image and its pixels (mainly for compositing in my case).

May I ask, what is your point? Tile rendering?

Thanks for the reply, *Not sure I understand your question right:* It's all about control. It does not matter to begin with, but it's comfortable to adjust it accurately regarding to the output image and its pixels (mainly for compositing in my case). May I ask, what is your point? *Tile* rendering?

Campbell Barton commented

2016-03-11 02:18:54 +01:00

If this is really needed for typical workflows - we could just add this into Blender.
So it would help if you could describe what kinds of tasks exact pixel inputs are useful for.

If this is really needed for typical workflows - we could just add this into Blender. So it would help if you could describe what kinds of tasks exact pixel inputs are useful for.

Christian Brinkmann commented

2016-03-11 12:42:29 +01:00

Ok, thanks Campbell. I try to write down some advantages as soon as I can.

Campbell Barton removed their assignment 2016-08-11 06:34:51 +02:00

Brendon Murphy commented

2017-04-15 08:03:47 +02:00

Added subscriber: @BrendonMurphy

Brendon Murphy commented

2017-04-15 08:03:47 +02:00

Changed status from 'Open' to: 'Archived'

Brendon Murphy closed this issue

2017-04-15 08:03:47 +02:00

Brendon Murphy self-assigned this 2017-04-15 08:03:47 +02:00

Brendon Murphy commented

2017-04-15 08:03:47 +02:00

Archiving this task, @p2or
thanks for submission, I will reopen if this in unresolved in blender & you can demonstrate advantages.
I also wonder if there's other addons now doing similar things?
Thanks.

Archiving this task, @p2or thanks for submission, I will reopen if this in unresolved in blender & you can demonstrate advantages. I also wonder if there's other addons now doing similar things? Thanks.

Christian Brinkmann commented

2017-05-22 22:05:38 +02:00

Added subscriber: @SeanKennedy

Christian Brinkmann commented

2017-05-22 22:05:38 +02:00

Thanks for this friendly reminder @BrendonMurphy,
Sorry for the delay @ideasman42,

we are using that Add-on at work, mainly for look development. When it comes to rendering several 3d elements or replacements per shot basis, especially when integrating CG and live action, we don't like wasting time while waiting for transparent pixels, so we can't live without blender's render border. However, as said before, it's crumbersome to adjust the values without the Addon at the moment. Maybe @SeanKennedy can confirm here...?

Real-world example
Consider a shot like the one below. It's captured with an Alexa at only 3k (3200x1800px) , where a car is coming into the shot and the job is to replace the license plate. The size of the license plate isn't changing that much, it's just moving through the image. As lighting/comp artists the only thing we'd like like to preview/render is the CG part of the image (the licence plate and its shadow) instead of the whole 3k image, which is something like 300x250px in that case, against 3k. Rendering time was 1:20 against 8 minutes (without render border) on a workstation per frame. The addon allows to adjust the box exactly around the license plate and render times are significant low as well.

The real advantage of the Addon is probably the ability of shifting the center of box, once the values are set up. Also it allows to adjust the edges of the border as accurate as required, in a more intuitive way (IMO). Another thing is direct access in the camera tab, which avoids searching through the data blocks for its properties. Getting feedback on the actual size of the box in pixels is great (the user gets instant feedback about the border position and the current/final dimensions), because you'd like to know how many pixels you need to render and what exactly you are delivering to the compositor.

I still think it's a nice addition, and I really hope this is a better explanation. If you have any suggestions or in case I missed something here, please let me know. By the way: It's hard to see any progress on python viewport manipulators. Do you think we can get a custom python manipulator at the center of the box in order to move the render border box directly within the viewport?

Regarding your question @BrendonMurphy: I don't remind any render border addon, which was coming up in the last year.

Thanks guys!
Cheers,
Christian

Thanks for this friendly reminder @BrendonMurphy, Sorry for the delay @ideasman42, we are using that Add-on at work, mainly for look development. When it comes to rendering several 3d elements or replacements per shot basis, especially when integrating CG and live action, we don't like wasting time while waiting for transparent pixels, so we can't live without blender's render border. However, as said before, it's crumbersome to adjust the values without the Addon at the moment. Maybe @SeanKennedy can confirm here...? **Real-world example** Consider a shot like the one below. It's captured with an Alexa at only 3k (3200x1800px) , where a car is coming into the shot and the job is to replace the license plate. The size of the license plate isn't changing that much, it's just moving through the image. As lighting/comp artists the only thing we'd like like to preview/render is the CG part of the image (the licence plate and its shadow) instead of the whole 3k image, which is something like 300x250px in that case, against 3k. Rendering time was 1:20 against 8 minutes (without render border) on a workstation per frame. The addon allows to adjust the box exactly around the license plate and render times are significant low as well. ![real-world-example.jpg](https://archive.blender.org/developer/F606365/real-world-example.jpg) The real advantage of the Addon is probably the ability of **shifting the center of box**, once the values are set up. Also it **allows to adjust the edges of the border** as accurate as required, in a more intuitive way (IMO). Another thing is **direct access** in the camera tab, which avoids searching through the data blocks for its properties. Getting feedback on the **actual size of the box in pixels** is great (the user gets instant feedback about the border position and the current/final dimensions), because you'd like to know how many pixels you need to render and what exactly you are delivering to the compositor. I still think it's a nice addition, and I really hope this is a better explanation. If you have any suggestions or in case I missed something here, please let me know. *By the way: It's hard to see any progress on python viewport manipulators. Do you think we can get a custom python manipulator at the center of the box in order to move the render border box directly within the viewport?* *Regarding your question @BrendonMurphy: I don't remind any render border addon, which was coming up in the last year.* Thanks guys! Cheers, Christian

Ray Mairlot commented

2017-07-02 19:10:36 +02:00

Added subscriber: @RayMairlot

Ray Mairlot commented

2017-07-02 19:10:36 +02:00

@BrendonMurphy @p2or

Hi. Seeing as it was asked, I just thought I would chip in and say, yes, there is another add-on that does this (though it works on a 0-1 scale instead of pixels), my 'Animated Render Border' add-on: https://blendermarket.com/products/animated-render-border/ .

I of course appreciate some people would prefer to have the features built into blender instead of needing an external (paid-for) add-on and my add-on may be doing some things differently from what is being discussed, but I think the general functionality is the same.

The general idea was, as @p2or said, to avoid having to render pixels you know to be transparent and to be able to move the render border in unison with an animated object or group of objects to both optimise renders and to allow quick re-rendering of selected portions of an animation. Aside from just exposing the render border values, my add-on automates the animation of these values by automatically tracking animated objects or groups (which I think probably goes beyond the scope of features that could be included in blender by default).

@BrendonMurphy @p2or Hi. Seeing as it was asked, I just thought I would chip in and say, yes, there is another add-on that does this (though it works on a 0-1 scale instead of pixels), my 'Animated Render Border' add-on: https://blendermarket.com/products/animated-render-border/ . I of course appreciate some people would prefer to have the features built into blender instead of needing an external (paid-for) add-on and my add-on may be doing some things differently from what is being discussed, but I think the general functionality is the same. The general idea was, as @p2or said, to avoid having to render pixels you know to be transparent and to be able to move the render border in unison with an animated object or group of objects to both optimise renders and to allow quick re-rendering of selected portions of an animation. Aside from just exposing the render border values, my add-on automates the animation of these values by automatically tracking animated objects or groups (which I think probably goes beyond the scope of features that could be included in blender by default).

Christian Brinkmann commented

2017-07-03 10:42:57 +02:00

Thanks for joining @RayMairlot!

Rombout Versluijs commented

2018-01-12 07:24:13 +01:00

Added subscriber: @RomboutVersluijs

Rombout Versluijs commented

2018-01-12 07:24:13 +01:00

I think this is very usefull, to me it sounds like Cambel Barton doesnt see the benefit of using exact inputs. Sometimes this is very much needed. Dont understand the hammering on why this and that, he explained it very well i think.

You have much more precision control. What would be even better if there was 3dview control. I guess thats a bit more work. But there are examples like archpack is using to update items in 3dviewport. This could be an active crop tool with way more and much better control than the current ctrl+b

I think this is very usefull, to me it sounds like Cambel Barton doesnt see the benefit of using exact inputs. Sometimes this is very much needed. Dont understand the hammering on why this and that, he explained it very well i think. You have much more precision control. What would be even better if there was 3dview control. I guess thats a bit more work. But there are examples like archpack is using to update items in 3dviewport. This could be an active crop tool with way more and much better control than the current ctrl+b

Sean Kennedy commented

2018-01-15 17:13:16 +01:00

I would indeed find this very useful. For example, say I turn on border render to render out a small vfx element faster. Then I get notes on the shot, so I go and do more versions, versioning up as I go, turning off border render because maybe in these new versions the effect is different. Eventually they settle on something very similar to the first version I submitted that had been rendered with border turned on, but I'm now 10 versions later and I've moved the border to other places. My compositing setup (in Nuke) is already setup, so if I can render with the exact same border dimensions as 10 versions earlier, I can easily just drop in the new render and not have to worry about anything. That's how I'd use it most.

Sign in to join this conversation.