Page MenuHome

Different Pixel Aspect Ratio in Scenes of same Blendfile Causes Rendering Incorrect Section
Closed, ArchivedPublic

Description

System Information
Win7 GeForce 980

Blender Version
Broken: 2.73
Worked: (optional)

Short description of error
Different pixel aspect ration of scenes in same Blendfile causes error in section and render size.

Exact steps for others to reproduce the error
Create a{F156499} new scene with linked objects. Set Pixel aspect ratio to 2:1 (x:y). Divide resolution x by 2.
Go back into 1st scene, compositor. Create a new input -> renderLayer, Render.
The image of the 2nd scene is incorrect.
If you go to the 2nd scene and render, go back to the compositor in the 1st scene, the image is correct.

Event Timeline

Sergey Sharybin (sergey) lowered the priority of this task from 90 to Normal.Mar 31 2015, 2:27 PM

Compositor scene will render all the scenes with the same resolution. it might also need to use pixel aspect from the composite scene, but i'm not really sure it'll be a totally correct approach.

I want to render side by side, and the result of each "eye" will be shrinked to half resolution, so I didn't see a point in rendering it full res and shrink it, if I can use the aspect ratio to render it smaller. I guess I'll wright a script that renders the scenes one by one. Or is there a more simple approach?

EDIT: If I set the master scene to the same aspect ratio the resulting image will be too narrow, or is there a way to directly enlarge the render size after render?

You can use scale compositor node.

As for original report -- i'll check with our compositor team about making it so pixel aspect is used from the "master" scene. But apart form that you just need to be aware of blender's treatment of render settings when building your workflow.

Sergey Sharybin (sergey) triaged this task as Low priority.May 25 2015, 9:30 PM
Sergey Sharybin (sergey) changed the task status from Unknown Status to Unknown Status.Aug 27 2015, 12:48 PM

After discussion with other devs it's not really so much a bug, just something you shouldn't be exploiting. With compositor becoming canvas aware it might be possible to map such cases in a reasonable way but in any case it's not a bug.

So thanks for the report, but archiving it now.