Freeze frames in re-encodes

[Echo147]

I've had a very frustrating issue related to divx for the last few weeks. The problem arises when using virtualdub to recompress an avi using the low motion divx 3.11 codec. The result always contains corrupt frames, even though the source avi was perfect.

I've tried almost everthing to cure it - from reinstalling the codec to even reinstalling Windows 2000 and downloading virtualdub again, the same happens. I'm beginning to think its a hardware issue but I've not added anything new recently.

Another strange thing is, if I use fast motion 3.11, the result is fine - no corrupt frames at all... I'm completely baffled.

Any suggestions would be appreciated.

[Echo147]

Update: I just made a 30 minute divx 3.11 low motion avi with my webcam software (640x480, 15fps) and there's no bad frames - So I can assume the codec itself is fine.

Why would virtualdub introduce freeze frames from a clean download of it?

[Fruitmaker]

dont know about your problem...

ever tried nandub instead ??
Just a guess... sounds like a keyframe-Problem to me.. try a divx-fixtool

if that doesnt help.. hm... perhaps anyone elsw can help you

have fun

[UncasMS]

vd can well be responsible for frozen frames!

i've experienced FF simply cutting a perfect avi into two parts!

therefore, the process of saving or any other additional process might lead to frozen frames.

i wouldnt use divx3.x anyway.

from my experience there is no such thing as a FF in your avi when using the original M$ v2 codec!!!

if you want to give it a try, install Tsunami's filter pack 3f (according to the install readme).

a link can be found in my signature

[Echo147]

Fruitmaker: Just tried with a clean copy of NanDub now - same bad frames I can't see a divx fix tool working, the output has corrupt frames, there's no way it'll correct them back to as good as the source.

UncasMS: By not using 3.11 I assume u mean upgrading to divx 4.0? Well I'm really reluctant to do this as it means everyone I send avi's to also has to upgrade also. But I'll check out that filter pack, see if it helps.

Cheers for the reply ppl.

[UncasMS]

NO WAY, echo!!!

i wouldnt recomend divx4 at all!!!!

i said use the ORIGINAL instead. divx 3 is a hacked M$ codec.

the 'original' M$ v2 version is what i consider best.


in your case, though, there must be a different problem. if you encounter the problem over and over again, another codec will not make a big difference imho.

[Echo147]

hehe ok - out of interest I have tried using divx 4.0 cos im desperate to work out this problem, and it works. but I dont like it...

Anyway, about the original codec. I thought MS had a resolution restriction on it? Which is why it got cracked into divx 3.11 in the first place... correct me if I'm wrong

[UncasMS]

m$ codecs v1, v2 and v3 are included in the filterpack i mentioned.