how can i make the picture perfect?

[shariryaniv]

good day.

every time i rip & encode a movie in nundub (after following the instructions in "doom9" site, step by step!), i find that the quality of the final result is ok, (only ok!) because you can see some electronics spots in the dark areas of the movie when you display the movie in full screen...
how can i get a better picture quality even if i have to create a 2 cd movie??????

thank you very mutch.
yaniv.

[WyldeF1r3]

encode at constant quant 2 :)

[shariryaniv]

forgive my ignorance but what is constant quant 2?
i searched nundub and gknot and didn't find a thing...

thanks.

[dahl]

Video -> SBC Options -> SBC Settings -> Compression Levels

[aramo]

There is a log file analyzer utility out there [I looked but could not find] that runs through the log file generated by the first pass and adjusts settings; including quant; to produce an optimised file for use in the 2nd pass. Some people swear by it, I found that the requirement to do something manual between 1st and 2nd passes outweighed the benifits.

Perhaps someone can post the name of the utility.

You could just try upping the bitrate to around 0.300bpp as recommended in the doom9 guide, this requires approx 12MB per minute of movie or approx 60 minutes per CD. Works for divx412/gKnot0.23b anyways.

[shariryaniv]

thank you alot.
i'll give it a try...

yaniv.:)

[vax]

I've posted a thread covering this topic, look at Nandub encoding after stats analysis, I hope it will be useful to you. You can find there links to Koepi's 'NandubStatsReader' tool. I have also added a similar tool into Nandub, called 'Stats analysis'. The download links to this updated version of nandub is in the thread. You can simply replace the executable of RC2 with the new release in the installation. 'Stats analysis' is under 'Video->SBC Options->Stats Analysis...'. I've added another tool under 'Tools->AVI Splitter' that automates the process of splitting large AVI into several pieces, e.g. 1400 MB into 2x700 MB, think you'll like it.

best regards,
vax

[esby]

Encoding at 'const Quant = 2'
or drf=2 to use nandub vocabulary
is NOT A GOOD IDEA,

Especially if you want to avoid the small blocks appearing
when there is motion...

These blocks are coming from a bug of the encoder
(aka the codec and not nandub)

And they will mostly show out when you ask nandub to uses drf=2...
If you want to get rid of them, uses drf=3 or 4 for keyframe,
and try to adjust the profile or the antishit param to limit
the problems.

esby

PS: Since drf is a degradability indicator, it does not
necessary mean that a drf of 2 will look better for the eye
than a drf of 3 or 4.
Of course drf of 6+ will likely not to be beautiful.
And drf of 16+ will just be horrible.

[vax]

Most often DRF2 encoded frames look better than those with DRF3+.
Actually Nando determines AVI quality (DIVX3 encoded movies only) in Nandub by calculating the average DRF for the whole movie, i.e movie with DRF2 for all frames will have the max possible quality 100.

best regards,
vax

[esby]

Indeed
'divx quality' = 200 / average DRF

But as i said, since the codec is somewhat bugged,
you'll end with frames having a drf=2 and full of problems.

Divx Quality just being a indicator of the average drf of the encode.

Nothing more.

esby