z.lib resizers for AviSynth+

[kedautinh12]

Originally Posted by Julek

zimg is so fast on CPU (at least in vapoursynth) that I see no reason to use GPU resizer, it is more useful to leave it free for heavy denoise/eedi/nnedi.

eedi2 had cuda ver
https://github.com/kedaitinh12/Vapou...2CUDA/releases

[tormento]

Originally Posted by Julek

zimg is so fast on CPU (at least in vapoursynth) that I see no reason to use GPU resizer,

Perhaps on newer systems. Not everybody has a brand new Sapphire Rapids processor .

[kedautinh12]

Originally Posted by tormento

Perhaps on newer systems. Not everybody has a brand new Sapphire Rapids processor .

Don't need. With AMD r3 series and above, intel 8th and above. it's very fast

[tormento]

Originally Posted by kedautinh12

Don't need. In AMD r3 series and above, intel 8th and above. it's very fast

It was figurative.

[StvG]

avsresize_r20 (pass: iFmc8FTt1DsT):
- not read "_FieldBased" frame prop when use_props=0;
- added ProPhotoRGB (TomArrow).

[FranceBB]

Thanks for the new release, I'll test it when I get back to the office on February the 2nd!

[StvG]

avsresize_r21 (pass: 0RHxLfJy1t0C):
- throw error if IsFieldBased()=true and interlaced=false/use_props=1;
- resizer wrappers: added parameter interlaced;
- changed behavior of interlaced=true - previously it force use_props=0; now it doesn't have effect when use_props=1.

[FranceBB]

Ah, ok.
Upgrading now again, thanks.

[StvG]

Just to point out if it's not obvious already - after r19 you can process interlaced content without interlaced=true when use_props=0 and _FieldBased > 0 which will lead to wrong outputs. Before r20 there will be error raised that clip must be frame-based because frame prop was checked. Now (>= r20) when use_props=0, none frame prop is read. Be careful.

Again info about use_props=-1 (default value):

i. Auto use_props=0
  1. Source and destination colorspace are same (source and destination are yuv/y, source and destination are rgb)
    - colorspace_op is undefined and chromaloc_op is undefined or chromaloc_op src is not auto (chromaloc_op="left=>left")
  2. colorspace_op is defined and every src value is not auto (x:x:x:x=>y:y:y:y), and chromaloc_op is undefined or chromaloc_op src is not auto (chromaloc_op="left=>left")
ii. Every other case - auto use_props=1

You can force to read frame props by set use_props=1, or force to not read frame prop by set use_prop=0.

[FranceBB]

Yep, that's good to know and that's exactly what a user would want: use_props=0 should avoid reading any property in any case and therefore speed things up.
By the way, I am beginning to slowly try frame properties for things I don't encode manually and go through automation.
Luckily, in my case, I should be ok 'cause indexers are reading frame_properties and if there are none, they're assumed and populated by my ClipPropertyParser() for all the automated supply chains in FFAStrans, so in theory it shouldn't matter, but yeah, thanks for the heads up.

I'll come up with a report of how things went tomorrow.

EDIT: So far so good

[ErazorTT]

Would it be possible to include the 2.6 gamma to the possible transfer function which is used in st431-2 and st432-1?

[StvG]

Can you ask the zimg author (https://github.com/sekrit-twc/zimg). If he wouldn't add it, I can take a look.

[FranceBB]

Hi there guys,
I tried to compile avsresize.dll using v141_xp:




the build completed fine



and the produced dll shows no issues in Dependency Walker:




however it just won't work in Avisynth.
Is it because it's zlib being actually incompatible with XP even though it's not erroring during compilation?

Test build (link valid for 7 days only): https://we.tl/t-ZcUDEqFsZp

[real.finder]

seems _FieldBased frame property is not used to check whether the source is interlaced or not (I also tried with use_props=1 when convert from yv12 to yv24 but it kinda broken)

also can we have independent chroma subsampling parameter? for let say convert anything to 4:4:4 regardless of bitdepth to do some filtering then back to 4:2:0 or whatever original subsampling with another z_ConvertFormat() call and this is easy z_ConvertFormat(pixel_type=PixelType(orig))

[StvG]

Originally Posted by real.finder

seems _FieldBased frame property is not used to check whether the source is interlaced or not (I also tried with use_props=1 when convert from yv12 to yv24 but it kinda broken)

also can we have independent chroma subsampling parameter? for let say convert anything to 4:4:4 regardless of bitdepth to do some filtering then back to 4:2:0 or whatever original subsampling with another z_ConvertFormat() call and this is easy z_ConvertFormat(pixel_type=PixelType(orig))

About _FieldBased - did you read this post?

I'm not sure what you exactly ask about "independent chroma subsampling parameter". Can you elaborate?

[real.finder]

Originally Posted by StvG

About _FieldBased - did you read this post?

didn't read it but still with use_props=1 seems not work (avspmod will show error about not frame base)

Originally Posted by StvG

I'm not sure what you exactly ask about "independent chroma subsampling parameter". Can you elaborate?

like adding new parameter called chroma_subsampling (or any short name) that accept "444" or "422" and so as string or as int so (-1=same as input) and this will be default or (0=444) (1=422) and so on, and this parameter will be ignored if user set pixel_type

[StvG]

Originally Posted by real.finder

didn't read it but still with use_props=1 seems not work (avspmod will show error about not frame base)

Colorbars(pixel_type="yv12")
propset("_FieldBased", 1)
z_ConvertFormat(pixel_type="yv24", use_props=1)

Above code throw error - frame property is read.
Using use_props=0 doesn't throw error - frame property is not read.

[real.finder]

Originally Posted by StvG

Colorbars(pixel_type="yv12")
propset("_FieldBased", 1)
z_ConvertFormat(pixel_type="yv24", use_props=1)

Above code throw error - frame property is read.
Using use_props=0 doesn't throw error - frame property is not read.

yes but with use_props=0 will treat the yv12 as progressive when convert it to yv24 which will cause chroma Field Blending

[StvG]

Originally Posted by real.finder

yes but with use_props=0 will treat the yv12 as progressive when convert it to yv24 which will cause chroma Field Blending

use_props=0 doesn't read frame properties. You have to take care if the video is interlaced or not. If the video is interlaced use interlaced=true.

If you want the frame properties to be read (including _FieldBased) use use_props=1.

[real.finder]

Originally Posted by StvG

use_props=0 doesn't read frame properties. You have to take care if the video is interlaced or not. If the video is interlaced use interlaced=true.

If you want the frame properties to be read (including _FieldBased) use use_props=1.

I know but the problem is with use_props=1 it not same as interlaced=true
avspmod error


with interlaced=true it work fine but I need to put it inside avsi function that work with interlaced and progressive and since we got frame properties in avs+ we should rely on them especially if we have a source that got mixed interlaced and progressive frames/sections