XviD registry keys and problems since 27-02-2002 builds

[sierrafoxtrot]

hi, sorry to be a pest, but i'd be much obliged if someone could help me with identifying all the registry keys xvid uses, including the ones used to store settings. i can't seem to encode 2nd pass any more with the newer builds (either koepi's or nics). the older builds (pre-curve correction) seem to work fine, but i haven't let the entire 2nd pass run to completion.

the 2nd passes that have successfully run have been either really, really undersized (by almost half!) or completely oversized and unplayable (~2Gb). scary.

i was wondering if there was a way i could wipe my system clean of all xvid traces and start from scratch.

also, as an aside, a mate was over a while back and tried to uninstall xvid by deleting it from my winNt\sys32 directory. now in the control panel add/remove program box i have this annoying "xVid dev 0.0.1" program which i cannot seem to remove. clicking it gives uninstall error. how do i get rid of this?

sorry if some of it isn't exactly xvid related, but if i sort this out i could do some more tests. :D

thanks in advance all :(

[rui]

Well, i just use the add/remove windows tab, then reboot, then goto regedit, look for any xvid keys, delete them, then reboot again, the install the new build.

Hope this helps.

[sierrafoxtrot]

@rui

i've just found the search function in regedit so i managed to get rid of those pesky entries where stuff is stored. thanks!

maybe now i can finally try encoding the replacements! :D

[rui]

glad to read that. Looking forward for your results.

[-h]

There is a "bug" where the overflow can run away, and eventually crash VDub. A fix is known, but it's a quick hack and doesn't really address the issue as well as it should.

It's being looked into..

-h

[sierrafoxtrot]

@rui

sure thing! i'm probably going to try going for 540* and it looks like it might need tempsmoother(3), because the default compcheck's 0.546 ... pretty high ... anyway, i'm sure xvid can handle it, once i sort out these crashes ...

@-h

yeah, kinda realised it when debug output was showing massive overflows. does anyone have any idea why this happens? i've noticed it seems to happen mostly during credits (i use const quant 20). anyway ... thanks for the heads up, i've switched to koepi's 28-02-2002 build. :)

[Franko30]

Originally posted by -h
There is a "bug" where the overflow can run away, and eventually crash VDub. A fix is known, but it's a quick hack and doesn't really address the issue as well as it should.

It's being looked into..

-h


@ Koepi:

Has this been looked into in your Feb28 build? That ("overflow running away") was what I was talking about in my postings in the CVS 2002-02-27 thread.

Cheers

Frank