I've just done another rip, and just like the last one (Shadows Run Black) it has come out at under 600MB.

My settings are correct as far as I can see, so I am puzzled as to why this has happened again.

I will release the rip anyway as the bitrate is fine for the so-so image quality on the DVD, but does anyone know of any issues or glitches with GKnot that could cause undersized rips?

I can post the log if necessary.

the same thing happened to me once. and the problem was that the xvid codec wasn't properly installed, because i didn't uninstall the older one first. so my guess is that if you first uninstall your codec and then reinstall the latest version things are running smoothly again.

i remember that spud tried almost anything then to help me, but it really was just a bad installation of the codec.

oh, and one other time i just had to go the codec settings in gspot. i didn't change anything there but afterwards everything was fine again...

Thanks avatar, I'll try that.

yup, normally its a stray setting somewhere, uninstall everything, reinstall everything.

Same happens me all the time. Set it in AGK for 2 CDs, got a great looking 570MB file. Uninstalling and reinstalling didn't work UNTIL I un/reinstalled regular GK too. I must have done this 8 times these past months. Reinstalling is no big deal but its a very annoying problem and I hope they fix it sometime soon.

I've just done a rip in GK with the latest stable XviD on a machine that I've used before to do rips on. It was set up to do a 700 MB rip and came out at 189 MB - wtf. I remembered this thread and uninstalled everything and reinstalled again with exactly the same results. I've checked and rechecked all the settings and I can't figure this out. What bugs me most is I've done this before quite a few times and it's always worked - so why has it started doing this now?

Take some screenshots of the Xvid settings for the second pass (settings need to be identical for both passes)

First popup -> Screenshot
Clcik the first "more" -> Screenshot
Advanced Options -> Screenshot
and quantization under Advanced options -> Screenshot

Then post them here, you sound like you've got a stray setting. The other thing will be that you've messed up your project.

Make sure your project is setup right, check the length, total size and resolutions tabs are all setup correctly.

Its worth noting what version of gknot you have 0.35.0 works with 1.1, but 1.1 causes under sizing with earlier versions.

my quantization is set at 1 / 31 u can use 2 / 9 also try both see what works for ya

@video-man,
you shouldn't set them to 1/31 unless your rip can cope, or so i'm told by the ripping wizards at fh, it doesn't allocate bitrate well.
Set it to 2/31, and only drop to 1/31 if you have bitrate allocation problems.

This is in reference to an undersized rip i was having that came out at 1.1GB

Well there they all are - I really hope someone can spot my stupidty immediately 'cos I'm getting fed up now after doing this 3 times. Thanks spud for your help.

There's absolutely no point in checking Packed Bitstream, it just makes it incompatible with standalones with zero pluses. You should check Adaptive Quantisation it offers some improvements and there's no reason to uncheck it.

Go into your options tabs and set those up as your defaults so its saved for each encode you do.


Now, as for your undersizing problem, try this... drop your min quantizers all to 1, and then on your b-vop (where you made the mistake of leaving packed bitstream checked) first box = 1, second box = 1.40 third box = 1. Changes need to be for both passes obviously.

Changing the b-vop settings has always fixed undersizing for me. (make sure its not default like this, you only need to force the issue with undersized rips)

I can understand if the size was a little smaller, but 20% of the predicted size is very odd. Can I also add that these are the settings I've always used. The other thing I'm thinking is that the source is quite noisy and interlaced as well, though I doubt trying to sort these should affect the filesize that much.

The packed bitstream setting is default in Simple @ LO - I'll change it to Advance Simple @ L5 and disable it then, but like I said I haven't changed any XviD settings since I first set it up.

Finally on the last screenshot you can see the filesize in the log (or what GK is rtying to set it to from the first pass), just doesn't end up at that.

Cheers spud - I'll crack on.

you've probably have a number of sources for your releasen disappearing when they turned off packed bitstream (which means the hash changes). Shouldn't use that stuff because of all the ludites.. on the one hand, i think big deal they knew what they were getting when they bought a crap standalone, but in this case it doesn't actually do anything useful. The other advenced profile stuff GMC and QPEL do improve quality, but they are even less compatible than Packed Bitstream and require more processing power.

I thought perhaps it was only encoding a really short clip. Once or twice the source file i was using was only a clip of the full movie, like when i did an encode from a vhs, the DV avi wasn't all being processed, just the first 20mins. Gknot shows urs is the full length.

oh and yes, you should use L5, simple is a bit restrictive for my tastes.

I've sussed it. OK here is the scenario. I tried the encode on my laptop, with the same settings and versions of XviD and GK with the same results. I dropped the XviD version on the laptop to 1.03 (with all the same settings) and it worked. On my PC I changed the profile to Simple @ L5 (with XviD 1.1 still) and that worked too. Which suggests that with Xvid 1.1 the profile has to be correct (to enforce the level settings?) and with 1.03 it doesn't matter if it's at Simple @ LO. That's my theory anyway - but I'm just glad it worked.

One thing spud, this is from a DVD source but the quality isn't that brilliant even for the original DVD, should it go in HQ or LQ. Cheers for your help btw.

low i'd imagine, if you forced down to < 512 resolution that's pretty much a automatic low quality since its suggestive that it needs the bandwidth