New issue
Advanced search Search tips

Issue 87 link

Starred by 6 users

Issue metadata

Status: Duplicate
Merged: issue 966
Owner: ----
Closed: Jan 2018


Show other hotlists

Hotlists containing this issue:
Hotlist-2


Sign in to add a comment

Motion vector size limits cause quality loss on very high resolutions

Reported by rsbul...@gmail.com, Nov 17 2016

Issue description

AV1 currently allows coding motion vectors residuals with a full pixel size of 11 bits (i.e. -2047-2047). This means if an object moves across the image with a motion vector above that size, this cannot currently be represented in the bitstream.

If the image size is significantly above 2k (e.g. 4k or 8k content), this presents an issue. Therefore, it would be nice if the limit could be increased or removed for AV1. Even cooler would be to make the limit depend on the frame size.
 
Project Member

Comment 1 by yaowu@google.com, Nov 30 2016

Labels: -Type-Defect Type-Enhancement
Project Member

Comment 2 by yaowu@google.com, Nov 30 2016

Labels: Hotlist-AV1-must-fix
In case of multicore decoding implementation (for ex. h/w, single tile/slice) 2 cores could decode in parallel with 11bit hight distance, but if make maximum limit, than only single core could do it. I don't think, 8K like, frame size are suitable for SW decoding. Where is no big adventure to use fast motion Inter blocks, rate control can't catch such big motion in real life.
Project Member

Comment 4 by yaowu@google.com, May 9 2017

Status: Available (was: New)
Project Member

Comment 5 by yaowu@google.com, Jan 4 2018

Mergedinto: 966
Status: Duplicate (was: Available)

Sign in to add a comment