Vdub Oversize problem

[Desai123]

Hi guys,

i was tried to encode a dvd to avi with xvid codec and followed bob somer´s guide.
the problem i encounter is tht when i use some extra filters like deinterlace, sharpen brightness etc, the size of the ripped avi increases than i specify in xvid settings.

can any of u help me with tht

[redwudz]

There's not really a simple 'cure'. You would need to take in account the added filesize. Those changes shouldn't have an effect on filesize, though. There may a particular one of those filters that is causing it.

What encoding settings are you using? If you do a 2 pass, it should come out very close.

And welcome to our forums.

[guns1inger]

However if you are using a contant quality type mode, adding detail with a sharpen filter will usually increase the bitrate required for storage.

[Desai123]

i m very pleased to c such fast response. i am runing 2 passes. as explained in bob somer´s guide. the settings r the same as there. wht i do extra is add some filters and then the size goes above 2 cd rip.
thats the link to the guide
http://www.bobsomers.com/articles/encoding-dvds-to-high-quality-movie-files-with-xvid-and-ac3-1

[manono]

That guide sucks. So, you're adding the filters for only the 2nd pass? They have to be on for both passes.

[Desai123]

i add the filters first. then go for xvid settings.
could u give me any other guide then

[manono]

Here are several guides for AutoGK. It's a fairly automatic process, but you won't be able to add any filters Take your pick:

http://www.doom9.org/autogk.htm
http://www.autogk.me.uk/modules.php?name=TutorialEN
http://www.rita.lt/guides/AutoGK_DVDtoAVI.htm
http://www.divx-digest.com/articles/autogk.html

If it looks good to you, first get and install the full Ver. 2.27 followed by the 2.35 update (just out today):

http://www.free-codecs.com/AutoGK_download.htm

If you plan on playing your encodes on a standalone DVD/MPEG-4 (DivX/XviD) player, when installing AutoGK, you'd probably should install it using the ESS chipset option.

Also, sometimes oversized video can be caused by installing a new version of XviD on top of an older version (without uninstalling the older version first). If you've done that before, I'd suggest uninstalling your XviD and then using the one that comes with AutoGK. If you resist working with an all-in-one app, be assured that, 1) it's a good one, and 2) you can pay attention to how it works and learn from it, so you can later branch out to doing it on your own.

[Desai123]

thx for the option manono but i have used autogk before. i dont want an automated process as i want my rips to be extra fine and in autogk, u cannot do tht.

the rips do come out very good but the oversize problem is worrying me

[manono]

Hi-

Sure, I understand your feelings, but, the thing is, that guide you're using now is teaching you all wrong. Just for openers, he's teaching you the VFAPI method, which was obsolete 5 years ago. The results are inferior and the encoding is about 30% slower than necessary. He's teaching you all wrong how to resize, and some of his XviD settings are screwy.

But if all you want is to get the sizes right again, I'd first suggest uninstalling your XviD, and then reinstalling it again, loading the default settings in the main screen (I think), before then customizing them to your liking.

[Desai123]

Hi-

Sure, I understand your feelings, but, the thing is, that guide you're using now is teaching you all wrong. Just for openers, he's teaching you the VFAPI method, which was obsolete 5 years ago. The results are inferior and the encoding is about 30% slower than necessary. He's teaching you all wrong how to resize, and some of his XviD settings are screwy.

But if all you want is to get the sizes right again, I'd first suggest uninstalling your XviD, and then reinstalling it again, loading the default settings in the main screen (I think), before then customizing them to your liking.

could u kindly give me some settings or a guide to encode so tht i get rid of the problem.
and
i have used other xvid settings also. (a friend had given me) but the problem only arises when i use the filters and it gets over sized.
i´ll highly appreciate it if u could guide me to get a 1400mb rip using custom settings and not an automated process

[manono]

OK, the way I learned to encode was with Gordian Knot (after a brief period using FlaskMPEG and VFAPI back in the dark ages of AVI encoding, before Nandub came around, and before AviSynth became robust enough to use). You can customze the AviSynth script (used for frameserving into VDubMod) with the proper crop, resize, the included filters, or any outside AviSynth filters you might want. It'll create the script for you. You can use any XviD settings you might want. GKnot is a front end for the encoding. After you learn AviSynth script creation and the best XviD settings for you, you can then start doing the whole thing yourself. But you may still want to refer to GKnot for the proper crop and resize, and to get the bitrate. Here are some guides:

http://www.doom9.org/gknot-main4.htm
http://www.doom9.org/xvid.htm
https://www.videohelp.com/guides.php?tools=141&madeby=&formatconversionselect=&howtosel...or+List+Guides

That's my advice; take it or leave it.

[Desai123]

hi,
i had a look at the xvid faq. it says to change the values under quantization tab regaridng the oversize problem. we can forget it for a while as i plan to experiment with gknot again.
now the question i have is how do we know wht frame rate to encode at as the guides do not explain it clearly.
what helps us decide if we should ivtc a particular film or not.

[manono]

Hi-

...i plan to experiment with gknot again

You realize that GKnot is different from AutoGK, don't you? GKnot gives you as much flexibility as you want. You can use it just for cropping, resizing, generating the AviSynth script, and getting the bitrate, and do your audio yourself, and open the script in VDubMod for manual encoding. Or you can continue the process and run a compression test and do the encoding using GKnot as the front end for the audio and video encoding, and muxing.

Maybe you've also used GKnot in the past.

now the question i have is how do we know wht frame rate to encode at as the guides do not explain it clearly.

You're in a PAL country, so unless you're talking about silent films, you'll always be encoding for 25fps. The framerate is determined by the D2V created in DGIndex. If you open it up, there's a line near the top that tells you:

Frame_Rate=29970 (30000/1001)

If it's an NTSC DVD you have, then it'll be either 23.976fps or 29.97fps (unless a silent film or a bad PAL2NTSC conversion), in which case it might be different), and you might get the final framerate either using DGIndex, or perhaps a final IVTC will be required. Be thankful you're in a PAL country where you don't have to learn about such things.

what helps us decide if we should ivtc a particular film or not.

That's not always easy to determine. You run the Preview, and if it's Progressive FILM, then you set the Field Operation for Forced Film, and it'll be 23.976fps. If it says Interlaced NTSC, then it's either true interlaced at 29.97fps, or it can be IVTC'd back to 23.976fps. In either case you set the Field Operation for Honor Pulldown Flags (as you do for all PAL DVDs) and you'll get a 29.97fps D2V. Unless you tell me you deal with a lot of NTSC DVDs, I don't much want to explain it all.