VapourSynth Installer, Applications, & Plugins for macOS (Intel)

[shph]

I just notice that Selur updated Hybrid Scripts about a month ago https://github.com/Selur/VapoursynthScriptsInHybrid so today i download them and try to use.
As usual i put a copy inside Hybrid.app and another copy to /Library/Frameworks/VapourSynth.framework/lib/python3.8/site-packages/.
With new scripts and Very Slow or Placebo deinterlace settings i got: Aborting '06_15_03_5110_02_video' due to: ERROR
I try VS 50 or 51 and different versions of MVTools and got same error. So it is definitely some problem with updated script itself or with macOS version compatibility.

Here i attach old working scripts to compare, if it helps.

[Selur]

newer QTGMC uses neo_fft3d (https://github.com/HomeOfAviSynthPlusEvolution/neo_FFT3D/releases) instead of fft3dfilter, so without neo_fft3d this will cause a crash.

[AdamCarter]

Can’t wait for the newest version of hybrid with updated qtgmc/neo-fftd.

Guess will gsve to wait for neo-Fft3d to be mac compiled first?

[l33tmeatwad]

Working on patching the neo plugin, it's got some issues that keep it from compiling on macOS.

Update: Looks like Sierra does not support compiling with some of the features it uses, I will need to find which version has the features needed to compile it.

[shph]

Why don't use Mojave 10.14.6 ? It is still up to date system and same time the last version that support 32 bit apps.

[l33tmeatwad]

Why don't use Mojave 10.14.6 ? It is still up to date system and same time the last version that support 32 bit apps.I mean I could and then compile with version compatibility flags, however I usually just find it easier to compile and test on the oldest OS version I plan for it to work on to make sure it doesn't crash or that I can gather a crash report. As for 32-bit support, why would that matter? Apple hasn't had a computer with a 32-bit processor since like 2006 and most of those lost support long before Mojave. The main reason to be concerned about 32-bit support would be if you were writing an application that used an external library that you only had access to 32-bit binaries for.

[shph]

Hybrid on macOS still use some 32 bit components, so Mojave is the last working system if maybe you want to test something with Hybrid.app

[l33tmeatwad]

Hybrid on macOS still use some 32 bit components, so Mojave is the last working system if maybe you want to test something with Hybrid.appFrom my understanding the developer has dropped support, so trying to maintain support will be a bit of a losing battle as the switch to ARM is going to cause the application to eventually become obsolete. Considering the complies I'm offering support back to 10.12 currently, there should be no issue with compatibility unless core functions are charged that break compatibility with the application itself.

[l33tmeatwad]

So I've got bad news for those of you looking to keep Hybrid up to date by using the neo fft3d plugin to allow the scripts to be updated...there are features used in the neo plugin that requires Catalina for it to compile...I will upload the plugin, but it will require Catalina or higher to run, so good luck!

[AdamCarter]

I run hybrid catalina. It runs great, but sox and lsdvd were the only plugins that didnt work for me. However shijan, said that the new versions of lsdvd and sox work now, so i bet once i update to the newest version Hybrid on catalina will be great.

I usually rip stuff using makemkv
Then run hybrid

Since i am in catalina and sox didnt work before i would remux the audio from original mkv to the new mkv using mkvtoolnix.

But if sox Is working now, boom, things rill be that much faster.

Still hoping for anime4k denoising or some waifu2k variant. Then i’d be in heaven.

[shph]

So I've got bad news for those of you looking to keep Hybrid up to date by using the neo fft3d plugin to allow the scripts to be updated...there are features used in the neo plugin that requires Catalina for it to compile...I will upload the plugin, but it will require Catalina or higher to run, so good luck!

Yep, bad news for Mojave users. But it appears it is possible to revert new QTGMC scripts back to legacy fft3dfilter. Just replace 'neo_fft3d.FFT3D' with 'fft3dfilter.FFT3DFilter' in havsfunc.py

Probably i will create two versions of VapourSynth+QTGMC+Hybrid package in future. One with legacy fft3dfilter and edited script compatible with Mojave and Catalina.
And second package with neo_fft3d.FFT3D for Catalina only.

So it still make sense to compile neo_fft3d

Hope it will be no problem with x64 version of ffmbc.

[l33tmeatwad]

I usually test these things before posting, unfortunately the plugin is causing fftw3 to crash when seeking. I'll try to collect details to pass on to the developer.

[shph]

Seems new stuff is always buggy.
I tested new QTGMC scripts with 'neo_fft3d.FFT3D' name manually replaced with 'fft3dfilter.FFT3DFilter' in havsfunc.py and everything works great with legacy fft3dfilter.

[l33tmeatwad]

Actually I think the method used to call fftw3 was broken by Catalina, which is ironic because it's the only version capable of compiling it.

[shph]

Maybe ask developer of neo_fft3d to add support for Mojave somehow?

[l33tmeatwad]

Maybe ask developer of neo_fft3d to add support for Mojave somehow?That doesn't actually fix the problem and would be a more complicated fix. It's counter productive to adjust something to only work on older versions of an OS.

[shph]

Also here is my test report about different versions of MVtools plug-ins that you share earlier.
MVtools-v20 and v21 works well.
MVtools-v22 and v23 are broken. When i use preset "Placebo" in Hybrid render starts, but after some short time it stops with error. "crashed: Helper1, exitCode: 11"

[AdamCarter]

Actually I think the method used to call fftw3 was broken by Catalina, which is ironic because it's the only version capable of compiling it.

Can this be compiled on catalina?

https://github.com/rlaPHOENiX/VSGAN

[l33tmeatwad]

If you used the VapourSynth installer then you already have Numpy and Mvsfunc, so all you would need to do is run the following commands (ONLY valid for those that used the installer):
sudo vspip3 install torch torchvision
sudo vspip3 install vsgan
Now for some reason the pip install also installs a bottled version of VapourSynth that will confuse Python and cause scripts to always crash, so you'll also need to run the following command to remove it:
sudo rm /Library/Frameworks/VapourSynth.framework/lib/python3.8/site-packages/vapoursynth.cpython-38-darwin.so
sudo rm -rf /Library/Frameworks/VapourSynth.framework/lib/python3.8/site-packages/VapourSynth-51-py3.8.egg-info
Additionally if you want to use the new commands installed easily you can do the following:
sudo ln -s /Library/Frameworks/VapourSynth.framework/bin/convert-caffe2-to-onnx /usr/local/bin/vsconvert-caffee2-to-onnx
sudo ln -s /Library/Frameworks/VapourSynth.framework/bin/convert-onnx-to-caffe2 /usr/local/bin/vsconvert-onnx-to-caffe2
sudo ln -s /Library/Frameworks/VapourSynth.framework/bin/futurize /usr/local/bin/vsfuturize
sudo ln -s /Library/Frameworks/VapourSynth.framework/bin/pasteurize /usr/local/bin/vscpasteurize
I always add vs when adding links so it doesn't potentially overwrite anything someone might have installed and also so it reminds me that I'm running stuff specifically for the VapourSynth framework.

[AdamCarter]

Actually I think the method used to call fftw3 was broken by Catalina, which is ironic because it's the only version capable of compiling it.

If you used the VapourSynth installer then you already have Numpy and Mvsfunc, so all you would need to do is run the following commands (ONLY valid for those that used the installer):
sudo vspip3 install torch torchvision
sudo vspip3 install vsgan
Now for some reason the pip install also installs a bottled version of VapourSynth that will confuse Python and cause scripts to always crash, so you'll also need to run the following command to remove it:
sudo rm /Library/Frameworks/VapourSynth.framework/lib/python3.8/site-packages/vapoursynth.cpython-38-darwin.so
sudo rm -rf /Library/Frameworks/VapourSynth.framework/lib/python3.8/site-packages/VapourSynth-51-py3.8.egg-info
Additionally if you want to use the new commands installed easily you can do the following:
sudo ln -s /Library/Frameworks/VapourSynth.framework/bin/convert-caffe2-to-onnx /usr/local/bin/vsconvert-caffee2-to-onnx
sudo ln -s /Library/Frameworks/VapourSynth.framework/bin/convert-onnx-to-caffe2 /usr/local/bin/vsconvert-onnx-to-caffe2
sudo ln -s /Library/Frameworks/VapourSynth.framework/bin/futurize /usr/local/bin/vsfuturize
sudo ln -s /Library/Frameworks/VapourSynth.framework/bin/pasteurize /usr/local/bin/vscpasteurize
I always add vs when adding links so it doesn't potentially overwrite anything someone might have installed and also so it reminds me that I'm running stuff specifically for the VapourSynth framework.


All of this went over my head.

[AdamCarter]

Recently upgraded to hybrid 8.16 vs r51 qtgmc custom setting does not work.
There are three variables i was playing with to try and get a lossless encode to run via topaz ai.
I Set the lossless and source matching on both with the highest settingS after temporal smoothing and 2xredefined It failed, then i tried changing just the source matching down one setting It failed , and then down another setting It failed, and then off It failed. Then i lowered the lossless down a setting It failed and then off It failed. I also lowered temporal smoothing to from 1 to 0 that failed. I tried Above settings when encode it to prorez for lossless it failed. I also tried to Encode x264 Rate 1 for lossless then 16, then 17 all Failed..

The source was a interlaced 29.97 variable fps file Ripped from An old tape recording .

Going to try my standard interlaced dvd hopefully i can do my standard encoding which is qtgmc bob even x264 Rate 17.

Shph do you happen to have the r50 complete install kmage with all the old stuff pre lsdvd and sox? And neofft3d and all those updates i just want to get back to my previous working build which I completely deleted.

Update normal ripped track from a dvd i ripped into mkv via makemkv. Seems to work like before with above build On placebo, i believe custom is still broken but havent tried it yet. . So it may be just that file. The file reports its progressive via tags, but hybrid said it was bottom field first. So i was running qtgmc bob 59.97. I also put it into a demo of topaz ai and it can only work on progressive media And it was processing the footage so either it just reads the tags and proceeds. hybrid identified it as interlaced bottom field first. It is so hard because it was likely recorded off of tv or vhs and at 29.97 to me that screams interlaced (or telecine).

[l33tmeatwad]

If you just need VapourSynth r50, you can find the installer linked in the first post of this thread, that is the one packaged with those Hybrid bundles.

[shph]

AdamCarter, It could be due VS-51 as well. Try install R-50. There is a report on BM forum that R-51 is buggy and suggest to update to R52-RC1.
I don't keep legacy Hybrid packages, but you can always download old original version of Hybrid 2017 and extract components manually from it and replace back in Hybrid.app (right-click -> show package contents)

[shph]

Here is a serious problem report: Vapoursynth R51 now produces video aliasing output compared to R50 https://github.com/vapoursynth/vapoursynth/issues

[Cary Knoop]

Here is a serious problem report: Vapoursynth R51 now produces video aliasing output compared to R50 https://github.com/vapoursynth/vapoursynth/issues
I encountered a crash in R51 (probably when calling vcfreq.dll) that is away in R52-RC1

[shph]

I can confirm aliasing problem in macOS VS-R51 running with early alpha version of Hybrid 2020. Aliasing is visible even with "Slow" preset.

[shph]

Any news about neo_fft3d ? It seems a lot of other filters now rely on it,
Also any chance to add CAS filter (Contrast Adaptive Sharpening) to collection? https://github.com/HomeOfVapourSynthEvolution/VapourSynth-CAS It is available Hybrid UI

[l33tmeatwad]

Any news about neo_fft3d ? It seems a lot of other filters now rely on it,
Also any chance to add CAS filter (Contrast Adaptive Sharpening) to collection? https://github.com/HomeOfVapourSynthEvolution/VapourSynth-CAS It is available Hybrid UINeo is pretty broke for macOS, it'll have to be fixed by the developer. I'll look into CAS when I get the chance.

[shph]

Also seems there is some mistake with dfttest plug-in or with plug-in naming in Hybrid. I will ask Selur about this, but can you check plug-in somehow to be sure that it works?

Filtering -> DeNoise -> DFTTest:

Failed to evaluate the script:
Python exception: No attribute with the name dfttest exists. Did you mistype a plugin namespace?


Traceback (most recent call last):
File "src/cython/vapoursynth.pyx", line 1956, in vapoursynth.vpy_evaluateScript
File "src/cython/vapoursynth.pyx", line 1957, in vapoursynth.vpy_evaluateScript
File "/Volumes/temp/Hybrid Temp/tempPreviewVapoursynthFile00_46_47_216.vpy", line 19, in <module>
clip = core.dfttest.DFTTest(clip=clip)
File "src/cython/vapoursynth.pyx", line 1546, in vapoursynth.Core.__getattr__
AttributeError: No attribute with the name dfttest exists. Did you mistype a plugin namespace?

Filtering -> DeNoise -> MCTemporalDenoise:

Failed to evaluate the script:
Python exception: There is no attribute or namespace named dfttest

Traceback (most recent call last):
File "src/cython/vapoursynth.pyx", line 1956, in vapoursynth.vpy_evaluateScript
File "src/cython/vapoursynth.pyx", line 1957, in vapoursynth.vpy_evaluateScript
File "/Volumes/temp/Hybrid Temp/tempPreviewVapoursynthFile00_48_42_176.vpy", line 26, in <module>
clip = havsfunc.MCTemporalDenoise(i=clip, settings="very high")
File "/Library/Frameworks/VapourSynth.framework/lib/python3.8/site-packages/havsfunc.py", line 3134, in MCTemporalDenoise
p = i.dfttest.DFTTest(tbsize=1, slocation=[0.0,4.0, 0.2,9.0, 1.0,15.0], planes=planes)
File "src/cython/vapoursynth.pyx", line 1233, in vapoursynth.VideoNode.__getattr__
AttributeError: There is no attribute or namespace named dfttest

[l33tmeatwad]

Make sure you have the latest build with the dependency built in and test it by itself if you need to. The Mac protection may stop it from loading as well so check the security section in system settings.

[shph]

Ok, probably just a bug in alpha version of Hybrid 2020, because no any error message when i select dfttest in QTGMC Deinterlace settings.

[AdamCarter]

I had same issues with r49, and r50 with 2018 hybrid with regards to denoisers. I dont know if they have been compiled in catalina or mojave yet or x64 yet, but i mentioned this earlier. That they didnt work,

https://forum.doom9.org/showthread.php?p=1919247#post1919247

[shph]

1. Some Denoisers and Sharpeners didn't worked because mvmulti.py script was missing in Hybrid. Selur add it here today https://github.com/Selur/VapoursynthScriptsInHybrid and it helps to fix problems with some filters.
2. Some Denoisers and Sharpeners don't work now because there is no macOS versions of neo_fft3d and CAS plug-ins yet.
3. DFTTest and MCTemporalDenoise don't work now probably because some bug in Hybrid with plug-in names or part names.

[AdamCarter]

Sweet, at least it is progressing. Getting very happy

[Selur]

@shph:
DFTTest calls in Hybrid look fine to me:
# Imports
import vapoursynth as vs
core = vs.get_core()
# loading source: /Users/selur/Desktop/test.avi
# color sampling YUV420P8@8, matrix:470bg, scantyp: progressive
# luminance scale TV
# resolution: 640x352
# frame rate: 25 fps
# input color space: YUV420P8, bit depth: 8, resolution: 640x352, fps: 25
# Loading source using FFMS2
clip = core.ffms2.Source(source="/Users/selur/Desktop/test.avi",cachefile="/Users/selur/temp/avi_c6b2c493052375dcc56052d30e195c86_853323747.ffindex",format=vs.YUV420P8,alpha=False)
# making sure input color matrix is set as 470bg
clip = core.resize.Point(clip, matrix_in_s="470bg",range_s="limited")
# making sure frame rate is set to 25
clip = core.std.AssumeFPS(clip, fpsnum=25, fpsden=1)
# Setting color range to TV (limited) range.
clip = core.std.SetFrameProp(clip=clip, prop="_ColorRange", intval=1)
# denoising using DFTTest
clip = core.dfttest.DFTTest(clip=clip)
# Output
clip.set_output()
-> this seems more like a problem with the autoloading, the library or the Vapoursynth install

Also 2 years ago none of the GPU supported/based filters worked which is why Hybrid atm. disables/removes the following on MacOS:

NNEDI3CL: https://github.com/HomeOfVapourSynthEvolution/VapourSynth-NNEDI3CL
KNLMeansCL: https://github.com/Khanattila/KNLMeansCL
gpu support in QTGMC, due to missing: NNEDI3CL
SVP/InterFrame: the gpu support
Anime4KCPP


additionally some filters were disabled since they didn't compile at the time on MacOS X:

DegrainMedian: https://github.com/dubhater/vapoursynth-degrainmedian
MCDegrainSharp: not sure whether this would work nowadays
libtcanny: https://github.com/HomeOfVapourSynthEvolution/VapourSynth-TCanny
and/or
libmvtools: https://github.com/dubhater/vapoursynth-mvtools
DeCrawl: due to missing libscenechange (https://forum.doom9.org/showthread.php?t=166769)
SSIQ: https://github.com/dubhater/vapoursynth-ssiq
Waifu2x: https://github.com/HomeOfVapourSynthEvolution/VapourSynth-Waifu2x-w2xc/
Waifu2x nvk: https://github.com/Nlzy/vapoursynth-waifu2x-ncnn-vulkan
SRMD: https://github.com/Kiyamou/VapourSynth-SRMD-ncnn-Vulkan
mClean doesn't work due to missing vcmod: source available over at http://www.avisynth.nl/users/vcmohan/
Limited Sharp Fasten Faster Mod: fails due to missing CAS
LGhost: doesn't work due to missing library https://github.com/HomeOfVapourSynthEvolution/VapourSynth-LGhost
Interframe/SVP: since there wasn't a mac version back then
all tools from Donald Graft


Cu Selur

[l33tmeatwad]

DFTTest is failing to load due to a C++ library error, something is wrong with the compile. I will look into what happened and recompile and test before uploading again. For now here's the the DFTTest v4 and the library dependancy:

DFTTest v4 (http://www.mediafire.com/file/dp81tjgj7dddy1z/DFTTest-r4.tar.gz/file)
FFTW3F (http://www.mediafire.com/file/7v9hu8j3chrnn7g/FFTW3F-3.3.8.tgz/file)

Side note, was looking into Hybrid and vsedit include is OLLLLLD, might want to consider updating that, but it's calling it as "vsViewer" which was apparently a lazy update to avoid updating code when it was switched from vsviewer to VapourSynth Editor. May want to update that in the source so users can update it.

[shph]

Filtering -> DeNoise -> DFTTest gives no error now with DFTTest v4. Great!

But there is still error in Filtering -> DeNoise -> MCTemporalDenoise. Strange...
Failed to evaluate the script:
Python exception: DFTTest: Function does not take argument(s) named slocation

Traceback (most recent call last):
File "src/cython/vapoursynth.pyx", line 1956, in vapoursynth.vpy_evaluateScript
File "src/cython/vapoursynth.pyx", line 1957, in vapoursynth.vpy_evaluateScript
File "/Volumes/temp/Hybrid Temp/tempPreviewVapoursynthFile19_55_22_278.vpy", line 26, in <module>
clip = havsfunc.MCTemporalDenoise(i=clip, settings="very high")
File "/Library/Frameworks/VapourSynth.framework/lib/python3.8/site-packages/havsfunc.py", line 3141, in MCTemporalDenoise
p = i.dfttest.DFTTest(tbsize=1, slocation=[0.0,4.0, 0.2,9.0, 1.0,15.0], planes=planes)
File "src/cython/vapoursynth.pyx", line 1835, in vapoursynth.Function.__call__
vapoursynth.Error: DFTTest: Function does not take argument(s) named slocation

[l33tmeatwad]

Filtering -> DeNoise -> DFTTest gives no error now with DFTTest v4. Great!

But there is still error in Filtering -> DeNoise -> MCTemporalDenoise. Strange...
Failed to evaluate the script:
Python exception: DFTTest: Function does not take argument(s) named slocation

Traceback (most recent call last):
File "src/cython/vapoursynth.pyx", line 1956, in vapoursynth.vpy_evaluateScript
File "src/cython/vapoursynth.pyx", line 1957, in vapoursynth.vpy_evaluateScript
File "/Volumes/temp/Hybrid Temp/tempPreviewVapoursynthFile19_55_22_278.vpy", line 26, in <module>
clip = havsfunc.MCTemporalDenoise(i=clip, settings="very high")
File "/Library/Frameworks/VapourSynth.framework/lib/python3.8/site-packages/havsfunc.py", line 3141, in MCTemporalDenoise
p = i.dfttest.DFTTest(tbsize=1, slocation=[0.0,4.0, 0.2,9.0, 1.0,15.0], planes=planes)
File "src/cython/vapoursynth.pyx", line 1835, in vapoursynth.Function.__call__
vapoursynth.Error: DFTTest: Function does not take argument(s) named slocation
Keep in mind you are using v4, there may have been some features added since then that are being utilized in the newer versions. I will compile the new one as soon as I can and will verify it's working before posting it.

[AdamCarter]

Thanks meatwad!!!!!!!

Thanks selur

[shph]

l33tmeatwad, can you confirm that "dotkill64.dylib" is correct plug-in name. I just noticed that all other plug-in names look like "libaddgrain.dylib", "libautocrop.dylib". But DotKill-R1 use just plain "dotkill64.dylib" name. https://www.mediafire.com/folder/wvdlnjapm1vvw#gm3qrek88a7bp

[l33tmeatwad]

l33tmeatwad, can you confirm that "dotkill64.dylib" is correct plug-in name. I just noticed that all other plug-in names look like "libaddgrain.dylib", "libautocrop.dylib". But DotKill-R1 use just plain "dotkill64.dylib" name. https://www.mediafire.com/folder/wvdlnjapm1vvw#gm3qrek88a7bp
Run the following command while in the directory with it:
otool -L dotkill64.dylib
If it shows up with a different name then it's wrong.

[shph]

looks like this:
otool -L /Library/Frameworks/VapourSynth.framework/lib/vapoursynth/dotkill64.dylib
/Library/Frameworks/VapourSynth.framework/lib/vapoursynth/dotkill64.dylib:
dotkill64.dylib (compatibility version 0.0.0, current version 0.0.0)
/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 120.1.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1226.10.1)

[l33tmeatwad]

looks like this:
otool -L /Library/Frameworks/VapourSynth.framework/lib/vapoursynth/dotkill64.dylib
/Library/Frameworks/VapourSynth.framework/lib/vapoursynth/dotkill64.dylib:
dotkill64.dylib (compatibility version 0.0.0, current version 0.0.0)
/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 120.1.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1226.10.1)
As you can see on the first line, it is correct. If you would like to change it, you can use install_name_tool as listed in the build instructions in this thread.

[shph]

Side note, was looking into Hybrid and vsedit include is OLLLLLD, might want to consider updating that, but it's calling it as "vsViewer" which was apparently a lazy update to avoid updating code when it was switched from vsviewer to VapourSynth Editor. May want to update that in the source so users can update it.

How about to update VS viewer icons based on something like modified SF Apple Symbols?
https://www.avanderlee.com/swift/sf-symbols-guide/
"SF Symbols were introduced during WWDC 2019 and are a big present for us developers. Apple basically gave us free symbols to use in our app and it’s even really easy to use them as well! With SF Symbols 2.0 being introduced in WWDC 2020 we’ve got even more possibilities to show beautiful icons in our apps."
"SF Symbols is a set of over 1,500 symbols that you can use in your app. They’re aligned and configurable in a wide range of weights and scales to adapt to your designs. As they are integrated into the San Francisco system font they automatically ensure optical vertical alignment with text for all weights and sizes."

You may see my another slowly moving customization project based on those icons here: https://www.pl32.com/forum3/viewtopic.php?f=3&t=6302&start=30

Here is my sketch for VapourSynth Editor. All icons are in vector format, but manually redrawn and optimized for 16x16 pixel grid size. If it possible, you may add some svg icons support for UI in future, so icons will look sharp on on hi-dpi retina-like displays. Let me know what you think. I can provide icons in PNG format as well.
https://i.imgur.com/k9jDNzf.jpg

[l33tmeatwad]

DFTTest r6 was updated and I was only able to insure it loaded, but it does load with VapourSynth. I am pretty busy this weekend so I figured I'd go ahead and upload it. If someone could let me know if it's working that would be great.

Side note, r7 added new features that require a newer compiler so that is why I complied r6 instead of r7. I may have to raise the base version supported again.

[l33tmeatwad]

Got a chance to test it, it appears to be working fine on my MacBook Pro as well. In addition to that I have uploaded the VapourSynth R52 installer.

[shph]

Thanks a lot! Updated DFTTest r6 seems works well. No more any errors related to it. Most denoisers work well now.

Only got errors due some missing plug-ins:

mClean DeNoise error because:
AttributeError: No attribute with the name vcmod exists.

LimitedSharpen-Faster-Mod and CAS sharpener error because:
AttributeError: There is no attribute or namespace named cas

[l33tmeatwad]

As I've said before, feel free to make requests, but please link to the source repository so I don't have to try and track them down.

[ChaosKing]

Lsfmod only needs CAS for smode 3 (or higher). Use defaults = slow or set smode to 2

https://github.com/HomeOfVapourSynthEvolution/VapourSynth-CAS
http://www.avisynth.nl/users/vcmohan/vcmod/vcmod.html (see bottom nav)

[l33tmeatwad]

Lsfmod only needs CAS for smode 3 (or higher). Use defaults = slow or set smode to 2

https://github.com/HomeOfVapourSynthEvolution/VapourSynth-CAS
http://www.avisynth.nl/users/vcmohan/vcmod/vcmod.html (see bottom nav)Thank you! I was looking through my backlog of suggested plugins as well as ones on my list of plugins not currently possible to compile and found my previous notes about vcmod and unfortunately that one is not cross platform. The other was apparently already on my list I just haven't gotten around to it yet.

Here are my notes on plugins that can't be compiled:
bilateralgpu - Depreciated
DePan - Depriciated
DGMVSource - Windows Only
IT - Crashes
vcfreq - Windows Only
vcm - Windows Only
VSFilterMod - Windows Only
waifu2x-w2xc - Depriciated
xy-VSFilter - Windows Only