Skip to content

Fix: MD5 error triggers with --TmvpNmvpAML=0 and --ArmcRefinedMotion=1

With this configuration, the MD5 error triggers because encoder uses ARMC-refined merge candidate list for merge CU's, while decoder would fail to reference this ARMC-refined merge candidate list.

Merge request reports