[XviD-devel] Hello xvid-devel

Milan Cutka cutka at szm.sk
Wed Mar 3 12:14:09 CET 2004


RC> Milan Cutka wrote:
>> Hi,
>> 
>> while updating ffdshow to newest XviD API I found out that qscale and
>> qscale_stride fields of xvid_dec_stats_t struct aren't filled by XviD. I know
>> now XviD has its own deblocking, but exporting quantizer array would help to
>> external postprocessing such as deblocking, deringing and visualizations in
>> ffdshow.

RC> Indeed, they are part of the API but not created or filled. I'll add it
RC> now, thanks for the info.

Thank you.

RC> PS2. Maybe you fixed it by now, but ffdshow+xvid4 used to display "b-frame
RC> decoder lag" message, if there was a lag in video. To get rid of this, use
RC> decoding stats and check if the output frame type is "XVID_TYPE_NOTHING". If
RC> it's so, but decoder actually used some data
(xvid_decore() >> 0), it's the warning frame and you shouldn't display it
RC> (xvid's dshow just returns S_FALSE and that works).

I just fixed it.

BTW I'm sorry for messed subject line in my email. Seems like a bug in The Bat!

  Milan



More information about the XviD-devel mailing list