digitalFAQ.com Forums [Archives]

digitalFAQ.com Forums [Archives] (http://www.digitalfaq.com/archives/)
-   Video Encoding and Conversion (http://www.digitalfaq.com/archives/encode/)
-   -   Do divx settings affect mpeg output? (http://www.digitalfaq.com/archives/encode/5524-divx-settings-affect.html)

zes 09-11-2003 09:44 AM

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 :)

Dialhot 09-11-2003 11:41 AM

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 !

zes 09-11-2003 12:29 PM

merci ;)
 
so it does have an effect :?
explains why my mpegs were kinda blurry
thanks!

J-Wo 09-12-2003 08:50 AM

where does one change these divx settings?

vmesquita 09-12-2003 10:34 AM

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

Dialhot 09-12-2003 10:36 AM

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.

Boulder 09-13-2003 06:55 AM

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:

vmesquita 09-13-2003 01:55 PM

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

Boulder 09-13-2003 02:08 PM

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.

Dialhot 09-13-2003 02:19 PM

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 ?

Boulder 09-13-2003 02:38 PM

Quote:

Originally Posted by Dialhot
Note : Didn't you ever notice that mpeg2dec3 has a deblocking/deringing feature also ?

I actually use it sometimes, deblocking luma (cpu=2,moderate_h=30,moderate_v=50). I've used it with some very poor quality DVDs and had good results. I think that those moderate_h and v values were suggested a long time ago when MarcFD added Nic's deblocking features to MPEG2DEC3. They don't soften much and get rid of the worst visible blocks on the DVD.

vmesquita 09-13-2003 10:57 PM

@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.

vmesquita 09-13-2003 11:37 PM

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

Boulder 09-14-2003 03:05 AM

Quote:

Originally Posted by vmesquita
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

There's two different places where you can set the postprocessing. One is in the codec settings in the screen you use when you're encoding something to XviD, the other's available when you play XviD material in some media player. I'm not sure which one is used with AVISource.

Dialhot 09-14-2003 05:50 AM

Quote:

Originally Posted by vmesquita
@Dialhot
DIvX "film effect" is not the same thing as blockbuster. It adds noise to the hole picture (not only the DCT areas),

But what do you think Blockbuster does ? Looking for DCT area before spaying its noise ? Of course not. The purpose of blockbuster is to help reducing the creation of DCT : they aren't supposed to be there when blockbuster starts its work !
Quote:

making compression very hard (I tried with DirectShowsource).
The problem can be here. Or simply the ramdomizer algorythm used in blockbuster is different from the one used in the codec. But the goal of both effects is the same.

Quote:

About the codec problem: I agree, but most people is doing only DivX AND XVid and it DivX 5 can handle DivX3 content.
You know that, I know that, a lot of people don't. They install codec via pack (nimda, ace...) that contain and install Divx 3.11, Divx 4.01 and Divx5.05 together (I really don't know why). But we can for sure give them hints about this.
Quote:

It looks like a good way to improve the source.
That's a way I tried weeks ago and decided to drop. Too blurry, whatever you do. The solution would be to have a control on the strength of each filter the codec applies. But we don't. Tell me if you find a way.
Quote:

BlindPP() produces good results but emulates a quantisizer
"BlindPP(clip, int "quant", int "cpu", str "cpu2", bool "iPP", int "moderate_h", int "moderate_v")
I will look at this.

zes 09-14-2003 06:30 AM

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.

zes 09-14-2003 07:36 AM

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:

Dialhot 09-14-2003 08:47 AM

Re: nm
 
Quote:

Originally Posted by zes
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:

Did you use the script we both blockbuster lines or only the fist one ? Because I removed the second line for my own encoding because I found one was enought, but perhaps on your very bad divx, you should try to put it again.

zes 09-15-2003 01:22 AM

this one
 
i've been using this script for a while now

Code:

#Post-Process

Blockbuster(method="noise",detail_min=1,detail_max=8,variance=0.3,seed=5823)
Deen()

GripCrop(528, 576, overscan=2, source_anamorphic=false)
GripSize(resizer="LanczosResize")

Undot()
TemporalSoften(2,7,7,3,2)
DCTFilter(1,1,1,1,1,1,0.5,0)
Blockbuster(method="noise",detail_min=1,detail_max=10,variance=0.5,seed=5623)

GripBorders()

i see you've been working on a new script, so i'm gonna give that a try now :)

vmesquita 09-15-2003 03:54 PM

@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


All times are GMT -5. The time now is 06:01 PM  —  vBulletin © Jelsoft Enterprises Ltd

Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.