you can overscan with datawindowNDC it is very simple, the first two values have to go below 0 and the second two will go above 1 for example {-0.95, -0.95, 1.05, 1.05} will generate 10% overscan, however i believe this does not show in the viewport or in mplay, and also per default will not display right away in nuke. reason is that karma renders and writes the overscanned pixels into the exr file but still sets the render resolution, which sets the pixel area in exr that nuke reads (sorry for the vague explanation here all of those things have names but i have a hard time remembering). So in nuke you need to tell it to read outside the defined area and you will see that the overscan has been rendered. this is actually the intented exr workflow as far as i remember from the exr docs.
regearding render region, this is a little bit hidden, you do have render region in two places actually. The first one is if you go to image view instead of using perpective view in the viewport, just click top right on perp > Set View > Image in image view just start the render and press space + h, for some reason the focus is always somewhere else, and by alt + left click and drag und can just drag a render region, you can get rid of the region by alt + doubleclick outside the region the other way is staying in perspective view, and click on the camera icon left in you tool bar, you will notice that on the top bar of your viewport you will have an icon that looks like a camera and next to it one looks a bit like a plane, the camera icon is called 3D camera the plane is called 2D Pan & Zoom, now when you click on 2D pan & zoom and press left shift + left click and drag you can drag a render region in the viewport. same as in the image view by left shift + double click outside the region you can get rid of the region again. Just make sure to click on the 3D camera icon again once you are done with test renders as the 2D mode does not let you tumble around in your scene
Would love to see the "Date Window NDC" labelled as "Overscan" and with changeable menu of "Pixels" or "Percentage" with input of Top, Right, Bottom, Left... That simple.
These kind of things makes me hate karma, I've been using mantra for more than a decade now and its so much better except that its slower. Karma is not production ready as of today no matter what Sidefx say. Rendering a region was a matter of just draging over the render view, now we dont even have the render view.
it's better in 19.5 I feel like it's gonna be an amazing production renderer in H20, especially if XPU gonna be production ready too. But that mouse render region control in mantra was awesome for sure
Thank you Nine Between and Sidefx. I would love to see more collaborations like this.
This series is 'Karma is not scary' ! Good explanation
Great series. You explained everything very well and I appreciate the time and effort you spent to figure this stuff for us. :)
you can overscan with datawindowNDC it is very simple, the first two values have to go below 0 and the second two will go above 1
for example
{-0.95, -0.95, 1.05, 1.05} will generate 10% overscan, however i believe this does not show in the viewport or in mplay, and also per default will not display right away in nuke.
reason is that karma renders and writes the overscanned pixels into the exr file but still sets the render resolution, which sets the pixel area in exr that nuke reads (sorry for the vague explanation here all of those things have names but i have a hard time remembering).
So in nuke you need to tell it to read outside the defined area and you will see that the overscan has been rendered.
this is actually the intented exr workflow as far as i remember from the exr docs.
sorry quick correction the values have to be {-0.05, -0.05, 1.05, 1.05}
Thank you for this series of tutorial :)
regearding render region, this is a little bit hidden, you do have render region in two places actually.
The first one is if you go to image view instead of using perpective view in the viewport, just click top right on perp > Set View > Image
in image view just start the render and press space + h, for some reason the focus is always somewhere else, and by alt + left click and drag und can just drag a render region, you can get rid of the region by alt + doubleclick outside the region
the other way is staying in perspective view, and click on the camera icon left in you tool bar, you will notice that on the top bar of your viewport you will have an icon that looks like a camera and next to it one looks a bit like a plane, the camera icon is called 3D camera the plane is called 2D Pan & Zoom, now when you click on 2D pan & zoom and press left shift + left click and drag you can drag a render region in the viewport.
same as in the image view by left shift + double click outside the region you can get rid of the region again.
Just make sure to click on the 3D camera icon again once you are done with test renders as the 2D mode does not let you tumble around in your scene
Thank you for sharing. The series is awesome !
Would love to see the "Date Window NDC" labelled as "Overscan" and with changeable menu of "Pixels" or "Percentage" with input of Top, Right, Bottom, Left... That simple.
Great series, thank you!
Thanks for sharing. Very informative.
Anyone knows how to change the deep compression rate like on the mantra node?
感觉必须和渲染尺寸一样大才行，我有试过改，但是报错了.
Do DCM render with Deniose ?
In mantra there is a matte option how do I use that in karma
use Render Geometry Settings LOP, it has Render Visibility and Is Matte properties
These kind of things makes me hate karma, I've been using mantra for more than a decade now and its so much better except that its slower. Karma is not production ready as of today no matter what Sidefx say. Rendering a region was a matter of just draging over the render view, now we dont even have the render view.
it's better in 19.5
I feel like it's gonna be an amazing production renderer in H20, especially if XPU gonna be production ready too. But that mouse render region control in mantra was awesome for sure