The current 360Lib code (360Lib-3.0rc1) with HM-16.15 while converting from ERP to RVP, we observe PSNR is not calculated properly may be due to not setting the bit depths as SPSNR_NN is disabled for RVP. We think the following might be a bug.

Old code: At line 2119 in source\App\utils\TApp360Convert\TApp360ConvertCfg.cpp

#if SVIDEO_SPSNR_NN

cSPSNRCalc.setSPSNREnabledFlag(m_psnrEnabled[METRIC_SPSNR_NN]); if(m_psnrEnabled[METRIC_SPSNR_NN]) {

cPSNRCalc.setOutputBitDepth(m_outputBitDepth); cPSNRCalc.setReferenceBitDepth(m_referenceBitDepth); cSPSNRCalc.setOutputBitDepth(m_outputBitDepth); cSPSNRCalc.setReferenceBitDepth(m_referenceBitDepth);

}

#endif

Suggested new code: #if SVIDEO_SPSNR_NN

if (m_psnrEnabled[METRIC_PSNR]) {

cPSNRCalc.setOutputBitDepth(m_outputBitDepth); cPSNRCalc.setReferenceBitDepth(m_referenceBitDepth);

}

cSPSNRCalc.setSPSNREnabledFlag(m_psnrEnabled[METRIC_SPSNR_NN]); if(m_psnrEnabled[METRIC_SPSNR_NN]) {

cSPSNRCalc.setOutputBitDepth(m_outputBitDepth); cSPSNRCalc.setReferenceBitDepth(m_referenceBitDepth);

}

#endif

Bug can be emulated by e.g. setting the coded picture size to 3840 x 1920 for the ERP 360 video input of the same picture size.

Wrong initialization values are used for multi-value input fields when WCG_LUMA_DQP_CM_SCALE is enabled.

When I set a different value set from the default via configuration file, the set is ignored.

Attached is the proposed patch.