Opened 11 years ago Closed 10 years ago #1229 closed defect (wontfix)PSNR computation for Bit_Depths > 8
Description
During the PSNR computations, the maxvalY and maxvalC are computed as follows -
Int maxvalY = 255 << (g_bitDepthY-8);
My contention is that they are incorrect and should be computed as
Int maxvalY = (1 << g_bitDepthY) - 1; Change History (5)comment:1 Changed 11 years ago by DefaultCC Plugin
comment:2 Changed 11 years ago by pandrivoncomment:3 Changed 11 years ago by dthoang
In the meeting notes of the January 2011 meeting in Daegu, there is this decision. Decision: It was agreed that, when IBDI is turned on, the output of the decoding process is, in principle, extended bit depth video, and the PSNR should be calculated without rounding the output first, with PSNR calculated as PSNR = 10 * log10( (255*2^(N-8))^2 / MSE ).
This is the reason why the PSNR computation is what it is today. Although the reason may no longer apply since IBDI is no longer supported, any change in PSNR computation should be proposed and discussed at the next meeting. comment:4 Changed 11 years ago by ksuehring
comment:5 Changed 10 years ago by ksuehring
I did not see this discussion being brought up during a JCT-VC meeting. I will close the software ticket here, because there is nothing to do in the software unless we decide to change the calculation at a meeting. Note: See
TracTickets for help on using
tickets. | This list contains all users that will be notified about changes made to this ticket. These roles will be notified: Reporter, Owner, Subscriber, Participant
|
You are right. Besides, HM and JM PSNR computation do not match. This was already discussed with JCTVC-I0108. Chairs note were:
"The contributor noted a (very) small difference between the PSNR calculations in HM and JM. This difference not seem significant."
This was recalled some meetings after but no action were taken.