AviSynth Filter Incompatability...? Cnr2 + Guava/Dup/VagueDenoiser...

[nbarzgar]

Hello,

I tried several times to load the following script (all this for anime-capture PicVideo mjpeg>mpg2-conversion)
AviSource("D:\Path\to\X.avi")
Trim(0,112921)
ConvertToYUY2()
GuavaComb(Mode="PAL",Recall=80,MaxVariation=25,Activation=30)
ConvertToYUY2()
Cnr2()
Dup()
VagueDenoiser(threshold=4,method=1,nsteps=6)
into CCE (2.67) or Canopus 2. Both crashed on me. I tried different combinations, using #.

Only when I removed the Cnr2+ 2nd ConvertToYUY2(), it worked. Before CCE also showed the duration of the file incorrectly as being 10 sec., "trims" active or not.

In the early stages I hadn't included the second ConvertToYUY2() in the script, but it made no difference with the crashing issue.
Removing (s.a.) Cnr2 did the trick... I tried to put it somewhere else in the script, to no avail.

Can anybody tell me the reason for this?

[Chainmax]

I don't know, but I'd advice you to ditch GuavaComb and CNR2 for DeDot() and FFT3DFilter(sigma=3,plane=3,bw=32,bh=32,bt=3,ow=16,oh=16) respectively.

[Boulder]

The version of CNR2 you use is broken but I'd follow the route Chainmax pointed to you anyway.

[nbarzgar]

Thanks for the good advice! :thanks:

@Chainmax: Do you mean UnDot() ? Can't find DeDot()... :confused:

@Boulder: I downloaded the .dll for Cnr2() again, put it into plugin-directory, no crashes now, but will follow chainmax's suggestion anyway.

Would you advice to use this combination on anime-captures generally (with different values depending on source-material) and/or drop Cnr2() for good...Or just use it on movies?

EDIT: FFD3DFilter throws an error on the "plane"-value, should be 0,1,2 - changed that in my script, looks as follows:

AviSource("....avi")
Trim(0,112921)
ConvertToYUY2()
FFT3DFilter(sigma=3,plane=2,bw=32,bh=32,bt=3,ow=16,oh=16)
UnDot()
Dup()
VagueDenoiser(threshold=4,method=1,nsteps=6) EDIT

[foxyshadis]

@Chainmax: Do you mean UnDot() ? Can't find DeDot()... :confused:
No, you could use search. They're very different, but the more readily available TComb will also work and probably be faster.

EDIT: FFD3DFilter throws an error on the "plane"-value, should be 0,1,2 - changed that in my script, looks as follows:
Geez, update, your version must be ancient. All your plugins seem to be. It's a good idea to try updating whenever a suggestion doesn't work instead of hacking at it.

For one, plane=2 means apply only to the second chroma plane, which is pretty useless. 4 means apply to all 3 planes.

[nbarzgar]

I checked with my plugin-directory and you're right, some of them ARE ancient. :(

Sorry, will try to alter that. But the FFD3DFilter I only got today from Avisynth.org/warpenterprises...and the .dll-file's got change-date of 2004...

Well, anyway, will try and search for the latest versions. Is it a better idea to look for them on this forum??

[Chainmax]

DeDot_YV12 (http://nullinfo.s21.xrea.com/#DeDot_YV12).

FFT3DFilter (http://avisynth.org.ru/fft3dfilter/fft3dfilter.html).

[nbarzgar]

Thanks, had found them in the meantime. FFD3DFilter throws the error still, although I have apparently the latest version available.

@foxyshadis: What's that about the two planes, could you explain that a bit more lucidly for non-experts? You mean the U and V information...?

[Daodan]

About FFT:


Filter uses fast external FFTW library version 3 (http://www.fftw.org)
as Windows binary DLL (compiled with gcc under MinGW by Alessio Massaro), which support for threads and have AMD K7 (3dNow!) support in addition to SSE/SSE2.
It may be downloaded from ftp://ftp.fftw.org/pub/fftw/fftw3win32mingw.zip
You MUST put FFTW3.DLL file from this package to some directory in path (for example, C:\WINNT\SYSTEM32).
Filter will NOT work without it!

It's from the documentation...usually the first thing you should read.

[nbarzgar]

Right, absolutely, and it also says:

To denoise all color planes (both luma and chroma)

Note: The processing speed will be decreased more, so you can consider other (simpler and faster) filters using for chroma denosing (CNR2, DeGrainMedian, etc).

I skip the descriptions of filters sometimes, because in many cases they explain things on a level that I cannot understand, since I would need to know more about basic concepts of digital picture/frame/field-storage etc. and I just now have only got the time for a - more or less clever - usage of it all.

That's why I asked for a simple explanation for non-experts...

[foxyshadis]

If you want to be able to use AVISynth effectively it really helps to know some of the theory, otherwise you'll get lost and beg for help too often.

Anyway, Y (or luma) is the brightness channel; alone, it's a greyscale image of your video. UV (or chroma) are the color channels, which mix to define all the colors to fill in Y. You almost always treat U & V as one, unless you're correcting one's color/saturation, so plane=1 or 2 (or masktools' u and v params) are pretty useless.

There's a lot of gotchas in converting colorspaces which you should read about in the manual, even if you only convert on playback.

Also, even if you get something from WarpEnterprises make sure you follow any links in the documentation to find possible newer versions. As you saw, they can be pretty behind sometimes.

[nbarzgar]

Thank you a lot!

It's not that I never read up on the theory, don't get me wrong. But looking at catchwords and 'headlines' of FFD3DFilter intimidated me in the abovementioned way... :(

Anyway, will follow all the good advice and especially look out for the links, i.e. the latest versions. By now I have two versions of the encoded .avi (=mpeg2 now), one with the script I created myself, the other with given changes.

Both are great, the second version (incl. FFD3DFilter ) took about 8.5 hours to encode, the first 5.5 hrs. I'd like to finish this project soon, but with my own script I included cropping in the last version of it and forgot the resizing. :angry:

Now I will try to use both in a test DVD (using the 'patch'-work-around on the smaller clip) and decide, if I have to encode a third time...with all proper filters, cropping * and resizing set. :D

______________________________
* very annoying, rather noticable white horizontal stripe, being reflected on TV screen at the top of the clip, I would not bother otherwise, since I know that resizing will lose data on the "way"

[nbarzgar]

Have to correct myself: there is a definite difference between the two versions!
The one including FF3DFilter shows by far better on the TV screen! The picture is clean, has depth (!) and the colors are defined and 'lively'!

Thank y'all again!