2.4 KiB
HEVC conformance fixtures
These fixtures come from the electronic attachment to ITU-T H.265.1 (10/2018), the conformance specification aligned with ISO/IEC 23008-8. Table 4 identifies the Sony GENERAL_*_RExt streams and their required profiles.
The .bit files are the original Annex B conformance streams. The Samsung archives name their payloads .bin; the repository stores those unchanged bytes with the common .bit extension. Each GENERAL_*_frame0.yuv file contains the first decoded picture extracted byte-for-byte from the corresponding published planar reference output; it was not generated by ImageSharp.
HevcPictureDecoderTests.DecodeOfficialRangeExtensionsPictureMatchesPublishedDigest limits each stream to its first independently coded picture, adapts that picture to the bounded hvc1 item contract, compares every reconstructed sample with _frame0.yuv, and verifies the published decoded-picture MD5 value for every present plane.
The retained matrix covers the ImageSharp 8, 10, and 12-bit still-image precision boundary across monochrome, 4:2:0, 4:2:2, and 4:4:4. Tool-specific H.265.1 streams remain necessary before every exposed Range Extensions tool can be marked complete.
The Main-profile traversal matrix comes from the official RQT_A_HHI_4 through RQT_E_HHI_4, STRUCT_A_Samsung_7, STRUCT_B_Samsung_7, and TUSIZE_A_Samsung_1 archives. Their published descriptions target residual-quadtree intra hierarchy depths zero through four, coding-tree and minimum-coding-unit structure, and a 64x64 coding-tree block with 32x32 minimum coding units and 16x16 minimum luma transforms, respectively.
HevcPictureDecoderTests.DecodeOfficialTraversalPictureMatchesPinnedHmDigest decodes each first independently coded picture through the production still-item path and compares all three native planes with fixed MD5 digests. The RQT values are the streams' decoded-picture-hash SEI values. For STRUCT and TUSIZE, the plane values were calculated from the first picture written by the HM reference decoder at commit 9c1f298659ab0cee9dc13d23d0304221575410b9; the complete HM output also matched each archive's published file MD5:
STRUCT_A_Samsung_7:02f02cc9a67222004ae18ee6bebd475aSTRUCT_B_Samsung_7:1f472e014aff120681e8482c8a04ef93TUSIZE_A_Samsung_1:5e6c198c852e92cdcca0e137fc2610c4