Undersized files with XviD 05-042003 Koepi's Build

[Colyptic]

I seem to be getting undersized files, anywhere from 5-15MB using the new build. For instance here's what I used for a 100 min. encode
Search Position=6
Quantisizer=H.263 (1st pass) New Mod. (2nd Pass)
VHQ=4 - wide
Max. I-frame Int.=300
Min. I-frame Int.=1
No 'extra features' except B-Frames 3/150/100
Alt. Curve=Med./100/200/50
Chroma Optimizer with 0 frame drop

Lanczos Resize (544x288) and deen (default values) used in the script

First pass came out to be 983MB
Second pass came out to be 600MB, XviD was set to target for 619290 (605MB).

The same setup, and XviD 22032003 (Koepi's Build) always came out to be within 1MB of the target size.

Anyone else experiencing this?

[seewen]

Have you tried with "VHQ = 0" ?

[NiTroGen]

Originally posted by Colyptic
I seem to be getting undersized files, anywhere from 5-15MB using the new build.
.............
Second pass came out to be 600MB, XviD was set to target for 619290 (605MB). Why does it bother you? You video is undersized a few megabytes, not oversized. You don't know how to fill the extra space of the CD? ;) I don't think that allocating 5 more megabytes to the video will give you a noticable difference in the quality.

PS. I think it's the Alt. Curve Compression responsible for this. Did you try to use Linear Curve Scaling?

[Animaniac]

Isn't modulated quantization coupled with B-frames a bad idea?

[Colyptic]

It doesn't bother me much, I can always reencode the audio as long as its MP3, AC3 is a different story...

Just stating the fact the older builds I've used in the past 6 months were always very precise (within 3MB or so of target size)this new build however seems not to be so precise for me, been using the same settings since VHQ feature was implemented. I've talked to a few others that have said the same thing. Are we really doing anything wrong or did something drastic change in this new XviD build?

As far as turning off VHQ, I tried that on a 10m 24s clip, turned out 1.4MB short of target.

Modulated Quantizers and B-Frames, I read some discussions that you shouldn't do it, but I've never seen a visual problem with any of the encodes I've done this way, so I'm really not sure.

Just did another encode overnight, 90 minute movie, 640x352 Lanczos with Deen. Aimed for 622093 (608MB), second pass was 1048MB. Result was 605203 (592MB) of video, 16MB short. I'm going to try the 22032003 build with the same script, XviD settings, and target size and see what happens.

[Koepi]

i have no such problems whatsoever, I always hit around 4kb of targeted size.

Did you hit "load defaults" after installing the build?

Regards
Koepi

[Colyptic]

yeah I did hit load defaults, acutally I did get it working right and its very precise. I just removed and installed again, now it's working great. :)