Fixing grain and deinterlacing? (Code Geass)

[Dext3r]

ok, I'll play around with that a bit to get rid of those parts.

Still waiting to hear back from @mirkosp about the others though.

[mirkosp]

The information box you need to show us is the one of honor pulldown, as that is the reliable one.
That said, even with that forced film information, you can see it's not 100% film. 99.85% is very high though so, if at the end of the video you have something like staff credits for this particular dvd release or some studio logo, that could be what's offsetting it. Otherwise, perhaps one or two scenes might not be film, in which case I'll have to ask you whether the chroma issue you pointed out in the beginning happens all over the place or just in that specific scene.
I have to admit, though, that I find it likely that it is some sort of encoding problem either on master or on the DVD. If it's just there you might just find it easier to deal with by opening photoshop and manually fixing the frames, in case you need to use that scene in your AMV.

Now onto the other issue. As I explained, nlmeanscl uses opencl to run faster than it would on the cpu. Assuming you placed the cloo and avsfilternet .dll files in the plugins folder as well, then I'd guess that perhaps your GPU doesn't have OpenCL support (which is quite likely if you have just on-board graphics instead of a dedicated card). You could run the filter on the cpu but at that point it'd be quite slow. Since blocking is the only issue at hand, I think smoothd2 should be enough. I'd suggest properly setting the qtype value of smoothd2, btw, as that tremendously helps out the resulting efficiency of the filter.

[Dext3r]

The information box you need to show us is the one of honor pulldown, as that is the reliable one.
That said, even with that forced film information, you can see it's not 100% film. 99.85% is very high though so, if at the end of the video you have something like staff credits for this particular dvd release or some studio logo, that could be what's offsetting it. Otherwise, perhaps one or two scenes might not be film, in which case I'll have to ask you whether the chroma issue you pointed out in the beginning happens all over the place or just in that specific scene.
I have to admit, though, that I find it likely that it is some sort of encoding problem either on master or on the DVD. If it's just there you might just find it easier to deal with by opening photoshop and manually fixing the frames, in case you need to use that scene in your AMV.

Now onto the other issue. As I explained, nlmeanscl uses opencl to run faster than it would on the cpu. Assuming you placed the cloo and avsfilternet .dll files in the plugins folder as well, then I'd guess that perhaps your GPU doesn't have OpenCL support (which is quite likely if you have just on-board graphics instead of a dedicated card). You could run the filter on the cpu but at that point it'd be quite slow. Since blocking is the only issue at hand, I think smoothd2 should be enough. I'd suggest properly setting the qtype value of smoothd2, btw, as that tremendously helps out the resulting efficiency of the filter.

Oh, I didn't think about how since I use honor pulldown flags for the preview, I obviously need to use it to get the accurate results in the end too.

I have an Nvidia 480 GTX card, so I should definitely have a card that has that kind of support. So if I just use SmoothD2 and HQDering; how do I use SmoothD2 specifically then for that given it has so many parameters? Is it just something like SmoothD2(10)?

Or do I have to account for some of the others too?

[mirkosp]

Yeah your card should definitely be supported... I'll just blame it on opencl in avisynth being buggy. It's not too important anyway.
As for smoothd2, the documentation is pretty good.
As I said, the qtype parameter's pretty useful.

Qtype (1, 2, 3, 4): Quant Type. Selects the type of quant-dequant processing that is used in the filtering. They are ordered by their deblocking strength from least strong to strongest. h263 intra and h263 inter, Qtype’s 2 and 4, ignore the matrix argument and use their own built in matrix.

1. mpeg intra
2. h263 intra
3. mpeg inter
4. h263 inter
The intra in Qtypes 1 and 2 referes to the encoding done for I-Frames. The inter in Qtypes 3 and 4 refers to the encoding done for P-frames and B-Frames. See http://www.fh-friedberg.de/fachbereiche ... ginnzi.htm for a good introduction to mpeg coding. Different matrices are usually used when encoding I-Frames then when encoding P-Frames and B-Frames. All the information about how a particular frame was originally encoded, I-Frame, P-Frame, B-Frame, and Matrix value, has been lost by the time SmoothD2 is passed a frame to process, SmoothD2 does not do automatic intra-inter Qtype or matrix switching.

