motion correction for xvid?

[Doom9]

well.. is there a big difference between activating motion correction in gknot for xvid and not doing so? I'd hate to re-encode yet again..

[Teegedeck]

Errrr.... I'd say so. But anyway, I think motion-correction results in worse encodings with any codec because the theory that the human eye can't detect it just isn't so convincing. So, if you have used it for 3.11, I think it's fair you used it with XviD (I believe DivX-4 has a kind of motion-based compression, too, that you cannot change). [EDIT:]Hm, perhaps motion-correction works better with codecs that use the blurry H.263 quantizer? :devil:

[Doom9]

motion correction is on by default in gknot if I'm not mistaken so sbc got it too.. in any case.. I also asked isibar but I guess I'll leave it as it is now... just reviewed the first of the 3 matrix chapters... rest of that movie is coming tomorrow as is the last xvid encoding session. now if I just had a solution for the wmv cutting problem... let's see what microsoft installed when I downloaded a whole serious of windows media tools....

[NeVeRLiFt]

G'Luck and thanks for what your doing.

[Evaldas]

How do I disable motion and luma correction in GKnot? Is it enough just to uncheck checkboxs under coresponding titles (near note "default")?

@doom9. Try asftools for wmv cuting. I think it should work.

[Doom9]

asftools is for ms mpeg4 v2/3 and maybe wmv7 (wm1)... not wmv8.. plus... I'm not going to download hundreds of megs of SDKs that just screw up my system for one simple tool. If somebody has it, send it to me but I'm pretty sure it will fail

[Teegedeck]

... Should we introduce instant crucification for anyone who suggests using WM8 after today? :devil:

[EDIT:] Of course not. I really try not to be biased against that codec, but it's pretty hard when I hear all that. Oh -forgot something. Perhaps I should have told you about a two-pass software that I read about in the old WMV-forum (called 'American WMV') that promised to make 2-pass easier.

[Doom9]

btw.. anybody else got crashes with the latest xvid builds when using the mpeg quantizers? trying to collect some additional hard facts for isibar.. I certainly can't use that mode (note that I got a build dated 1/22 directly from the CVS... that includes mmx optimized mpeg quantizers.. apparently not quite compatible with my cpu)

[-h]

btw.. anybody else got crashes with the latest xvid builds when using the mpeg quantizers? trying to collect some additional hard facts for isibar.. I certainly can't use that mode (note that I got a build dated 1/22 directly from the CVS... that includes mmx optimized mpeg quantizers.. apparently not quite compatible with my cpu)

I'm crashing on my K7 1.2 Ghz - it only occurs when using MPEG quantisation with quant=2. Quant>=3 is fine. However, the fault in Vdub seems to be non-specific to mmx, and may be a compiler issue..

-h

[Doom9]

well, isibar sent me a build earlier which worked using mpeg quantizers and the only diff between that and the one that's crashing now is that the crashing one has mmx optimized qantizers so I guess there's something to that.

also... I'm of course only using 2 pass vbr so that means min=1 max=32 ;)

[-h]

Hrm no CVS update yet, I guess it's a weird one.

If you want the speed of the mmx version, anyway, you can set the min quant to 3 and go for broke.

-h