How to compensate Min Quality ?

[sid]

Maybe you read this Handy...

You said that i should try to use

Antishit 16
MinQuality 30
Motion Modulation 0

The problem is that the video quality becomes perfect but the filesize gets out of control :/ How can i compensate that ? Raising the DRF from 7 to 8 or 9 would let get the quality worse...

[manono]

Hi-

Try setting Min Qual=1.

Not to disagree with Hanty, but Min Qual=30 can sometimes result in oversized files

[Hanty]

Anti shit at 30 DOES add about 15-25 MB/CD for me. So if you are cutting it close to the 700 mark then you might consider manonos option.

Personally I say it's worth it though because at 30 it virtually eliminates ALL spots/grain/shit. Oh, and I don't recommend messing with the DRF levels, they have proven to be unreliable and most codec gurus here recommend having them at 2-16 for everything.

[OUTPinged_]

Hanty, there is no way DRF16 will look good in hq encode anyway

i can understand people capping max at 8, but 16....

look, how often does your encode use higher than 7 drfs? 1%? 0.1%?

imo you can take a burden of those 1% of frames and be almost sure no scenes will get blocky.


and minQ isnt that reliable too tbh. on Lain encode it was choosing CL32 (!) frames for one particular scene (lots of high contrast red and blue gradient on black background+flashing), so i had to reencode that piece myself.


last one: is it just me, or antishit at 16 misses some serious shit? i raised mine till 21, only then it helped alot.


beeeeeeeeeeeeeeeer beeeeeeeeeeeeeeeer beeeeeeeeeeeeeeeer beeeeeeeeeeeeeeeer \o/ \o/ \o/ \o/ \o/ \o/ \o/ \o/ \o/ \o/ \o/

[manono]

Is that the secret-raise the Anti-shit setting? Don't you just hate it when you have an otherwise good looking rip, except for one or 2 cases of inverted blocks on the subs. It's enough to drive a man to making separate subs.

[Hanty]

Night of the Living Dead had some frames at 8-9 for me, that's the most obvious that comes to mind. And I say it looked quite good (good as in close to the source). It might not be much but I saw this guys entire getup (.vcf) on irc (#doom9), and believe me there wasn't much else to tweak here without starting to settling for less.

I speak from my own experience. Where 10/20/0 in antishit has let through "shit" while 16/30/0 hasn't, there's no right or wrong about it. Anti-shit is a slave of circumstances.

I'm slighly contradicting myself though, since there already were complaints on the encode being oversized I can't recommend it. Those anti-shit settings are for the times when you have some space over to play with.

[sid]

Hi,

i tried the suggestions Hanty gave me on another movie today, final size should be ~700megs. But i got a filesize of 952MB. Here are my settings (crosspoint 450, alt. SCD 35). Maybe i made the error somwhere:

VirtualDub.audio.SetSource("F:\\STUDIO54\\VIDEO_TS\\studio54 AC3 T01 3_2ch 384Kbps DELAY -66ms.mp3");
VirtualDub.audio.SetMode(0);
VirtualDub.audio.SetInterleave(1,500,1,0,0);
VirtualDub.audio.SetClipMode(1,1);
VirtualDub.audio.SetConversion(0,0,0,0,0);
VirtualDub.audio.SetVolume();
VirtualDub.audio.SetCompression();
VirtualDub.audio2.SetSource(1);
VirtualDub.audio2.SetMode(0);
VirtualDub.audio2.SetInterleave(1,500,1,0,0);
VirtualDub.audio2.SetClipMode(1,1);
VirtualDub.audio2.SetConversion(0,0,0,0,0);
VirtualDub.audio2.SetVolume();
VirtualDub.audio2.SetCompression();
VirtualDub.video.SetDepth(24,24);
VirtualDub.video.SetMode(3);
VirtualDub.video.SetFrameRate(0,1);
VirtualDub.video.SetIVTC(0,0,-1,0);
VirtualDub.video.SetRange(0,0);
VirtualDub.video.SetDivX(820,10);
VirtualDub.video.SetQualityControl(2,16,30,0);
VirtualDub.video.SetMotionDetection(8,10,300,300);
VirtualDub.video.SetCrispness(30,0);
VirtualDub.video.SpaceKF(24);
VirtualDub.video.InternalSCD(100);
VirtualDub.video.SetMinKBPS(400);
VirtualDub.video.SetCurveFile("F:\\STUDIO54\\VIDEO_TS\\studio54.stats");
VirtualDub.video.SetCurveMcFactor(30);
VirtualDub.video.SetCurveCompression(35,3);
VirtualDub.video.SetCurveFilter(270,2500);
VirtualDub.video.SetCurveCredits(139280,350);
VirtualDub.video.SetLumaCorrectionAmp(1,10,30);
VirtualDub.video.SetCurveRedist(1);
// VirtualDub.video.CalcCurveCompression();
VirtualDub.video.SetCompLevelsMain(2,16);
VirtualDub.video.SetCompLevelsA(300,3,16);
VirtualDub.video.SetCompLevelsB(300,4,16);
VirtualDub.video.SetCompLevelsC(300,5,16);
VirtualDub.video.SetCompLevelsD(300,6,16);
VirtualDub.video.SetCompLevelsE(300,7,16);
VirtualDub.video.SetCompLevelK(4,31);
VirtualDub.video.SetBitsReservoir(5,35,30,80,90,0);
VirtualDub.video.SetLowBrCorrection(0,0);
VirtualDub.video.NoAVIOutput(0);
VirtualDub.video.GenStats("",0);
VirtualDub.video.SetEncodingControl("");
VirtualDub.video.filters.Clear();
VirtualDub.video.filters.Add("resize");
VirtualDub.video.filters.instance[0].SetClipping(6,68,0,66);
VirtualDub.video.filters.instance[0].Config(576,240,4);
VirtualDub.subset.Delete();
VirtualDub.brc.Set( 0, 700 );
VirtualDub.brc.Set( 1, 1 );
VirtualDub.brc.Set( 2, 124 );
VirtualDub.brc.Set( 3, 97 );
VirtualDub.brc.Set( 4, 1 );

