Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
|
|
Thread Tools | Search this Thread | Display Modes |
1st September 2015, 11:28 | #322 | Link |
Registered User
Join Date: Nov 2014
Posts: 440
|
v0.6.1 release: https://github.com/Khanattila/KNLMeansCL/releases.
It corrects an error that I had introduced in the previous version.
__________________
github.com |
2nd September 2015, 20:16 | #325 | Link |
Registered User
Join Date: Aug 2009
Posts: 463
|
Same here. I use it with StaxRip x64 and Avisynth+. Same error with 0.6.0. Builds up to 0.5.9 work just fine.
__________________
Intel Pentium G3220, Asus H81M-K, 4GB DDR3@1600MHz (1333MHz working), LG W1934S, Windows 8.1 Pro x64 |
2nd September 2015, 20:24 | #326 | Link |
Soul Architect
Join Date: Apr 2014
Posts: 2,559
|
I'm using AviSynth 2.6
Also, KNLMeans is giving me better results than FF3DFilter on most videos, but why is it giving me such bad output on this video? The lines in the background end up being very jerky (I know, the source video is bad quality), but FF3DFilter is doing a MUCH better job in this particular case. In most other videos with similarly bad quality, however, KNLMeans gives a better output. Here's the video https://mega.nz/#!CNICBS5S!56wGjk8gt...k4ms8mPXFr0nkY KNLMeansCL(D=2, A=1, h=3, device_type="GPU")
__________________
FrameRateConverter | AvisynthShader | AvsFilterNet | Natural Grounding Player with Yin Media Encoder, 432hz Player, Powerliminals Player and Audio Video Muxer Last edited by MysteryX; 2nd September 2015 at 21:07. |
3rd September 2015, 00:41 | #327 | Link |
47.952fps@71.928Hz
Join Date: Mar 2011
Posts: 940
|
Win7 (x64) SP1
GTX 750 ti GeForce 355.82 (newest; although I don't think much changed as far as video processing goes, mostly just new games) KNLMeansCL v0.6.1 Code:
SetMemoryMax(512) LoadPlugin("C:\AVS\dgdecnv2049\DGDecodeNV.dll") DGSource("E:\Demux\Scream\Scream.dgi", crop_b=140, crop_t=132) #KNLMeansCL(D=2, A=1, h=3, device_type="GPU", info=true) I don't see "jerky lines" in the sample video. I grabbed a demux of the poorly mastered BD for Scream, since it's noisy and messy. (Canadian BD Region A, identical to USA BD) (all images are "large thumbnail", click to follow to original size (1920x816) Here's original Frame #7282: Focus: the white door frame behind Drew Here's with the settings used by MysteryX: KNLMeansCL(D=2, A=1, h=3, device_type="GPU", info=true) Focus: the white door frame behind Drew Looks it denoises a lot of the main flat areas, but any edges are nearly the same. When you scan forward, you can see this jerkiness it produces to due to unfiltered edges. Some frames, the edges are cleaned out right. And a large portion of (proceeding) frames, the noise varies, giving it a jerky look when played back. At those setings. Here's same settings, an earlier frame where the door frame is entirely denoised and clean edges. Frame #7275: Frame #7276 is pretty clean too. From there, it starts to degrade back to a noisy edge. BUT I changed parameters and found this: Frame #7313 KNLMeansCL(D=3, A=0, h=3, device_type="GPU", info=true) Jerky-ish lines. Are those the kind of jerky lines you got? I couldn't get those lines on the sample video with previous settings. I haven't checked with new settings to see if jerky lines appear.
__________________
Win10 (x64) build 19041 NVIDIA GeForce GTX 1060 3GB (GP106) 3071MB/GDDR5 | (r435_95-4) NTSC | DVD: R1 | BD: A AMD Ryzen 5 2600 @3.4GHz (6c/12th, I'm on AVX2 now!)
|
3rd September 2015, 04:46 | #328 | Link |
I'm Siri
Join Date: Oct 2012
Location: void
Posts: 2,633
|
Quote:
and the jerky lines are just common motion flow artifacts solution: enable spatial processing, pick an A value greater than 0 |
3rd September 2015, 09:44 | #330 | Link | ||
Registered User
Join Date: Nov 2014
Posts: 440
|
Quote:
Quote:
Each driver has its own OpenCL compiler. I can not test all possible cases.
__________________
github.com |
||
3rd September 2015, 10:11 | #331 | Link |
Registered User
Join Date: Nov 2014
Posts: 440
|
__________________
github.com |
3rd September 2015, 13:04 | #332 | Link | |
Registered User
Join Date: Nov 2014
Posts: 440
|
Quote:
__________________
github.com |
|
3rd September 2015, 22:07 | #333 | Link |
Registered User
Join Date: Aug 2015
Posts: 40
|
Hello.
With this script by feisty2: http://forum.doom9.org/showpost.php?...&postcount=234 vsedit shows me the following message: Code:
Failed to evaluate the script: Python exception: knlm.KNLMeansCL: VapourSynthCreate error (clBuildProgram)! Traceback (most recent call last): File "vapoursynth.pyx", line 1469, in vapoursynth.vpy_evaluateScript (src/cython/vapoursynth.c:23703) File "/media/TEMPORAL/scrypt.vpy", line 60, in <module> spt = core.std.CropRel (core.knlm.KNLMeansCL(padding(clp,24,24,24,24), 0, 24, 4, h=3.2),24,24,24,24) File "vapoursynth.pyx", line 1368, in vapoursynth.Function.__call__ (src/cython/vapoursynth.c:22272) vapoursynth.Error: knlm.KNLMeansCL: VapourSynthCreate error (clBuildProgram)! My graphics card is a GTX 960, using NVIDIA 355.11 driver. "nvidia_uvm" seems loaded into the kernel. nVidia OpenCL in Blender 3D seems to be working properly. What could be causing the problem? EDIT: I have found that a file "KNLMeansCL.txt" is generated in the same folder as the script: http://pastebin.com/4Cvep6w8 Another question. I have two devices that can use OpenCL, Nvidia and Intel. How to indicate in the script which device KNLMeansCL should use? Last edited by YAFU; 3rd September 2015 at 23:34. |
4th September 2015, 00:03 | #334 | Link | |
Registered User
Join Date: Nov 2014
Posts: 440
|
Quote:
Or you can manually set the default opencl device in your system environment. EDIT. v0.6.2 is required. Tomorrow I correct everything. Others have had problems.
__________________
github.com Last edited by Khanattila; 4th September 2015 at 00:12. |
|
4th September 2015, 18:24 | #336 | Link |
Registered User
Join Date: Nov 2014
Posts: 440
|
__________________
github.com |
4th September 2015, 19:16 | #337 | Link |
Registered User
Join Date: Aug 2015
Posts: 40
|
Hi.
I updated from git (git pull), compiled and installed (Kubuntu Linux 64 bits, nvidia 355.11 driver) Still having similar error in vsedit, and this is the log: http://pastebin.com/eiWtS3ws I uninstalled intel OpenCL driver, so nvidia is the only OpenCL device. Last edited by YAFU; 4th September 2015 at 19:19. |
Thread Tools | Search this Thread |
Display Modes | |
|
|