[RESOLVED] Applications hanging when using extra AVS plugins that depend on GPU

[sparktank]

Hello.

Windows 10 Pro, x64
AVSPlus_86, r2347
GeForce GTX 750 Ti
Driver: R376.19 (r376_06-6) / 21.21.13.7619 (12-1-2016)
DGdecNV, latest slipstream

Issue:
Whenever I use DGSource() as the source filter on any MKV file (regardless of format), it works fine until I use an external AVS plugin that depends on using the GPU (KNLMeansCL, SVPFlow, etc) and then the application hangs. AvsPmod, VirtualDub, AvsMeter, etc.

Something simple as any version of KNLMeansCL will cause apps to hang.

Using a simple script on any source file with just DGSource called will work.

Working:

Code: Select all

LoadPlugin("path\DGdecodeNV.dll")
DGSource("source.dgi") #mkv, 1080p bluray remux, avs, 23.976, progressive

But then using something like this...

Hangs:

Code: Select all

LoadPlugin("path\DGdecodeNV.dll")
LoadPlugin("path\KNLMeansCL.dll")
DGSource("source.dgi") #1080p bluray remux, avs, 23.976, progressive
KNLMeansCL() #default settings

Using FFMS2 and DSS2 will allow me to use other plugins that depend on GPU usage.

What I've tried:
Uninstalling Avisynth+, SVP, K-Lite Codec Pack, NVidia drivers (all with Revo Uninstaller).
And then re-installing the above. Except, I don't use KLCP anymore. I just install the programs separetely.
I've also uninstalled Intel OpenCL entirely so it's just Nvidia's OpenCL.
I've even tried using older NVidia drivers but don't know how far back to go as they're all mostly "Game Ready" with no real input on what's changed as far as video goes.
I've also removed plugins from the autoload directory so I have call plugins in the script.
I've scanned and checked for duplicate files to prevent any conflict.
I've also installed as many MSVC runtimes I can using a nifty all-in-one.

What I use:
I use Avisynth installer batch to install AVSPlus_86 in a separate location.

I also use the latest dev builds for AVS+

Troubleshoot:
I've asked for assistence already from Mr Admin and the issue is definitely on my end.
So it's not any of the plugins.

Possibilties:
Need to use a much older NVidia driver?
Graphics card dying?
Power supply dying?

Suggestions? Input?
Anyone else experience similar problems?

It seems to only happen when more than one plugin wants to work with the GPU.

Maybe I should power down, unplug it all and take out the card and give it a good dust off with an air can?

I have a really old and smaller card I can try.
I think it's a Zotac in the 500/600 series.

[admin]

It's a known issue for Win10. The only way to make it work is to use 64-bit everything: DGDecNV, Avisynth, and all plugins.

I'll add a note about this to my release notes.

[sparktank]

Gah! I see now!

It's been quite awhile since I've used KNLMeansCL, so it finally caught up to me.

Thanks for the info!

I'll adjust my setup to use x64 AVSPlus if I want to use both.

I believe that SVP also allows for x64 use, so I'll install their x64 libraries as well.

I only discovered this recently, as using SVP while watching movies, it uses FFDShow_source() so it went largely under the radar until I tried to encode a clip to 60fps using DGSource().

Thank you thank you!

Welp, time for my first cup of coffee and get cracking on using x64.

[admin]

Good luck and please report your results.

Be aware that there is technology for easily switching between Avisynth+ 32-bit and 64-bit. There are several ways to do it. If you do not use the plugin directories, it's particularly easy because you do not have to touch the registry. That's how I do things.

[admin]

That's peachy keen.