Generally you are supposed to manually set the qtype for the frame, but if you don't feel like spending all that effort, in the case of mpeg-2 DVDs, set it to 3 (which is mpeg inter).
That way it'll be much more effective in removing the blocking and mosquito noise at lower quant values, which is its filtering strength parameter. The default of 3 might not be enough for some of the most action intense scenes, but I really would suggest you to at least filter only those scenes at that point, since filtering clean scenes will just ruin them.
As for the other parameters, feel free to read the documentation, but I personally haven't found to be nearly as necessary and useful as these two, though I guess in some cases the matrix parameter could make wonders.

[Dext3r]

Yeah your card should definitely be supported... I'll just blame it on opencl in avisynth being buggy. It's not too important anyway.
As for smoothd2, the documentation is pretty good.
As I said, the qtype parameter's pretty useful.

Qtype (1, 2, 3, 4): Quant Type. Selects the type of quant-dequant processing that is used in the filtering. They are ordered by their deblocking strength from least strong to strongest. h263 intra and h263 inter, Qtype’s 2 and 4, ignore the matrix argument and use their own built in matrix.

1. mpeg intra
2. h263 intra
3. mpeg inter
4. h263 inter
The intra in Qtypes 1 and 2 referes to the encoding done for I-Frames. The inter in Qtypes 3 and 4 refers to the encoding done for P-frames and B-Frames. See http://www.fh-friedberg.de/fachbereiche ... ginnzi.htm for a good introduction to mpeg coding. Different matrices are usually used when encoding I-Frames then when encoding P-Frames and B-Frames. All the information about how a particular frame was originally encoded, I-Frame, P-Frame, B-Frame, and Matrix value, has been lost by the time SmoothD2 is passed a frame to process, SmoothD2 does not do automatic intra-inter Qtype or matrix switching.

Generally you are supposed to manually set the qtype for the frame, but if you don't feel like spending all that effort, in the case of mpeg-2 DVDs, set it to 3 (which is mpeg inter).
That way it'll be much more effective in removing the blocking and mosquito noise at lower quant values, which is its filtering strength parameter. The default of 3 might not be enough for some of the most action intense scenes, but I really would suggest you to at least filter only those scenes at that point, since filtering clean scenes will just ruin them.
As for the other parameters, feel free to read the documentation, but I personally haven't found to be nearly as necessary and useful as these two, though I guess in some cases the matrix parameter could make wonders.

Ok awesome, so how should I put my SmoothD2 command then? Because the first parameter is Clip or ClipZmask, so I can't just skip that one to get to the quantum?

[Dext3r]

Essentially what I'm saying is how do I just use the default value for a parameter?

[mirkosp]

Code: Select all

smoothd2(qtype=3)

By specifying a parameter's name, you can just change that one. The other parameters will retain their default value.

[Dext3r]

Code: Select all

smoothd2(qtype=3)

By specifying a parameter's name, you can just change that one. The other parameters will retain their default value.

Alright, now when I try to run HQDering, even though I made that .avsi file, it says there's no function called "Edgemask".

Am I missing something else for that one?

[l33tmeatwad]

Code: Select all

smoothd2(qtype=3)

By specifying a parameter's name, you can just change that one. The other parameters will retain their default value.

Alright, now when I try to run HQDering, even though I made that .avsi file, it says there's no function called "Edgemask".

Am I missing something else for that one?

It's part of masktools: http://avisynth.org/mediawiki/MaskTools

[Dext3r]

Code: Select all

smoothd2(qtype=3)

By specifying a parameter's name, you can just change that one. The other parameters will retain their default value.

Alright, now when I try to run HQDering, even though I made that .avsi file, it says there's no function called "Edgemask".

Am I missing something else for that one?

It's part of masktools: http://avisynth.org/mediawiki/MaskTools

Yeesh its like one problem causes another! Now its asking about a YV12Layer function, which says its contained within the Masktools, but even though I added the .dll file, that's not enough though apparently.

Do I need to extract the MaskTools folder as well?