Filtering help needed

[poisondeathray]

And if you can't find a good combination of settings that works on everything, then another option is to use a manual override file

[x264]

could you show me how it's done? Do i need to note down the combed frames in a notepad?

[poisondeathray]

could you show me how it's done? Do i need to note down the combed frames in a notepad?

Yes you do . There are examples in the instructions. Use a "+" to indicate combing

TFM(ovr="override.txt")

eg
60,80 + will force frames 60 through 80 to be considered combed

[x264]

So it should be like this

440,460 +
670,690 +
....
....

[manono]

Or forget the override file and add in Vinverse after the IVTC to clean up any leftover stray interlacing. It usually does a pretty good job of it.

[x264]

Ok.

[x264]

Can NNEDI3 be used to downsize?

[Selur]

No.

nnedi is an intra-field only deinterlacer. It takes in a frame, throws away one field, and then interpolates the missing pixels using only information from the kept field. It has same rate and double rate modes, and works with YUY2 and YV12 input. nnedi can also be used to enlarge images by powers of 2.

source: http://web.missouri.edu/~kes25c/
-> doesn't make any sense trying to use it for downsizing,...


for the fun of it look at:

big = ImageSource("Testkiste_gesamt_400.jpg", end=250).convertToYuY2()

b1 = big.BicubicResize(1280,854).meInfo("Bicubic")
b1 = big.BilinearResize(1280,854).meInfo("Bilinear")
b3 = big.BlackmanResize(1280,854).meInfo("BlackmanResize")
b4 = big.GaussResize(1280,854).meInfo("GaussResize")
b5 = big.LanczosResize(1280,854).meInfo("LanczosResize")
b6 = big.Lanczos4Resize(1280,854).meInfo("Lanczos4Resize")
b7 = big.PointResize(1280,854).meInfo("PointResize")
b8 = big.SincResize(1280,854).meInfo("SincResize")
b9 = big.Spline16Resize(1280,854).meInfo("Spline16Resize")
b10 = big.Spline16Resize(1280,854).meInfo("Spline36Resize")
b11 = big.Spline64Resize(1280,854).meInfo("Spline64Resize")
b12 = big.GaussResize(1280,854,p=75).meInfo("GaussResize")

return Interleave(b1,b2,b3,b4,b5,b6,b7,b8,b9,b10,b11,b12)

function meInfo(clip a, string b){
    return a.AddBorders(8,8,8,8,color=$FFFFFF).Subtitle(b,align=8,font="kroeger 08_53",size=12,text_color=$000000,halo_color=$FFFFFF)
}

with the attached image to see the differences of different resizers when downsizing (feel free to adjust the script to your needs)

[x264]

Which field does it throw away?

[Selur]

from the documentation of nnedi3:

field -

Controls the mode of operation (double vs same rate) and which field is kept.
Possible settings:

-2 = double rate (alternates each frame), uses avisynth's internal parity value to start
-1 = same rate, uses avisynth's internal parity value
0 = same rate, keep bottom field
1 = same rate, keep top field
2 = double rate (alternates each frame), starts with bottom
3 = double rate (alternates each frame), starts with top

If field is set to -1, then nnedi3 calls child->GetParity(0) during initialization.
If it returns true, then field is set to 1. If it returns false, then field is set to 0.
If field is set to -2, then the same thing happens, but instead of setting field to 1
or 0 it is set to 3 or 2.

Default: -1 (int)

Also see the edit I did on my last post.

[poisondeathray]

Which field does it throw away?

the opposite one to whichever one you tell it to keep

[x264]

suppose i make two deinterlaced clips, for one of them i throw away the odd fields and for the other i throw away the even fields. Will there be any visual difference between the two?

[Selur]

Will there be any visual difference between the two?

sure, since the upper and lower field of a clip differs, there should be differences

[x264]

Does raising the no. of bframes increase compression?

[jagabo]

Does raising the no. of bframes increase compression?

Depends on whether you're using CRF or bitrate based encoding.

[x264]

I'm using CRF based encoding.

[Selur]

also the benefit of using B-Frames shrinks with their number increasing, especially since more than 6 B-frames are rarely used.

[x264]

do i need to set the --colormatrix option in x264 or will it automatically set it for me?

[Selur]

you have to set it if you want it

[x264]

When i preview a DVD in DGIndexNV the calorimetry is BT 601. should i set --colormatrix as bt601 in x264?

[Selur]

a. unless you change the color matrix through Avisynths ColorMatrix-function you should set the "--colormatrix"
b. there's no '--colormatrix bt601', x264 only offers:

      --colorprim <string>    Specify color primaries ["undef"]
                                  - undef, bt709, bt470m, bt470bg
                                    smpte170m, smpte240m, film
      --transfer <string>     Specify transfer characteristics ["undef"]
                                  - undef, bt709, bt470m, bt470bg, linear,
                                    log100, log316, smpte170m, smpte240m
      --colormatrix <string>  Specify color matrix setting ["???"]
                                  - undef, bt709, fcc, bt470bg
                                    smpte170m, smpte240m, GBR, YCgCo

source: x264 --fullhelp
colormatrix related options -> you might want to read the documentation of Avisynths ColorMatrix and http://forum.doom9.org/archive/index.php/t-157299.html to get a better understanding on what to set when.

[jagabo]

Does raising the no. of bframes increase compression?

I'm using CRF based encoding.

It will give you more compression (smaller files) but lower quality. Because b-frames are encoded with higher quantizers. Going over 3 or 4 b-frames gets only a tiny bit more compression with most material, tenths of a percent. Blu-ray players cannot handle more than 4.

[x264]

Is it necessary to resize after cropping of the black bars of an NTSC 720x480 DVD?

[poisondeathray]

Is it necessary to resize after cropping of the black bars of an NTSC 720x480 DVD?

No, you can encode with AR flags

Or you can resize using square pixels

[x264]

Will all sources exhibit banding when overdenoised?

[poisondeathray]

Will all sources exhibit banding when overdenoised?

Not necessarily . Only content that predispose you to banding e.g. gradients

[Selur]

Sure with enough denoising, you will end up with a lot of color gradients which will cause banding unless a dithering is or a higher precision than 8bit is used.

---
poisondeathray was faster and the funny thing is we are both right

[x264]

Could you explain what a gradient is?

[Selur]

color gradient = interpolation steps / transition between one color and another, simply google for color gradient and look at the picture results and you should see some results with smooth transition and some with visible steps (banding)

[sanlyn]

Could you explain what a gradient is?

Examples of smooth gradients and banding - Lagom LCD test patches: http://www.lagom.nl/lcd-test/gradient.php