z.lib resizers for AviSynth+

[poisondeathray]

Originally Posted by Myrsloik

I sure hope you benchmarked this way:

vspipe script.vpy .

And at ludicrous speeds you basically end up benchmarking very irrelevant things, like the number of calls used for writing to stdout and nothing else.

Exactly! You want to measure the pipe speed before an actual encoding application . Because that is how it would be used in real usage scenario. IMO , that is more useful information

vspipe --y4m script.vpy - | ffmpeg -f yuv4mpegpipe -i - -an -f null NUL

ffmpeg -i script.avs -an -f null NUL

[videoh]

Originally Posted by Myrsloik

You'll have a line with createfilter that looks something like this:

vsapi->createFilter(in, out, "DGSomething", init, getframe, free, fmUnordered, nfMakeLinear, data, core);

Thank you. nfMakeLinear is undefined. Do I need more recent headers?

Yes, I will export frame info.

Do I still need to do this:

muldivRational(&VI[0].fpsDen, &VI[0].fpsNum, 1, 1);

[Myrsloik]

You need newer headers and you still need to do that

[videoh]

Thanks. Working now.

[videoh]

What is the Vapoursynth equivalent of:

env->SetVar(env->Sprintf("%s", "FFPICT_TYPE"), static_cast<int>(ctype));

[Myrsloik]

Originally Posted by videoh

What is the Vapoursynth equivalent of:

env->SetVar(env->Sprintf("%s", "FFPICT_TYPE"), static_cast<int>(ctype));

If the picture type is a single char you'd do something like this:

VSMap *Props = vsapi->getFramePropsRW(Dst);
vsapi->propSetData(Props, "_PictType", &Frame->PictType, 1, paReplace);

Note that many properties have standard names and types. See this part of ffms2 for hints.

[videoh]

Thanks.

[Myrsloik]

No properties are required but a list of what you should call some things if you do attach them is here. For example all the colorpsace stuff gets used by format conversions automatically then.

You're free to make up your own properties too as long as they don't start with _.

[videoh]

Nice. Just what the doctor ordered.

[poisondeathray]

Originally Posted by HolyWu

The discrepancy with BlankClip you observed comes from the fact that, one uses direct file input while the other uses pipe. If you use ffmpeg -i test.avs -an -f null NUL you do see faster fps. But if you use avs2pipemod64 -y4mp test.avs | ffmpeg -f yuv4mpegpipe -i - -an -f null NUL you will see the same (or very close) fps compared to vpy. I don't know if pipe does cause that large overhead or it's the limitation of ffmpeg itself.

It is what we currently use. If there is overhead, than means if you use ffmpeg to encode, that overhead is currently incurred in real practice too - i.e it reflects reality. If you were to encode, say using libx264, it would be marginally slower because of that penalty

But I would like to compare "apples to apples" someday. It is a dream. Maybe with this


https://forum.doom9.org/showpost.php...6&postcount=10

maybe quote it before it might disappear

[poisondeathray]

Originally Posted by HolyWu

So, the penalty of pipe only has a significant impact when the script itself is quite fast. Otherwise in practical complex scripts, together with real encoding, it could be considered negligible.

Thanks for the testing!

It's just 1 test so far, but 4.5% faster is still significant. But when coupled with actual encoding (-c:v something), you'd expect that difference to drop more

[TheLastOfUs]

Doesn't work for me. Constantly still says no such function z_ConvertFormat. I put it under plugins+ in AviSynth+ Prog Files x86 :/

Using FFMS2 for a 4K mkv...what am I doing wrong?

[Groucho2004]

Originally Posted by TheLastOfUs

Doesn't work for me. Constantly still says no such function z_ConvertFormat. I put it under plugins+ in AviSynth+ Prog Files x86 :/

Using FFMS2 for a 4K mkv...what am I doing wrong?

Run "AVSMeter avsinfo" (or "AVSMeter64 avsinfo") and let us know if that produces any errors.
It's quite possible that you don't have the required runtimes installed.

[TheLastOfUs]

Originally Posted by Groucho2004

Run "AVSMeter avsinfo" (or "AVSMeter64 avsinfo") and let us know if that produces any errors.
It's quite possible that you don't have the required runtimes installed.

AVSMeter just crashes, assuming its flipping out because that function doesn't exist apparently.

AviSynth+ 0.1 (r1576, x86) (2.6.0.5)

Script error: There is no function named 'z_ConvertFormat'.
(C:\Users\Desktop\AVSMeter281\New File (1).avs, line 2)

[Groucho2004]

Originally Posted by TheLastOfUs

AVSMeter just crashes, assuming its flipping out because that function doesn't exist apparently.

AviSynth+ 0.1 (r1576, x86) (2.6.0.5)

Script error: There is no function named 'z_ConvertFormat'.
(C:\Users\Desktop\AVSMeter281\New File (1).avs, line 2)

1. Update AVS+ to the most recent version
2. Read my last post again - The command line should be "AVSMeter avsinfo"

[TheLastOfUs]

Ok doing so now!

[TheLastOfUs]

Didn't even REALIZE there's a most recent fork. I always just went to AviSynth+ website lol

[TheLastOfUs]

Originally Posted by Groucho2004

1. Update AVS+ to the most recent version
2. Read my last post again - The command line should be "AVSMeter avsinfo"

Updating worked. Thank you kindly!

I love avsmeter. It's amazing for diagnosis. I'm surprised I'm JUST now finding out about your tool!

[TheLastOfUs]

sOLVED!

[TheLastOfUs]

Remove!