DGDecNV and KNLMeans under Win10_x64

[sparktank]

KNLMeansCL just got updated again, with enhanced error logs.
https://github.com/Khanattila/KNLMeansCL/releases

Maybe try again to see if it gives more details.

Have you tried re-installing NVidia drivers? "Fresh" install ?

I can't think of much for Nvidia + Win10.
Other than some DX9_interop was droppped, used in NNEDI3 (MadVR).
But not sure what could affect OpenCL.

Maybe create a new thread in Doom9 inquiring others that use Win10 what they're experience with Win10+OpenCL would be for NVidia.
Perhaps, there's an older driver or newer beta driver that works with OpenCL+KNLMeansCL.

[Guest 2]

KNLMeansCL just got updated again, with enhanced error logs.

Yes, 0.6.2, no way.

Have you tried re-installing NVidia drivers? "Fresh" install ?

Tried even developer one.

Other than some DX9_interop was droppped, used in NNEDI3 (MadVR).

No use for me.

Maybe create a new thread in Doom9 inquiring others that use Win10 what they're experience with Win10+OpenCL would be for NVidia.

OpenCL works perfectly, even with very heavy benchmarks. It's the binning with DGDecNV that gives me problems.

Neuron2, where are you? Any time for some testing?

[Guest 2]

With this script:

Code: Select all

SetMTMode(5)
SetMemoryMax(2048)
LoadPlugin("D:\eseguibili\media\DGDecIM\DGDecodeIM.dll")
DGSourceIM("E:\in\1_46 Don Camillo\camillo01.dgi",engine=1)
ChangeFPS(last,last,true)
crop(244, 0, -244, -8)
SetMTMode(2)
SMDegrain (tr=6,PreFilter=4,thSAD=400,contrasharp=false,refinemotion=false,plane=4,chroma=true,lsb=true,mode=6)

I get this



With this even simpler one:

Code: Select all

LoadPlugin("D:\eseguibili\media\DGDecNV\DGDecodeNV.dll")
DGSource("E:\in\1_46 Don Camillo\camillo01.dgi")
crop(244, 0, -244, -8)
KNLMeansCL(device_type="GPU", info=true)

I get green preview with CUDA ERROR! text in upper left corner.

[sparktank]

Ah, forget the clean install I asked on doom9.

What a curious case!

Have you tried to re-download DGdecNV ?
When updating, are all files replaced or just a few?

[admin]

@Guest 2

Sorry to report that everything works fine for me with this script:

loadplugin("dgdecodenv.dll")
loadplugin("knlmeanscl.dll")
dgsource("alba.dgi")
KNLMeansCL(device_type="GPU", info=true)

I have 64-bit everything on Win10. I use Avisynth+ r1825. GT 220 GPU. nVidia driver 341.81.

Did you notice that the blurb for KNLMeansCL says MT versions of Avisynth are not recommended?

[Guest 2]

@Guest 2

Sorry to report that everything works fine for me with this script:

loadplugin("dgdecodenv.dll")
loadplugin("knlmeanscl.dll")
dgsource("alba.dgi")
KNLMeansCL(device_type="GPU", info=true)

I have 64-bit everything on Win10. I use Avisynth+ r1825. GT 220 GPU. nVidia driver 341.81.

Did you notice that the blurb for KNLMeansCL says MT versions of Avisynth are not recommended?

Is there some debug info I can send you?

[Guest 2]

I read in Blender forums that other people are having CUDA errors in Win10.

Blender uses CUDA 6.5, but it does not support win10 officially.
CUDA Toolkit 6.5
win10 should be supported by CUDA7.5RC.
nVidia Developer Zone

It does not think it's strange even if an error occurs in my opinion.

I put my Win8.1 disk back, same encoding configuration, and everything works OK.

I dunno if Nvidia is aware of these problems.

@Neuron2:

1) could you please ask your Nvidia insiders about Win10 CUDA or memory management?
2) I read you are using AviSynth+. Any problem with standard AviSynth?

[admin]

When nVidia releases a CUDA version that claims win10 support, I will upgrade to it. A problem I foresee is that likely earlier cards will no longer be supported. I have complained to nVidia about this and I don't want to maintain multiple versions so I don't know what will happen.

I am using 64-bit stuff. Does plain vanilla Avisynth have a 64-bit version?

Please provide links to the Blender postings of interest.

[Guest 2]

When nVidia releases a CUDA version that claims win10 support, I will upgrade to it.

Neither for a test version?

I am using 64-bit stuff. Does plain vanilla Avisynth have a 64-bit version?

Only fork and very old ones. AviSynth+ does but it's bugged as hell.

