According to the APV specification:
“The value of TransCoeff[cIdx][x0][y0] MUST be in the range of -32768 to 32767.”
However, the current OpenAPV decoder implementation does not appear to explicitly validate this constraint, and it seems to accept out-of-range TransCoeff values without reporting an error.
For example, the FFmpeg decoder fails decoding when it encounters out-of-range TransCoeff values.
Is this difference in behavior intentional? If not, should the OpenAPV decoder explicitly reject non-conforming bitstreams (e.g., return an error) when TransCoeff is outside the normative range?
According to the APV specification:
“The value of TransCoeff[cIdx][x0][y0] MUST be in the range of -32768 to 32767.”
However, the current OpenAPV decoder implementation does not appear to explicitly validate this constraint, and it seems to accept out-of-range TransCoeff values without reporting an error.
For example, the FFmpeg decoder fails decoding when it encounters out-of-range TransCoeff values.
Is this difference in behavior intentional? If not, should the OpenAPV decoder explicitly reject non-conforming bitstreams (e.g., return an error) when TransCoeff is outside the normative range?