oversized encodes. (read the guides and searched)

[pdottz]

i'm trying to get some of my toon caps to be a certain filesize since they are about 12 minutes each. all xvid settings in vdubmod are default @L3 for both passes. tried cartoon mode and still got this problem.

for my second pass i tell it i want the filesize to be 70megs. i calculate for the audio being 128cbr mp3. and it says the bitrate will be 670. now when it's done encoding, the audio is fine but the final size is 115-125megs. and gspot says the bitrate is 1115 instead of the 670 it was supposed to be.

can anyone help me with this.

[GolovachLena]

Try caping default values of min quatinzer from 1 to 2, this may help.

[celtic_druid]

Since you searched I am assuming that you read all the threads about changing the default overflow treatment settings?

[lord_hevonen]

i have the same oversize problem right now, a 2CD (1,4GB) rip ends up being about 2,5GB! I'm using 2-pass Xvid with min quantizer set to 2, and the targeted file size given for both passes.
Very annoying, i think i'll switch to DivX which is sad because i think this rip looked better in Xvid...then again the better quality probably is just because of the oversize.

[Didée]

Originally posted by lord_hevonen
and the targeted file size given for both passes.
So you did it the wrong way. When doing a correct 1st-pass, you *can not* specify a file size.

Once more:

- select "1st pass" (encoding type), and in the "more..." window, specify a unique "yourmovie.pass" file.
- Let the 1st pass run
- when finished, select "2nd pass". If you did more things in the meantime, go in the "more.." window and select the correct "*.pass" file that was created during the 1st pass
- enter desired filesize
- Let the 2nd pass run

There are enough FAQs and guides that describe the procedure in more detail. Actually, it's really simple.

i think i'll switch to DivX
No one holds you back. You can't threaten with that statement.

[lord_hevonen]

Thank you for your advice, only one thing: i said i may end up trying Divx. What on earth makes you think it was meant as a THREAT?

If you are annoyed that i asked something allready answered somewhere else, i'm sorry, maybe you shouldn't have bothered to answer me at all. Anyway, thanks again for the info.

[Didée]

(Just a little arguing for the argument's sake)

Then why did you mention at all that you are likely to change to DivX? This has little to do with the actual subject, and provides little help as well in tracking down the error you made.

And in first place you did not say you may end up with DivX (which would be a vague probability). You said "I think I'll switch", which by the word is a declaration of intend.

Compare: If one is stuck with lacking functionality of a product of company X, then usually one will ask them "are you able to give me that basic functionality also, or do I have to switch to the product of company Y ? [blah!]".
That kind of arguing is a (very common) kind of threatening, and reminds me much of your style of arguing.

However, before actually switching over, you should just try again. After all, you were only one or two clicks away from doing the 2-pass procedure correctly. (And how were I supposed to rest easy, being the final cause that you're using DivX 'til eternity ;) )
Mind you, I've already made much worse things, like running a 2-days-encoding job while having forgotten to comment out a "histogram(mode="levels")" line in the avisynth script :devil: