The following warnings occurred:
Warning [2] Trying to access array offset on null - Line: 14 - File: inc/plugins/cookielaw.php(272) : eval()'d code PHP 8.3.12-nmm1 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/plugins/cookielaw.php(272) : eval()'d code 14 errorHandler->error_callback
/inc/plugins/cookielaw.php 272 eval
/inc/class_plugins.php 142 cookielaw_global_intermediate
/global.php 100 pluginSystem->run_hooks
/printthread.php 16 require_once
Warning [2] Trying to access array offset on null - Line: 14 - File: inc/plugins/cookielaw.php(272) : eval()'d code PHP 8.3.12-nmm1 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/plugins/cookielaw.php(272) : eval()'d code 14 errorHandler->error_callback
/inc/plugins/cookielaw.php 272 eval
/inc/class_plugins.php 142 cookielaw_global_intermediate
/global.php 100 pluginSystem->run_hooks
/printthread.php 16 require_once



Selur's Little Message Board
Better SMDegrain for VapourSynth - Printable Version

+- Selur's Little Message Board (https://forum.selur.net)
+-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html)
+--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html)
+--- Thread: Better SMDegrain for VapourSynth (/thread-1118.html)

Better SMDegrain for VapourSynth - hanspeter007 - 12.08.2019

Hi,

i have some material with heavy graining, where I need a temporal radius bigger than 3, but the current implemented SMDegrain for Vapoursynth supports only tr < 3.
On Vsdb (page 2) I found an improved version of SMDegrain for Vapoursynth ("SMDegrain with float and tr > 3 support"). Is it possible to use external plugins in Hybrid? Or is it possible to implement this version of SMDegrain in future releases of hybrid?

RE: Better SMDegrain for VapourSynth - Selur - 12.08.2019

Quote:Is it possible to use external plugins in Hybrid?
If you know your way around Vapoursynth scripting that's what the custom section is for.

Quote: Or is it possible to implement this version of SMDegrain in future releases of hybrid?
Hmmm,...
Looking at https://github.com/Helenerineium/G41Fun/blob/master/G41Fun.py it would require some additional changes, atm. is doesn't support using nneci3 opencl, like the version Hybrid uses. (not many changes, so no real problem)

Quote:tr > 3 uses mvsf hence requires float input, also requires mvmulti module.
So an additional color conversion (input needs to be YUV444PS) and additional dependencies. (https://github.com/IFeelBloated/vapoursynth-mvtools-sf/blob/master/src/mvmulti.py which requires https://github.com/IFeelBloated/vapoursynth-mvtools-sf/releases, which I can't get to compile on anything but Windows <- this really is troublesome)
-> this would be a Windows only thing, not sure it's worth the trouble. (having to maintain a modified Windows and a modified Linux version)

Cu Selur

RE: Better SMDegrain for VapourSynth - hanspeter007 - 17.08.2019

Thank you for your detailed answer. I think in those cases I'll stick to avisynth, even if its slower. But it will save a lot of work with custom scripting and so Big Grin