Closed hooke007 closed 1 year ago
zlibwapi.dll
. The manual install section is updated to include download link to it. Or follow NVIDIA's documentation.And this is why I really prefer using some sorts of package manager, as the dependency chain is getting long.
No it doesn't. The same issue (Tested 1.0.0-pre4).
Could you then try loading nvinfer_builder_resource.dll
using https://github.com/lucasg/Dependencies or https://github.com/adamrehn/dll-diagnostics to see if it loads correctly?
And can you share what Windows 10 version your are on?
win10 pro 22H2 19045.3086
This looks weird, on my end it works correctly.
Do you have other plugins using CUDA loaded? What's your GPU model and NVIDIA driver version?
Do you have other plugins using CUDA loaded
No, only NNVISR with its deps is in the environment. RTX4080 studio driver 536.40
What's your Python and VapourSynth version? Can you test if it works in command line, or even better, if the conda distributed installation works?
python 3.11.4 vs R63
Hmm...Sry I don't use conda.
Well, unless adding the dir into user variable's PATH, other solutions did no help. And then I meet with the next problem...
The source clips' res are 1280x720 & 1920x1080
OK I see. It's vapoursynth's way of placing dependencies alongside plugin not conforming with default Windows library loading behavior. A fix will be available later.
And then I meet with the next problem...
Looks like you are having debug output enabled. The message amount will be overwhelming. Can you check the last non-debug messages before the error?
v1.0.0-pre5 is released which should really address this issue.
My environment has TensorRT and cuDNN under PATH for convenience, so didn't found the issue at first place. Sorry for the confusion.
Tested https://github.com/tongyuantongyu/vs-NNVISR/releases/tag/v1.0.0-pre3
It seems https://github.com/tongyuantongyu/vs-NNVISR/issues/2 hasn't been fixed. So I have to manually add the PATH and then load nnvisr. But vs still quickily crashed and I captured the last info.