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 |
14th December 2016, 14:02 | #1021 | Link |
Registered User
Join Date: Nov 2014
Posts: 440
|
It would be a step back, and that's what I want to avoid
__________________
github.com |
14th December 2016, 20:13 | #1022 | Link |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
you can use SMDegrain_prefilters(4) and play with it settings
__________________
See My Avisynth Stuff |
16th December 2016, 00:32 | #1024 | Link |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
even so
SMDegrain_prefilters =\\= SMDegrain with SMDegrain_prefilters(4) you will get only KNLMeansCL output clip, and there is knlm_params to use other KNLMeansCL params and you can feed that clip in SMDegrain if you want like this Code:
knlclip=SMDegrain_prefilters(4, knlm_params=", wmode=0") SMDegrain(prefilter=knlclip)
__________________
See My Avisynth Stuff |
16th December 2016, 03:04 | #1025 | Link |
Registered User
Join Date: Jan 2016
Posts: 162
|
Feature request:
Extra "mask" clip option For each pixel in the output clip, if the value of corresponding pixel in "mask" is 0 (black), just copy the value from input clip; else, use NLM normally. Hope this will reduce computation complexity a lot in some cases, althought the can also be achieved by mt_merge(source, KNLMeansCL(source), mask) but that's too slow when there's only few pixels need to be processed Last edited by WolframRhodium; 16th December 2016 at 05:20. |
19th December 2016, 13:11 | #1028 | Link | |
Registered User
Join Date: Nov 2014
Posts: 440
|
Quote:
What kind of problem? Loss of precision or anything else?
__________________
github.com |
|
5th January 2017, 17:28 | #1031 | Link |
Registered User
Join Date: Nov 2014
Posts: 440
|
Ok, I release the beta.3 in the next days.
__________________
github.com |
5th January 2017, 21:12 | #1032 | Link |
Registered User
Join Date: Oct 2014
Posts: 268
|
@khanattila: What about the results of that 'benchmark only' build you did?
Are you going to put 'optimal' settings inside the plugin based on detected gpu / generation. are or you going to open up parameters like those so we can find our own optimal distribution with the final release? |
6th January 2017, 15:26 | #1033 | Link | |
Registered User
Join Date: Nov 2014
Posts: 440
|
Quote:
__________________
github.com |
|
6th January 2017, 18:50 | #1034 | Link | |
Acid fr0g
Join Date: May 2002
Location: Italy
Posts: 2,574
|
Quote:
Speed is determined by total script, not only a plugin. I could trade some speed for better prefiltering or anything else.
__________________
@turment on Telegram Last edited by tormento; 6th January 2017 at 18:52. |
|
6th January 2017, 20:05 | #1035 | Link |
Registered User
Join Date: Oct 2014
Posts: 268
|
But the parameters have nothing to do with quality or speed settings for the plugin. More a way to optimize the workload so it performs better for certain video cards.
Certain AMD generations need other parameters than other AMD cards or something. My otherwise speedy GTX 1060 needed really different (low) settings to gain maximum speed than the latest RX480 cards for instance. This has nothing to do with quality or what the plugin does. More the way the plugin gives commands to the GPU as far as I get it . |
17th January 2017, 15:35 | #1036 | Link |
Registered User
Join Date: Oct 2009
Location: crow-land
Posts: 540
|
Hello. A newbie type question, however worth asking since I find I am in need of guidance.
I wonder if you could clarify whether and when KNLMeansCL is appropriate to use as a plain denoiser by itself ? I noticed it's been used in SMDegrain however I am unclear if KNLMeansCL is appropriate for use as a denoiser in its own right, for example on a range of OTA TV captures for moderate denoising a la mdegrain1/2/3. Any advice or links to comparisons somewhere ? Another objective is to attempt to identify GPU (eg OpenCL) based filters for the times when a fast workflow is OK, ie where some improved quality output is hoped for but not paramount and speed is valued. (Tools = ffmpeg and x264, portable vapoursynth_x64, win10_x64.) So far I have only seen these GPU based filters
Do you know of any other GPU filters usable in vapoursynth, or ffmpeg, especially sharpeners ? Is there already a list somewhere ? Thanks. |
17th January 2017, 18:22 | #1037 | Link | |
Registered User
Join Date: Nov 2014
Posts: 440
|
Quote:
Do not focus yourself on gpu based filters.
__________________
github.com |
|
17th January 2017, 19:02 | #1038 | Link | |
I'm Siri
Join Date: Oct 2012
Location: void
Posts: 2,633
|
Quote:
|
|
17th January 2017, 19:09 | #1039 | Link |
I'm Siri
Join Date: Oct 2012
Location: void
Posts: 2,633
|
Also it's a big mystery that how the hell NLMeans ended up acting as a "pre filter" for MDeGrain? You do realize that's like doing a motion compensation pre filtering for RemoveGrain, right?
EDIT: simple rule, the fancier filter gets to be the main filter, so MDeGrain should be the pre filter (rclip) and NLMeans should be the main filter. Last edited by feisty2; 17th January 2017 at 19:23. |
17th January 2017, 20:25 | #1040 | Link | |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
Quote:
__________________
See My Avisynth Stuff |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|