AcademySoftwareFoundation / AcademySoftwareFoundation/OpenImageIO

iv: tolerate/display partially-written exr files (originally #1191).

Open
#4,713 1 comment 0 reactions 0 assignees View on GitHub
devdays difficulty/easy good first issue help wanted iv
Dominant language
C++
Stars
2.4k
Forks
698
Avg merge
3d 4h
Merged PRs (30d)
47

Description

The idea is to make sure that iv can accept a partial file, meaning: one that opens, but some scanlines/tiles succeed when read and others fail, it should be tolerant of this, and optionally may want a display mode where it's clear which tiles are missing versus black.

The iv side is probably straightforward. The question is how many things you'll bump into upstream (in ImageBuf? ImageCache? ImageInput? OpenEXR's ImageInput implementation?) that might stand in your way and need some adjustment to tolerate the missing parts of the file. Those will need to get fixed.

Contributor guide

Open the contributing guide

Research direction

Start with iv and trace partial-read handling through ImageBuf, ImageCache, and ImageInput, including the OpenEXR ImageInput implementation named in the issue. Determine which layers reject missing scanlines or tiles and whether a display mode should distinguish missing tiles from black pixels. Done means partially written EXR files open and render available data without failure, with any agreed missing-tile indication covered by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
computer-graphics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.