do divx settings affect mpeg output?
should i leave post-processing options for divx disabled or has it no effect on the final mpeg output?
i ve read somewhere that the latest divx scripts 'spray' noise to reduce blocks. so what if i enable deblocking and deringing (divx 5.1) and then 'spray' even more noise for mpeg? just a thought :) |
Let every postprocessing off. Scripts are designed to deal with all artifacts, and if you removed them with the codec feature, the filters used in the scripts will be too heavy. Your picture will probably become too blurry.
Deringing for instance blurs the picture a lot ! |
merci ;)
so it does have an effect :?
explains why my mpegs were kinda blurry thanks! |
where does one change these divx settings?
|
I think post-processing settings are not used unless you use DirectShowSource instead of AVISource (but DirectShowSource gives me problems). Right now I am doing some tests exchanging undot for BilndPP() on the version 2 of the script and getting nice results. But I haven't tried version 1 script yet. BlindPP is a postprocessing filter included in MPEG2DEC package.
[]'s VMesquita |
vmesquita we are talking about the postprocessing done by the codec itself ! So they are used when you decode the video with avisource.
And the proof is that CQ found by CQMatic raise when you set the post process settings on. |
And encoding gets a lot slower too. Try encoding a small DivX clip with zero postprocessing and then at full PP in the codec settings. You'll see the difference :wink:
|
Dialhot and boulder,
This is very interesting! I'll do some tests about it, I always thought post-processing was not used when decoding but I never tested... So maybe I can replace undot by leaving Post-Processing on. :D []'s VMesquita |
I wouldn't do that. Post-processing in the decompression process means removing blocks whereas UnDot deals with general noise. Besides, UnDot doesn't slow down the encoding process nearly as much as the PP settings.
|
What is amusing is that XVID decoder has the deblocking/dering features since a long time a noone ever ask a question about it.
The same : the "film effect" of Divx decoder that is present since version 5 is the equivalent of Blockbuster(noise), and again noone ever thought about this. But that is a good thing : do not rely on anything that is in the codec else you will need a script for each CODEC TYPE avi : xvid, divx 5.05, divx 3.11, divx 4.01... Note : Didn't you ever notice that mpeg2dec3 has a deblocking/deringing feature also ? |
Quote:
|
@Dialhot
DIvX "film effect" is not the same thing as blockbuster. It adds noise to the hole picture (not only the DCT areas), making compression very hard (I tried with DirectShowsource). About the codec problem: I agree, but most people is doing only DivX AND XVid and it DivX 5 can handle DivX3 content. It looks like a good way to improve the source. BlindPP() produces good results but emulates a quantisizer "BlindPP(clip, int "quant", int "cpu", str "cpu2", bool "iPP", int "moderate_h", int "moderate_v") To Deblock and Dering on any kind of DCT-encoded source. Of course, less accurate than decoder intergrated PP, but still very efficient need YV12 input." What means that integrated PP would be even better. Real PP works by knowing the quantisizer and softening the blocks and rings. Maybe PP+blockbuster noise would be a great team... @boulder Good point about undot. |
update:
Just did a 1000 frames xvid clip with and without post-processing using avisource and got exactly 8.125.412 bytes in both... Wired... I encoded in CCE Q40. []'s VMesquita |
Quote:
|
Quote:
Quote:
Quote:
Quote:
Quote:
|
i'm thinking off letting the codec's PP do it's job and be done with it. no filters in avisynth. gonna do a few encodes, see what it's worth.
|
nm
i did 2 quick encodes to see if there's a clear difference .
first one: divx max deblocking, no deringing, and a little bit film effect, no script second : divx PP disabled, and dialhot script. ok i must admit i was doubting this whole scripting bit for a sec, but i'm back on track now :lol: though they both had practically the same bitrate, dialhot's script does a nicer job on the source than divx' own PP options. more artifacts were seen with divx PP, dialhot's was crisper. but for the deblocking part: both were blocky as hell (used a low quality divx) in the same parts. seems that there's no real solution to this yet :cry: |
Re: nm
Quote:
|
this one
i've been using this script for a while now
Code:
#Post-Process |
@Dialhot
How do I enable post-processing during decoding in XVid? I was trying to do that changing XVid settings during playback, but I guess I was only changing DirectShow Decoder properties... Maybe changing in other place I can get it to work. I really would like to compare this to blindpp()... []'s VMesquita |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.