![]() I was able to get knlmeanscl working using a workaround by adding a border before denoising and removing the border after denoising (see knlmeanscl thread). Sometimes you've just gotta do, what ya gotta do. If you like the result when using MDGrain2, maybe you need to upgrade your CPU.are you using distributed encoding ? I don't quite understand why you're complaining about your graphics card not working with KNLMeansCL, when you don't like the result anyway. So i'm still looking for another GPU denoise filter. Especially with animated stuff there seems to be some "color bleeding". I would really like to keep the original 1920x1080 resolution.Īnd to be honest i don't like the result of the KNLMeansCL filter. I really like the result but it is too CPU intensive.ĮDIT: however KNLMeansCL does work if i change the resolution of the video from 1920x1080 to 1916x1080 or any other resulotion! So something strange is going on. I've done some conversions with MDegrain2. I used to use fft3dgpu in the past with avisynth 32bit (?), but i don't think there is a 64bit version. ![]() What other GPU denoise filter do you recommend for an AMD GPU? i'm willing to add it manually to the avisynth script. When i set it to 0 or adapter there is a normal image, but i wonder if denoise works at all with these settings. Am i doing something wrong? I get a very dark image when i set mono noise to 2 or higher. KNLMeansCL does not seem to work on my AMD VEGA 64.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |