hi, setting the pixel aspect ratio as 2 in H19.5.303 sets the viewport correctly but the Mplay render is still at 1. I couldnt test disk renders since it doesnt write anything to disk and I need to further investigate.

Is this a bug or is there something I should do for disk and MPLAY renders?

Karma ROP in out context, or usdrender LOP node? I think there's a bug in resolution on the ROP that should be fixed in the current daily build.

jsmack
Karma ROP in out context, or usdrender LOP node? I think there's a bug in resolution on the ROP that should be fixed in the current daily build.

The USDrender LOP and also the same for the Karma ROP.

AhmedHindy

jsmack
Karma ROP in out context, or usdrender LOP node? I think there's a bug in resolution on the ROP that should be fixed in the current daily build.

The USDrender LOP and also the same for the Karma ROP.

Hmm, well it works fine for me.

so my steps are:

1. establish the correct rendered exr image with Mantra and pixel aspect ratio of "2" on the camera OBJ node and with the BG Plate.
2. import the camera with sceneImport LOP.
3. add a background plate that is of aspect ratio of 2 in Solaris and set resolution to "manual" with correct resolution.
4. set the pixel aspect ration to "2" on the render product prim for Karma and change conform policy to "adjust pixel aspect ratio".
5. render in viewport with hydra will make the background stretchy (correct) but the added explosion looks squished vertically.
6. rendering to Mplay wont display the BG Plate and there wont be a "2:1" aspect ratio indicator in the top left of MPLAY to indicate it rendered correctly like in Mantra.

Instead of "Adjust Pixel Aspect Ratio", what if you use "Crop Aperture"?

I experimented alot and found the solution:

- use "crop aperture" or "adjust aperture height" on the "conform policy" in step 4 in my previous comment instead of "adjust pixel aspect ratio"

robp_sidefx
Instead of "Adjust Pixel Aspect Ratio", what if you use "Crop Aperture"?

man I wish I saw your comment earlier, I am glad that there are two options that give the same correct results.
Hope this helps someone in the future.

AhmedHindy


I experimented alot and found the solution:

- use "crop aperture" or "adjust aperture height" on the "conform policy" in step 4 in my previous comment instead of "adjust pixel aspect ratio"

robp_sidefx
Instead of "Adjust Pixel Aspect Ratio", what if you use "Crop Aperture"?

man I wish I saw your comment earlier, I am glad that there are two options that give the same correct results.
Hope this helps someone in the future.

I wonder if your camera is being imported with the wrong backplate size. If the camera backplate aspect ratio matches the rendered screen size, the aspect ratio conform policy shouldn't have any effect on the render. (I think it still confuses things in the scene viewer even when they do match though)

jsmack
I wonder if your camera is being imported with the wrong backplate size. If the camera backplate aspect ratio matches the rendered screen size, the aspect ratio conform policy shouldn't have any effect on the render. (I think it still confuses things in the scene viewer even when they do match though)

not sure what you mean but the camera is on the OBJ level and I plugged the backplate there and set pixel aspect ratio to 2 and it works perfectly with Mantra and that's it.

I used scene import camera LOP to get it to Solaris and a backgroundplate LOPto simply add it. The shot was a simple explosion and it wasn't placed correctly + it was squished or squashed with different settings.

conform policy set to "Crop Aperture" saved the day