SVP with AviSynth 2.6 or AviSynth+ ? (Page 2 of 5)

I tried it but get an error that SetFilterMTMode doesn't exist.

Now I get what you're saying that MT isn't in the official AviSynth+ build... so where do I get the MT version then? I searched for it and can't find a MT version of AviSynth+

Oh it doesn't even have a compiled version! Thanks, I really wasn't interested in compiling it myself.

So far it's working, with memory usage between 600-1000MB (similar to 2.5.8)

There might be a slight additional lag when initializing videos.

Anything I should pay attention to when testing it?

The main problem with 2.5.8 MT is that especially when controlling MPC-HC via API, it crashes very regularly and I need to scan the process every few seconds to detect a crash to auto-kill the process.

One question about SVP... if I wanted to patch 'generate.js' during setup, is there a way for me to programmatically know in which folder SVP was installed? MPC-HC has a registry key with its installation path, but I haven't found anything to indicate SVP's location.

And another quick question (perhaps off-topic): when using SVP with Interframe, what happens if I always specify to use the GPU and it runs on a computer that doesn't support it?

Mystery
with memory usage between 600-1000MB (similar to 2.5.8)

similar to 2.5.8 "SVP build"

Anything I should pay attention to when testing it?

memory leaks especially after script reloading
MT efficiency (how many threads're required to achieve "SVP index" = 1) (more threads => more memory consumption)
overall stability

The main problem with 2.5.8 MT is that especially when controlling MPC-HC via API, it crashes very regularly

I really have no idea how you make it happen. In a real life it doesn't crash at all unless you start seeking the video.

is there a way for me to programmatically know in which folder SVP was installed?

may be via uninstallation path?

what happens if I always specify to use the GPU and it runs on a computer that doesn't support it?

AVS script will give an error

I tried using this build of AviSynth+ MT for encoding videos with EEDI3+NNEDI3, and am getting about 3-4% lower performance than with the official build.

Not my fault    Building AVS+ is extremely straightforward - like opening the solution and pressing "Build" button.
May be MT branch doesn't incorporate ALL commits to the main one...

Here's another test with a different script.

AviSynth+ (non-MT): 6m21

PluginPath = "Encoder\"
AviSource("Job2_Input.avi", audio=false).ConvertToYV12()
LoadPlugin(PluginPath+"FFT3DFilter.dll")
fft3dfilter(sigma=3, bt=5, bw=48, bh=48, ow=24, oh=24, ncpu=8)
LoadPlugin(PluginPath+"nnedi3.dll")
nnedi3_rpow2 (2)
nnedi3_rpow2 (2)
Spline36Resize(960, 720)
fft3dfilter(bt=-1, sharpen=0.1, ncpu=8)

AviSynth 2.6 MT: 5m36

SetMTMode(3,4)
PluginPath = "Encoder\"
AviSource("Job2_Input.avi", audio=false).ConvertToYV12()
SetMTMode(2)
LoadPlugin(PluginPath+"FFT3DFilter.dll")
fft3dfilter(sigma=3, bt=5, bw=48, bh=48, ow=24, oh=24, ncpu=8)
LoadPlugin(PluginPath+"nnedi3.dll")
nnedi3_rpow2 (2)
nnedi3_rpow2 (2)
Spline36Resize(960, 720)
fft3dfilter(bt=-1, sharpen=0.1, ncpu=8)

That "thing" (2.6 MT) is actually doing quite well (besides memory usage).

If you can tell me what's wrong with my AviSynth+ MT script, I'll give it another try.

Mystery

I think you need to overwrite second line:

Looks like MultiThreading is not working. MT result similar to ST result (SingleThreading).

You need to add line

Distributor()

to the end of scriprt to make MT working.
* For AVS+ last line of script must be:

Prefetch([threads_number])

What mean clock deviation and how it related to AVS-script or Avisynth library version?

Mystery
This "thing" (AviSynth+ MT) is far from being a finished product...

You've just opened my eyes 

Nevetheless this's the only chance to get SVP in x64 players...

https://forum.doom9.org/showthread.php?p=1697689

Now I did the SVP/Interframe encoding test with AviSynth+ MT. I've set the threads to 14 as that's the default in generate.js for 8 CPU + GPU.

It worked fine and performance is impressive: 31s! (compared to 41-25s with v2.5.8)

What causes massive visual glitches is resizing. A script with a simple Spline32Resize causes problems; so does NNEDI3 resizing.

Bugs so far:
- AviSynth+ MT doesn't work with resizing
- It crashes when closing
- Drop frames / clock desync problem

With v2.5.8 / v2.6 I don't need to enter Prefetch(14) because InterFrame takes care of it. If I specify Prefetch on top of what Interframe does, am I duplicating the thread creation?

The performance, however, looks very promising!!

I believe that getting AviSynth+ MT to work properly, combined with processing frames *after* madVR, would allow for much better output quality (drastically improved performance, but would have to be tested)

Denoise/Sharpen with FFT3DFilter is working (not crashing). Keep in mind that there may be all kinds of subtle bugs that change the output quality and are hard to see.

Just looking at the file size (twice bigger than 2.5.8), I'm not sure I want to look at it.

It's definitely not working with resize functions. Just create a basic script that has a Spline32Resize function and it has lots of serious visual glitches.

I get what you're saying... and perhaps your time is better spent working on SVP itself while you let others figure out AviSynth MT. That's a WHOLE other project in itself.

Now it's working with either v2.5.8 or v2.6. Perhaps you could give the option during installation as to which version to use. I'd probably recommend v2.6 if they have over 3GB of RAM.

If they want SVP to work in x64, then someone will have to first make a proper AviSynth MT work in x64 first. THEN you can rewrite your assemblies in x64. But for now, most video components are still working in x86. Might be different a few years from now.

When I was looking into testing x64 AviSynth, the people in the community were under the impression that you weren't interested in providing a x64 version of SVP. That's not actually the case. You want to support that, but there just is no version of AviSynth that supports x64, MT and ffdshow. You just have to let them know that. As soon as any version supports x64, MT and ffdshow, you'll be more than happy to provide x64 SVP binaries for it. Until then, there's no point in spending time there.

You know what funny thing and sad joke is? That with those memory leaks anf 8GB onboard I can say "Well, FINALLY that RAM I payed for is used somewhere!"
Actually I have never known about them.
You should patch player's exe with 4GB patch.
I saw no bugs except 1 isolated in PotPlayer with disabled video processing option. My encoders use the AVS which came with them.
Clock deviation... have you ever thought it shoul be normal due to 59.937 fps ntsc (or whatever standard) being played on 60HZ monitor? Wait... maybe it's vice versa, your monitor's refresh rate is 59.9 instead of 60?

Chainik, Always read your nick as Chainlink until I followed github link)

I also tried Avisynth 2.6 MT with MPC-HC 1.7.7 on Windows 7 for watching videos
and have no crashes anymore on seek and no memory problems 
So good idea to use that!

will wait there for MT-enabled version...