[Hanty]

Like I said earlier, being big on anti-shit is counterproductive for 1 CD rips.

[sid]

ok with leaving min quality 0 or using it with modulation to get the desired filesize, what can i do else to improve the quality ?

[Hanty]

With 1 CD rips you should be asking, "what can I do to get size down?" and second think about quality.

[sid]

It should be possible to 1:38 min on 1cd with good quality. I mean i speak about not acceptable quality for 1cd rip. i had better 1cd rips before which were longer and i wouldnt care if the picture in general would be less sharp or just the background. But i speak of heavy blocks and jerky scenes.

I was asking myself why you have only 20-30 megs oversize with ANtishit 16,MinQuality 30 and Modulation 0 and i had 200 (trying that on 2cdrip 400megs) oversize. you see my latest settings above and everything seems to be good to avoid such a big oversize :confused:

[Hanty]

Length in time is not a good measure of how big an encode will turn out to be. All movies compress differently.

[sid]

Lets get back to Quality Control problem. I would like to use it like you told me, but what could be the problem for the 'extreme' oversize ? You saw my settings and i dont find a reason in them myself. On the other side the motion modulation seems to be the reason that the movies get so much oversize when i use antishit 16/min quality 30 and motion modulation 0. Well i dont understand this cause you said you use that settings, too, and get only 20-30 mb. :confused:

[Hanty]

And I also said that all movies compress differently and that I don't recommend it for 1 CD rips.

[manono]

hi-

Lowering your minimum bit rate from 400 to 300 or so will help some.

Did you Force Film or IVTC to get the frame rate down to 23,976fps (for NTSC stuff)? You can check File Information in Nandub to make sure.

[sid]

its a german dvd, so RC2 -> 25fps

Hanty: if you dont recommend it for 1cd should i just use Antishit16 / Minqual 0 / modulation 0 or use antifreeze instead ?

[Hanty]

Go with what manono suggested earlier, 16/1/0

[OUTPinged_]

sid, as people are already pointing you out, just set minQ at 1. next, raise antishit to 20 or 21 at least (16 just doesnt cut it).

other option is, dont use that thing at all. if you get artifacts on subs, change sub's border width/color/font. if you get artifacts in movie, just use another codec. all codecs are about the same and you wont get drastical quality decrease only because of switching. (dont use divx4, it sux)

[CdinT]

manono: I'm using 16/0/50 from some time. Everything seems ok with this setting. Could you please tell me the benefits gained from the setting you use?

[manono]

Hi CdinT-

If it works for you, then keep using it. I've had enough problems with shit and I'm not recommending anything. I was just responding to the fellow that was getting oversized files with 16/30/0. 16/1/0 will give you the filesize you want, but is not guaranteed to get rid of all the shit. Perhaps OUTPinged_'s settings are better.

[Hanty]

There's one anti-shit setting for every encode. Anyone preaching a single setting as being the rule should be questioned. Newbies to encoding love to swallow any generalizations because that means they can unplug testing/thinking, and then they are completely lost when their "promised" settings aren't working.

[CdinT]

OK, I've got it, thanks for reply guys.