Undersize Oversize problem 2 pass

[bob0r]

OK i tried everything for 3 days, now i am desperate, so lets ask the experts.

1 TV Ep per, 2 Vob files (1gb and 500mb) encode

Tried last xvid alpha by koepi, tried 1.0 beta 3 and rc1/rc2

Tried newest gknot and tried to encode via dvd2avi/vfapi to vdub

tried
VirtualDub-1.5.8
VirtualDub-1.5.10

All default xvid settings.

Like 1-2 weeks ago, my latest cap from satellite PAL, went perfectly, 2 pass target size perfect.

Now these DVDs, i already have done DVD1 and DVD2 now i want to do all 4 DVDs again and they all give me problems:

NTSC interlaced 29.970
crop 16 pixel left, 10 pixel bottom, resize to 512x384

i save pass1 to job control, i open pass2 setting, i fill in 675000 as target size, and what do i get?

4:3 ~840mb or ~1700mb, once i even got 9mb??
then i did 16:9 for a change, got so desperate, then i got ~530mb

Remember, i have done encodings in the past, so i think i got the settings right.

What could it be?
Windows XP PRO SP1 + all fixes?
Newest nvidia driver?
Versions of vdub?
Any other existing driver/dll that could make it all go wrong?

I never get the right target size anymore, how can i make sure i get the right size? Doesn't have to be super quality, anything will do!

[Koepi]

I want to point you to our excellent search function - it'll dig up threads where all these things have been discussed to death, with several different solutions.

I recommand you to read the doom9 guides, too, since your encoding chain is already ... well, flawed at least.

Fetch proper versions of dvd2avi, create a proper avisynth script (and istall avisynth 2.5x in first place). Use VDubMod 1.5.4.1.
Hit "load defaults" after installing a new codec version.

...and so on, and so on, all "well" documented in this forum.

Koepi

[bob0r]

Yup thanks, i did all the guide, step by step, but as i said, first it worked, and now it has stopped working.

But since i got a goal of 350-650mb, ill try 400mb target, guess thats all i can do, unless some other people have some advice...thanks

[bob0r]

Okay okay... last week i installed windows XP, but i installed it on D:, so my Windows 2000 Professional, Service Pack 4 (5.0 - 2195) was still on C:

I booted into windows 200, used the same setting, same codec(s) and the same virtual dub(1.5.10).

What does this mean?
Windows XP pro bug?
Nvidia driver bug (because thats the only thing different then on the win2000 system)?

I have encoded in winxp before, went good also.

So it seems a system error, but what is causing it?

Koepi, if you are interested, let me know what details you need, if not, i guess some system/os/xvid combinations just won't go.

I tried your latest alpha release, and will try the RC2 soon also.

[bob0r]

If choose PAL 4:3 as INPUT resolution, target size is DEAD ON perfect :D

Don't ask me why, but thats what works for me!

With GKNOT + newest update

edit:
Total size video + audio

699 MB (733,333,504 bytes) just perfect

Can anyone tell me why if i choose PAL 4:3 as input (instead of NTSC)
Why there are no size problems?

[Soulhunter]

Originally posted by bob0r
Can anyone tell me why if i choose PAL 4:3 as input (instead of NTSC) Why there are no size problems?
Just for guessing... :rolleyes:

A different framerate maybe... ???


Bye

[chilledoutuk]

With rc2 I have been testing with normal full quality first passes and have been hitting my taget sizes to withing 10kb which is as good as ever.

One thing i have changed is the minimum quant to 2 instead of 1 as at quant 1 a hefty overflow is need to hit target sizes and quality improvement almost non existant.

people that complain about getting undersized files do anoy me as all you have to do is use a andreas matrix and you will be able to achieve that filesize without the use of quant1 which even the devs dont like.

[bob0r]

Originally posted by Soulhunter
Just for guessing... :rolleyes:

A different framerate maybe... ???


Bye

Yes well, but source = NTSC 29.970fps (.vob)

But i choose PAL 4:3 25fps input resolution, and thus target size has no problems?
Meaning... for ntsc i need some special work done?

I got pal here, so the final encode plays perfect on my TV