Bitrate Computation and SEI Messages

[haudiobe]

From @galpinf:
6) MD5 of bitstream (Optional may be tricky depending on the codec or SEI usage)
7) Metrics (where is calculated the rate? Should be before SEIs – at the encoder log level, not file level)

[haudiobe]

Why would the encoder add SEIs? And if it adds SEIs and the SEIs are relevant/necessary, then they should count.

I believe we should not use the encoder log for the bitrate. It should be the file size. Also MD5 is for the bitstream.

Please confirm

[haudiobe]

No comments received, we use the file size.

[galpinf]

1- MD5 SEI in bitstream are convenient to check integrity at frame level (as opposed to file integrity). Workaround: MD5 computation from outside can be adapted to be performed at frame level though.
2-when doing chunk encoding, we might need to adapt the concatenation tools (knows as parcat in vtm) in order to get exactly the same bitstream for comparison if we are not using frame based bitrate

[nlsdvl]

HM/bin/SEIRemovalAppStatic is now used to compute bitrate for HM/SCM.
Currently, this is disabled for other encoders.