Please provide links to the Blender postings of interest.

https://developer.blender.org/T45987

In the meanwhile I am using DGDecIM but on a i7-2600k is slower than DGDecNV and the avs script runs at 5fps instead of 8fps.

[admin]

@Guest 2

I made a 64-bit test version with CUDA 7.5 for you. Please tell me the results.

http://rationalqm.us/misc/Guest 2_64.zip

[admin]

Did you lose interest in this problem?

[Guest 2]

@Guest 2

I made a 64-bit test version with CUDA 7.5 for you. Please tell me the results.

http://rationalqm.us/misc/Guest 2_64.zip

I'll do a try with that ASAP.

I didn't lose interest, I had to work for 12 hours every day on last friday, saturday and sunday to solve a bad work problem.

As I wrote on doom9, my current encoding pipeline is 32bit, I need that version if possible

Thanks for your work.

[admin]

http://rationalqm.us/misc/Guest 2_32.zip

[Guest 2]

http://rationalqm.us/misc/Guest 2_32.zip

As I wrote on Doom9, tried DGDecNV with another OpenCL plugin named nnedi3ocl however it's so old I can't set OpenCL GPU priority.

If I remove Intel GPU from bios and leave Nvidia only, it simply doesn't work, even with sw decoding.



Now I'm going to install Nvidia developer drivers with Windows 10 and OpenCL extension support.

Edit: neither developer 355.97 does the magic. KNLMeansCL works perfectly without DGDecNV.

[admin]

"KNLMeansCL works perfectly without DGDecNV"

And DGDecNV works perfectly without KNLMeansCL?

For my system, they both work perfectly together.

Windows 10 64-bit
DGDecNV 2049 64-bit
KNLMeansCL 64-bit 0.6.2
GeForce GT 730
OpenCL 1.2
CUDA 355.82
Avisynth+ r1825

[Guest 2]

And DGDecNV works perfectly without KNLMeansCL?

For my system, they both work perfectly together.

Windows 10 64-bit
DGDecNV 2049 64-bit
KNLMeansCL 64-bit 0.6.2
GeForce GT 730
OpenCL 1.2
CUDA 355.82
Avisynth+ r1825

The answer is yes on 32bit.

Your system is working on 64 bit, I just have to try 64 bit but I suppose you could be faster as I have to understand how to use AviSynth+ on 64bit without messing things up.

[Guest 2]

I was looking for x64 encoding alternatives.

Look at latest threads of http://forum.doom9.org/showthread.php?t=172068&page=29, there are some problems with Windows10 and DGDecNV.

Can you please tell me the easiest way to test x264 encoding in x64 environment?

[admin]

Look at latest threads of http://forum.doom9.org/showthread.php?t=172068&page=29, there are some problems with Windows10 and DGDecNV.

You jump to conclusions! I could equally say "problems with Windows 10 and staxrip".

Can you please tell me the easiest way to test x264 encoding in x64 environment?

Install Avisynth+ and then use a 64-bit version of x264.exe. BTW, there is a great thread on Doom9 about switching Avisynth versions back and forth easily.

Somehow I doubt all this will make a difference but certainly try it if you like.

[admin]

Agreed. On the other hand, it may be a useful heuristic to try to get someone to look into the issue, especially when everyone is pointing fingers at each other.

[AJR]

Can you please tell me the easiest way to test x264 encoding in x64 environment?

All you have to do is install AVS+ from here:
http://www.avs-plus.net/

This build (r1576) is the most stable, I would not recommend r1825. Then you can use DGIndexNV/DGDecodeNV/x264, all 64 Bit.

May I know why exactly you dont recommend r1825? Whats wrong with this version? Authors of Avisynth+ recommends r1825 as the most stable "single threaded" solution, MT is marked as unstable.

[AJR]

I dont use QTGMC so I dont understand why it is so important to say dont use r1825 in general. I am using hw deint via VP6. I dont see such slowdown between r1576 and r1825. Did you find anyone else who has confirmed general slowdown?

I cannot find recommendation for r1825. So maybe I was not remembered well. But I am sure I have read a post that r1825 in sigle threaded processing is working at least the same well as r1576. If you want I can edit my previous post and delete the sentence about recommendation

[jpsdr]

I dont use QTGMC

QTGMC is just used here as test to show a potential global/general issue, not something specific to QTGMC.

[admin]

Didn't someone identify the commit that caused it? If so, why can't we have a fixed version pronto?

[admin]

Have the original developers abandoned Avisynth+? We now have random people trying to hack away on it?

[Guest 2]

Could you please put version 2049 instead of test in the test builds?

Otherwise staxrip can't recognize them