Dependency of high precision motion vector bit decoding on reconsturcted MV values

flaccidware / webm

Automatically exported from code.google.com/p/webm

0 stars 0 forks source link

Dependency of high precision motion vector bit decoding on reconsturcted MV values #1036

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

This is an unintentional leftover dependency that leads to additional 
complexity in hardware implementation. The dependency should be removed in VP10.

Original issue reported on code.google.com by ya...@google.com on 10 Jul 2015 at 11:40

GoogleCodeExporter commented 9 years ago

Also in vp9: two blocks next to each other where the second uses the first as 
reference with no offset (i.e. NEAR/NEAREST) can still have different MV values 
(i.e. the high precision bit can be flipped between the two).

Original comment by ya...@google.com on 10 Jul 2015 at 11:54

GoogleCodeExporter commented 9 years ago

Original comment by ya...@google.com on 14 Jul 2015 at 4:42

Added labels: Component-libvpx, Type-Enhancement

GoogleCodeExporter commented 9 years ago

Original comment by ya...@google.com on 12 Aug 2015 at 10:06

Changed state: Assigned