From: Michel L. <wa...@zo...> - 2001-11-06 10:30:35
|
On Mon, Nov 05, 2001 at 05:05:15PM +0700, Peter Gubanov wrote: > But fortunately, it stated for macroblocks, not for pixels. ;-) A bit > easier to care about, but I haven't ever seen a encoder which cared. > BTW, I have tested my encoding engine and generated a stream of 1000 > frames. It contained 1 I frame and 999 P frames, all predcted. The > mismatch error becomes rather noticable even despite I use exactly the > same IDCT for encoder and decoder, and encoder is closed loop (i.e. it > reconstructs a reference picture before predicting the next). Oh ? weird. How does thar error look like, I suppose this is high-frequency noise ? -- Michel "Walken" LESPINASSE Is this the best that god can do ? Then I'm not impressed. |