Re[8]: [XviD-devel] New Motion Estimation (from sysKin) committed to branch

Michael Niedermayer xvid-devel@xvid.org
Wed, 25 Sep 2002 20:59:57 +0200


Hi

On Wednesday 25 September 2002 19:03, Radoslaw 'sysKin' Czyz wrote:
> > if yes or dunno than it would be nice if someone could provide a short
> > file which shows these problems
>
> OK, I just encoded a very small clip. The only decoder which doesn't
> give me any problems with it is xvid VfW. Please check how it goes for
> you. Artifacts are quite visible with anything else.
> http://users.bigpond.com/syskin/test.avi . 980KB
the modulo_time_base seems to be wrong ( again ;) ) 

(type 1-I 2->P 3->B)
 type:1 modulo_time_base:0 increment:0
 type:1 modulo_time_base:0 increment:0
vop not coded
frame skip, framesize=6
 type:2 modulo_time_base:0 increment:2
 type:3 modulo_time_base:0 increment:1
 type:2 modulo_time_base:0 increment:4
 type:3 modulo_time_base:0 increment:3
 type:2 modulo_time_base:0 increment:6
 type:3 modulo_time_base:0 increment:5
 type:2 modulo_time_base:0 increment:6
vop not coded
frame skip, framesize=6
 type:2 modulo_time_base:0 increment:9
 type:3 modulo_time_base:0 increment:7
 type:3 modulo_time_base:0 increment:8
 type:2 modulo_time_base:0 increment:12
 type:3 modulo_time_base:0 increment:10
 type:3 modulo_time_base:0 increment:11
 type:2 modulo_time_base:0 increment:12
vop not coded
frame skip, framesize=6
 type:2 modulo_time_base:0 increment:16
 type:3 modulo_time_base:0 increment:13
 type:3 modulo_time_base:0 increment:14
 type:3 modulo_time_base:0 increment:15
 type:2 modulo_time_base:0 increment:19
 type:3 modulo_time_base:0 increment:17
 type:3 modulo_time_base:0 increment:18
 type:2 modulo_time_base:0 increment:22
 type:3 modulo_time_base:0 increment:20
 type:3 modulo_time_base:0 increment:21
 type:2 modulo_time_base:0 increment:0   <-------
 type:3 modulo_time_base:0 increment:23
 type:3 modulo_time_base:0 increment:24
 type:2 modulo_time_base:0 increment:4

btw, why are there not-coded VOPs in there?
if they are supposed to be skiped frames then they should have a unique 
timecode IMHO

[...]

Michael