Back to Search Document details
42nd Meeting: Santa Eulària, ES, April 2026 2026-02-19 14:34
AHG17: Suggestion to enable BIM for the GOP-based RPR comparison point
Abstract
This contribution suggests modifying the lambda in rate-distortion optimization for the GOP-based RPR comparison point in the CfP draft by setting the VTM configuration parameter BIM equal to 2. The lambda is then reduced for CTUs that are likely to be used for prediction of other pictures and increased for other CTUs. Doing so the encoding spends more effort to reduce the distortion for CTUs that are predicted to be important.
JVET-AP0043 AHG17: Suggestion to enable BIM for the GOP-based RPR comparison point [K. Andersson, P. Wennersten (Ericsson)]

This was reviewed during the Aachen meeting (see JVET-AP0041). Viewing was performed there, and it had been concluded that it was not harmful using the method, but there was no evidence that visual quality would be improved when BIM=2 would be used (confidence intervals overlapping), compared to RPR encodings that use BIM=0 (see report JVET-AP0041), but no final recommendation about using it was made.

Short presentation of the document was given Wednesday 29 April at 1645.

After short discussion, it was agreed to use BIM=2 for the additional VTM encodings employing RPR (not in anchors), which have the main purpose of getting better understanding how much benefit comes from proposals using some kind of adaptive resolution coding. It is assessed that this is in compliance with the general coding conditions of the CfP; this encoder-side tool is also properly documented in JVET-AO2002, and its is usage is documented in the configuration files which will be made available. No need for change in draft CfP.

Decisions
After short discussion, it was agreed to use BIM=2 for the additional VTM encodings employing RPR (not in anchors), which have the main purpose of getting better understanding how much benefit comes from proposals using some kind of adaptive resolution coding. It is assessed that this is in compliance with the general coding conditions of the CfP; this encoder-side tool is also properly documented in JVET-AO2002, and its is usage is documented in the configuration files which will be made available. No need for change in draft CfP.
Citation