KhronosGroup / KhronosGroup/DataFormat
How to describe interleaved planes?
- Dominant language
- C
- Stars
- 43
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Section 3.2 explains how formats such as Y'CbCr 4:2:0 are described with _two_ Y' planes under the specification (when other conventional APIs would only use one Y' plane). Table 96 contains an example descriptor for this format.
However, I don't see any way to make the difference between two consecutive planes and two interleaved planes. Section 3.2 uses per-plane byte offsets and strides to denote the difference, but I don't see these reflected anywhere in the descriptor in table 96?
Is the expectation that there is no way to make the difference in general? Or, as the following note explains, is the expectation that descriptors may reflect interleaved planes via the fourth sample coordinate, but this isn't mandatory?
> One suggested convention for interlaced data is that the field of a sample be encoded in the fourth sample coordinate (the first field as samplePosition3 = 0, the second field as samplePosition3 = 1, etc.)
Or, am I missing something else?
Contributor guide
No contributing guide indexed for this repository
Research direction
Read Section 3.2, Table 96, and the note about encoding interlaced data in the fourth sample coordinate. Determine how the specification distinguishes consecutive from interleaved planes, or identify the documentation decision needed; done means the descriptor behavior is explicitly clarified.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100