This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Better SMDegrain for VapourSynth
#1
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?
Reply
#2
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/.../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/vapoursy...mvmulti.py which requires https://github.com/IFeelBloated/vapoursy...f/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
Reply
#3
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
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)