1 and half hours at 900 bitrate and I get 1.3 gb

[jomer]

Hi people. I need help.
I did my first rip some weeks ago following step by step the Nandub SBC encoding guide from doom9.com
The movie I ripped was Tomb Raider. I did all the steps...
----Starting Nandub a message appeared. It said I did´nt have correctly installed DIV-X codecs and I said... continue. Maybe the problem was that I needed divx 3.11 alpha to see a film which I couldn´t see well at all with the divx 3.20 codecs. So I installed 3.11 alpha over it.-----
dvd2avi>vfapi>and then in nandub. I did everything right and I got a file a bit bigger than I thought, but the problem was that I forgot to change the bitrate and left it on 910 when should be about 800.
The file was 680 mb with two passes and without audio. The second time I still didn´t get the size I needed so the third time I started the process again and did the two pass rip one followed by the other automatickly, not as the second time, where I did the first and then, using the stats the second one.
I got the filesize I needed and so I have TR.

After that rip I decided to rip Armageddon. 2 hours and 30 mins so I decided to rip it into 2 cds. Once again the divx problem message appeared and I told it not to appear any more marking the same option I marked the previous times.
And then problems started, once again followed the steps exactly as shown on the guide but this time changing values to a 2 cd rip.
When everything was ready, even that crosspoint setting set to ~460~, I pressed shift f8 to make two passes through the night on my p3 800@850 and I went to bed.
14 hours later the rip was about to finish but I could see that the filesize was about 2 gigs.
Once it finally ended, I cheked the filesize and I found that it was 2.1 GB :eek: !!!!!! and without sound, it was very extrange. I repeated the whole process following exactly the instructions given on the guide.
Once again I got a file over 2 gb for a film of 2 hours and half at bitrate of about 1000. I got f***** :scared: . That was too much. The bitrate calculator gave me a result of about 1100 bitrate for two cds of 680 mb with 128 bit sound.

I deleted armageddon and got Little nicky and the problem persists. I followed the steps and cheked if they where correct. Ripped it 3 times once with very different settings which I got from a spanish guy. He changed many things (nearly all, he changed them but then they were different from doom9s guide) and got almost the same filesize. 1.3 gb for a 1.5 hours movie without sound :confused: .

What is wrong with my configuration? Can anyone help me please? :( It´s very frustrating. Even for a "newbie" the guide is not difficult if you read all of it and if you understand it without problems, even being spanish :rolleyes:

Could it be coz of the message of the beginning? How can I fully delete divx3.20 codec then?

[UHT]

>I did my first rip some weeks ago following step by step the Nandub >SBC encoding guide from doom9.com

its doom9.org or doom9.net

>couldn´t see well at all with the divx 3.20 codecs. So I installed >3.11 alpha over it.

divx 3.20??

you arent being specific enough for me to give any help with the rest of your problems im afraid....and dont trust "some spanish guy"

[jomer]

I knew I read something somewere. I went to the downloads page on doom9 and foud it. Divx 3.2 ...
DivX 3.11 VKI - a patch to make DivX VKI by default (sometimes DivX 3.11 plus VKI is referred to as DivX 3.2)

I don´t know anything more to tell you. If you could say what do I need to tell you...

[Teegedeck]

Well, don't use anything different from DivX 3.11 alpha with Nandub. Hacks like 3.20 will have features like inserting keyframes at the start of scenes or their own brand of CBR - but all of this conflicts with Nandub that is supposed to have complete control over keyframe-insertion and bitrate.

[rmatei]

I could try and solve your problem, but you didn't post the specific settings. Also you seem very, very confused. There's a lot of pathetic advice out there about ripping. Just go to doom9.org, guides, and follow the gordian knot guide under divx3. And I mean, read it, read it again, and again until you fully understand. I guarantee your problems will go away, and if they don't you can come back here.

[jggimi]

Many of these tools are limited in their capability to integrate with others. As an example, this is from the readme to Gordian Knot:do not complain if you replace included software with other or newer versions and something doesn't work.
it's highly, highly, highly recommended to install THE FULL PACKAGE. also if you think you already have this codec or that software. it doesn't hurt to reinstall the codecs. the newest and best sw is included in the pack and it's prooven that it works TOGETHER.I can't comment on theWEF's spelling or grammer, but the point is very clear. GKnot is an integrated compilation of many different software tools, such as DivX, AviSynth, Virtual Dub, Azid, HuffYUV, and others. If you upgrade one of them, you'd better know why you're doing it, and what the impact is on the other tools in your suite.

[jggimi]

I've been thinking, since you're running into trouble with DivX3 filesize using Nandub, why don't you try Gordian Knot? It's a front-end calculator for Nandub when encoding DivX3, and according to forum polls, it's the favorite DivX3 encoding methodology. There's another reason you might want to use it; this is from Doom9's DivX3 guide (highlights mine):Newbie friendlyness:

FlaskMpeg: ++
Gordian Knot: ++
Mpeg2Avi: -
Nandub: --
Fair Use: +