[XviD-devel] what's wrong again ;)

Radoslaw 'sysKin' Czyz xvid-devel@xvid.org
Mon, 30 Sep 2002 23:05:40 +0930


Hi

I found another problem with new timecodes ;) They are so simple, yet
so tricky.
This time, it's with max_bframes = -1. Encoding crashes after exactly
one second, at WriteVopHeader() again.
Those are time values, dumped at every WriteVopHeader():

seconds = 0 ;fbase = 65535 ;ticks = 0
seconds = 0 ;fbase = 65535 ;ticks = 0
seconds = 0 ;fbase = 65535 ;ticks = 0
seconds = 0 ;fbase = 65535 ;ticks = 2730
seconds = 0 ;fbase = 65535 ;ticks = 5460
seconds = 0 ;fbase = 65535 ;ticks = 8190
seconds = 0 ;fbase = 65535 ;ticks = 10920
seconds = 0 ;fbase = 65535 ;ticks = 13650
seconds = 0 ;fbase = 65535 ;ticks = 16380
seconds = 0 ;fbase = 65535 ;ticks = 19110
seconds = 0 ;fbase = 65535 ;ticks = 21840
seconds = 0 ;fbase = 65535 ;ticks = 24570
seconds = 0 ;fbase = 65535 ;ticks = 27300
seconds = 0 ;fbase = 65535 ;ticks = 30030
seconds = 0 ;fbase = 65535 ;ticks = 32760
seconds = 0 ;fbase = 65535 ;ticks = 35490
seconds = 0 ;fbase = 65535 ;ticks = 38220
seconds = 0 ;fbase = 65535 ;ticks = 40950
seconds = 0 ;fbase = 65535 ;ticks = 43680
seconds = 0 ;fbase = 65535 ;ticks = 46410
seconds = 0 ;fbase = 65535 ;ticks = 49140
seconds = 0 ;fbase = 65535 ;ticks = 51870
seconds = 0 ;fbase = 65535 ;ticks = 54600
seconds = 0 ;fbase = 65535 ;ticks = 57330
seconds = 0 ;fbase = 65535 ;ticks = 60060
seconds = 0 ;fbase = 65535 ;ticks = 62790
seconds = -1 ;fbase = 65535 ;ticks = 65520
[crash]

I think I should finally learn how the timestamps work, myself ;)

Regards,
Radek