OpenEXR and OpenEXR-Multilayer data inconsistencies. #45637
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#45637
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Ubuntu 14.04.2 LTS 64-bit
AMD A8-5550M APU with Radeon(tm) HD Graphics × 4
AMD Radeon HD 8550G
Blender Version
Broken: 'Blender V2.55.1 and newer' as the OpenEXR file states; yet it can be any version.
Short description of error
Case scenario: Rendering an image of X and Y size (here being 1920 x 1080 in example image).
Rendering a scene (with or without all passes enabled) yields expected results for the "dataWindow" and "displayWindow" variables.
Both are set to -> (0, 0) - (1919, 1079).
Rendering a scene with [ bpy.context.scene.render.use_border = True ] and setting the render border should yield two different results. The Variable "displayWindow" should stay exactly the same as it represents the render size of 1920 x 1080 and "dataWindow" should represent the render border region.
Data dump.
Exact steps for others to reproduce the error
1 - Setup a render border inside camera,
2 - Select OpenEXR or OpenEXR-Multilayer image formats,
3 - Render,
4 - Save render as a file.
Optional steps:
5 - Install python2 or 3 OpenEXR bindings,
6 - Dump the file header using code below:
Suplied .blend: openexr datawindow bug.blend
Changed status to: 'Open'
Added subscriber: @Genome36
Added subscriber: @kevindietrich
It appears that
Imf::Header.dataWindow()
is not set at all (at least not with the render border size). But I'm not sure how to get that info into the OpenEXR API.Added subscriber: @Sergey
Changed status from 'Open' to: 'Archived'
ImBuf in Blender is not aware of the border rendering and can't set data window. Surely it's possible to support such a feature but it's not considered a bug. Thanks for the report anyway.