At around 528x or higher, blockbuster is not needed.

-kwag

It should be used after all the temporal/spatial filters, because if not, the noise will be filtered and you don't want that :)
Put the BlockBuster filter on the last line of your script.

-kwag

Should I put it before Gripborders() or literally the last line in the script? I do notice some blockiness without blockbuster even at 528x480 resolutions, so I'm hoping blockbuster can fix it (even tho you say it's not effective at that resolution).

What exactly do you mean by this?

Yes :oops:, I should have specified that :!: Try it :) I'm just following SansGrip's recommendations, where he tested it, and came to that conclusion :cool: As above. Try it and see if it kills the blocks. Based on our previous tests, Blockbuster really is ineffective in CQ mode. Apparently, the encoder filters out a lot of the noise, and renders the filter useless. However, in CQ_VBR, it does work, but then you get worse quality on the high frequency spectrum of the encode (artifacts, etc.)

-kwag

1. Yes
2. ...
3. I use with more blocky DivX 3.11 rips.

[]'s
Vmesquita

The problem with ffdshow is that you'll have to use DirectShowSource to load the clip and thus seeking is extremely slow, making the prediction step very slow indeed. Also DirectShowSource doesn't seem to work on every system so that's another problem.

vhelp,

I was just referring to bad DivX/XviD sources in general. Low bitrates and crappy preprocessing do produce quite noticable blocks in the final video and it's sometimes very difficult to get rid of them.

Hmmmm... how about this try:

AviSource("some Southpark/Futurama/Simpsons Ep")
ConverttoYV12()
MergeChroma(blur(1.58))
MergeLuma(blur(0.05))
BlindPP()
Convolution3D(preset="AnimeLQ")
Fluxsmooth()
Warpsharp()
Undot()
Dup()
GripCrop(352, 240, overscan=0, source_anamorphic=false)
GripSize()
GripBorders()


P.S:
No blockbuster for me... Avisynth 2.52 :-(

"Razor"my friend,
:wink:

one little hint:
using resize at the end of the script can give
short final size but is extreme slow to encode!

:!:

>Real time :D
I guess I don't need resizing as these episodes already ARE 352x240 :lol:

I think I'll leave that away from no on :wink: :roll:

great,then will be faster!

:)

With last Xvid codec and Divx5.05 you do not need this ConvertToYV12() : both codec are able to provide output already in YV12. The time gain is quite big.
[/i]

Okay so I did some tests with BB and its different parameters and I've found that adding BlockBuster(method="noise", detail_min=1, detail_max=10, variance=1.0, seed=1) at the end of my script (before gripborders) does a great job in getting rid of some of the blockiness from my divx/xvid sources. This was done at 528x480 wtih CQ_VBR, but I even think it works with CQ but I'd have to go back to some of my tests to confirm this. Here's a couple questions I got for ya all:

1) Is it just me or is CQ_VBR a lot slower than CQ?

2) I'm very confused by the CQ_VBR scale. I'm encoding at CQ_VBR ~10-12. That just seems so low compared to my old CQ days! Does everything work "backwards" in the CQ_VBR world?

3) Someone else mentioned using Fluxsmooth to get rid of the divx blockiness. Could someone please shed some light on this? Is it better/faster than BB?

and last but not least

4) I've been reading stuff about how different divx codecs can slow down prediction. Like ffdshow vs divx3 vs divx5.05. If this is so which should I have? According to gspot I have about 3-4 different codecs depending on my source...

Don't bother, it's normal (except that if I remember well, I used to have a CQ_VBR near 25, and not as low as yours).

[/quote]3) Someone else mentioned using Fluxsmooth to get rid of the divx blockiness. Could someone please shed some light on this? Is it better/faster than BB?[/quote]
No, Fluxsmooth is to fix mosquitoes, not blocks.

ffdshow is a directfiltershow, not a codec and its normal to have it at the end of the rendering chain.

Morgan swither is also a directshow filter, as it DirectVobSub and DivxFreeze. I guess that you have some of these into the 3-4 you describe.

All this is normal. But the codec is always the very first element of the chain given by gspot. And that is the only one used by avisynth when you use the instruction "avisource" (you have to use directshowsource if you want to use all the filters indicated by gspot).

my friend Wilbert..

based on my divX v5.0.2 sources, your above tip WORKED !!
Colors are back to the way they are suppose to be. I'm happy :)

Thanks again pal,
-vhelp

anything new?

could someone of you, who undestands all these filters a bit give me some "general" DivX -> KVCD Script ? This would be very cool as it is much harder to get mpeg4 files to a good quality KVCD than to get DVD Files :cry:

We have done a complete thread on this subject, and found a brand new script that does great things :

http://www.kvcd.net/forum/viewtopic....455&highlight=

cool! thx!
I thougt this thread was mainly focused on the compression "blocks" of low quality divX! I guess I'll have to rad a bit in it! THX! :D

Razorblade2000,

Be sure to check the thread DialHot suggested, it does wonders to DivX sources! :D But remember that you can't get a bad quality source to produce great quality output. I would say that a 2-CD DivX source of 2 hour movie using that script can produce results close (but still inferior, and smoother) to a DVD source. But if you're dealing with a 1-CD DivX movie, the script still works great, but the quality won't be as good. Of course I am talking about quality to my eyes, might be different from yours. :wink:

<edit> the thread is mainly about the DCT blocks that appear a Lot in DivX sources (even 2 CD sources) in dark areas... The annoying "dancing blocks", as I call... I consider this the worst weekness of a DivX source. (the other weekness would be too much smoothing... But Xvid is better for this matter)</edit>

[]'s
Vmesquita

@ vmesquita :)

Is this "quaility thing" based on viewing on your PC monitor ??
Or, are you refering to how it looks viewed through a TV-OUT ??
-vhelp

vhelp,

I was refering to converting a 2-CD DivX source to KDVD using the DCT killer script. And viewing using my Philco DVP-2500 on close to a DVD backup at least for my eyes.

But you can also get good quality DivX viewing on TV-Out using a GeForce MX-200 with Svideo. But in this case it is mandatory to use post-processing and add mplayer noise on playback with FFDShow to get a good output. I used to do that all the time till I got my DVD Burner. The noise added throught FFDShow is to kill the annoying DCT Blocks.

I also tried to use Mplayer noise when encoding to KDVD but sadly it doesn't work, the noise becomes small dancing blocks in the final MPEG2 output.

When viewing on PC Monitor, DivX movies generally look great, even 1-CD rips. The DCTs become invisible, maybe because there is less contrast...

Xvid tends to smooth less the picture and retain more details.

[]'s
Vmesquita