16.05.2023, 11:58
Feedback from Adobe:
The original AVCI 50/100 specification in 2005 had a mistake, requiring the full range flag to be set in the bitstream even though the content is always legal range. The solution is to make sure the wrapper is marked as limited range, and for applications to interpret the decode range according to the wrapper, not the bitstream. Professional media applications have been aware of this specification glitch for ages and have handled it correctly. If we were to export AVCI 50/100 with the full range flag set to false, it would not conform to the spec, and many media validation tools would fail the file.
The original AVCI 50/100 specification in 2005 had a mistake, requiring the full range flag to be set in the bitstream even though the content is always legal range. The solution is to make sure the wrapper is marked as limited range, and for applications to interpret the decode range according to the wrapper, not the bitstream. Professional media applications have been aware of this specification glitch for ages and have handled it correctly. If we were to export AVCI 50/100 with the full range flag set to false, it would not conform to the spec, and many media validation tools would fail the file.