- pioverfour changed review status to Awaiting Review
- 3 mo
Instead of having a globally-defined scene resolution, this add-on allows you to set a resolution for each camera. Whenever you switch cameras, either manually or through timeline markers, the scene resolution will get updated to the camera’s.
You can find the camera resolution settings in the Object Data properties, under the Camera panel.
Animating the resolution is not supported by default in Blender, and
regular animation rendering will only use the resolution at render
start.
This add-on provides a new Render Animated Resolution operator which
works around this limitation. Note however that starting a render this
way will lock the interface until the render is complete, or until
Blender is killed.
In addition to providing direct controls for each camera’s resolution,
this add-on allows you to create a new camera by setting a render
border inside the camera view in the 3D viewport (Ctrl + B), and
clicking Bake Render Border in the Custom Resolution panel.
A new camera is created, which uses the exact area defined by the
border. This allows you to select multiple cropped areas in a camera.
This add-on uses a workaround to animate the camera resolution, which can sometimes cause stability issues. If you encounter such issues, try disabling the add-on.
The add-on is currently available in English and French. If you’d like to help translate it to your language, please open an issue.
This extension does not require special permissions.
Hi Damien! Handy stuff.
Couple of things before we approve:
Hi Nika, thanks :)
You're right about third one yes. Just warning for those who already know what depsgraph update is.
I added the Camera tag and a warning paragraph, let me know if it’s enough!
Thanks!
uploaded new version: 2.2.1
uploaded new version: 2.2.2
uploaded new version: Add-on "Per-Camera Resolution" v2.2.3
Hey everyone,
Just a heads-up about a recent change regarding the licensing of add-ons on the Blender extension platform. Moving forward, all add-ons will need to be released under the GNU/GPL 3.0 license (SPDX:GPL-3.0-or-later). This is mainly to keep things simple and consistent across the board.
Previously, we accepted various licenses as long as they were compatible with Blender’s distribution. However, to avoid any confusion and streamline the process, all add-ons using the bpy API should now be presented as GPL 3 (the same license the Blender bundle is distributed). Regardless of whether the original code was under GPL 2, or something else like MIT or ZLIB.
Existing add-ons versions won't be affected. However, new updates will need to comply to the revised requirements.
Thanks for understanding, and feel free to reach out if you have any questions.
Sign in to comment.
Ready for review