DivX5 and gknot?

[Difflam]

anyone tried installing divx5, and just doing an encode in gknot (even tho it appears to not support it yet, ie u have to tell it you are doing a divx 4 encoding)? Apparently there are no problems with doing this, a friend of mine successfully encoded a few things like this. I personally havent yet tried it out.

Can anyone think af any reason why this should be done?

[dragoman]

Hi,

I have read the instructions on this, but since the bitrate calculator is all wrong for DivX 5 in Gknot (at present), I don't really see a reason to do so.

I can set up Vdub with Job Control to encode automatically the credits, 1st pass, and 2nd pass. Joining them in Nandub afterwards is not that big a deal.

I personally am going to wait until the new Gknot comes out (hopefully with DivX 5.0 support).

dragoman

[kastro68]

Just use Gknot to make an *.avs file.

Then open the *.avs file in Virtualdub with Fast recompress. Use Virtualdubs Job control feature and come back in 3 hours.

Ja ne

[dragoman]

Yeah that's what I do too....easy to make a seperate movie and credits file....plus you don't use the internal filters in DivX 5, you use avisynth ones in Gknot...

dragoman

[tripnotik]

Why do you say the bitrate calculator is wrong? Let's recapitulate what a bitrate is. It is the number of bits per amount of time. So 1000 kbps will always be 1000 kbps no matter which codec you use. (well, there was a little difference between divx3.11 and divx4 because one assumed 1kb == 1000b and the other 1Kb = 1024b) And on two rips, it gave me the right filesize +/- 3MB.

And besides, everybody should learn how to use avisynth scripting language. It's really easy and powerful, and I find it easier than relying on GordianKnot. I mean, writing 5 lines is not very hard.

[dragoman]

Hi,

Why do you say the bitrate calculator is wrong? Let's recapitulate what a bitrate is. It is the number of bits per amount of time

Sure it is. If you are using a Constant-bitrate (CBR) encoding method.

However, if you are using a two-pass, Variable-bit-rate (VBR) method, the ending filesize cannot be accurately predicted 100% of the time.

Espcially with DivX 5 Pro. B-frames takes conventional bitrate-calculators predictions and throws them out the window. A different video source will have a different level of compressiblity, and therefore a different filesize. Sometimes you may get lucky (as you have) and have a filesize close to what the DivX 4 calculator gave you, but not all the time.

dragoman

[rui]

dragoman, all you wrote is correct, but i already made about 7 divx5 pro rips, and all of them were almost 700 MB in size.
I used Gnot to creat the main movie avs and credits avs, do the audio, then using the bitrate gnot gave me to config the encode in vdub, and voila, all avi's, after joinning credits and audio were almost spot on.

[theReal]

As long as you're not hitting maximum quality, divx5 with b-frames does not produce smaller files in 2-pass encodes. When you're at maximum quant 2 quality anyways and the use of b-frames makes your files too small, then don't use b-frames and your settled.

I can only say I don't know any case where I ever reached maximum quality with a dvd->divx conversion, so I think I will not very often have the "problem" of not reaching the desired filesize.