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

[shph]

Yep, link was posted by Selur in this list https://forum.doom9.org/showpost.php?p=1921547&postcount=140 Some plug-ins from that list already work. (NNEDI3CL, KNLMeansCL, DegrainMedian, SSIQ, DeCrawl, MCDegrainSharp)

DeDot: https://github.com/dubhater/vapoursynth-dedot isn't available for mac atm.

[ChaosKing]

Does this help?
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=vapoursynth-plugin-vcmove
https://github.com/4re/vapoursynth-portage/blob/master/media-plugins/vapoursynth-vcmod/vapoursynth-vcmod-2017.10.17.ebuild

[shph]

also currently missing:
CAS
vcmod: http://www.avisynth.nl/users/vcmohan/
LGhost library https://github.com/HomeOfVapourSynthEvolution/VapourSynth-LGhost
Edgefixer: https://github.com/sekrit-twc/EdgeFixer
SagNomMod: https://github.com/HomeOfVapourSynthEvolution/VapourSynth-SangNomMod
Anime4KCPP

[AdamCarter]

And anime4k
For us animation enthusiasts.

Will this forked waifu2x work?
https://github.com/Nlzy/vapoursynth-waifu2x-ncnn-vulkan

[l33tmeatwad]

Edgefixer: https://github.com/sekrit-twc/EdgeFixer
EdgeFixer and ContinuityFixer are actually the same thing, it got renamed at some point and I was still using the old name.

[shph]

KNLMeansCL Denoiser combined with "Placebo" or "Very Slow" preset gives me this artifact in Hybrid. Bug in plug-in or in Hybrid or somewhere between?
https://i.imgur.com/diiN0LS.jpg

[l33tmeatwad]

Added the following plugins:
Dedot
LGhost
SangNomMod

CAS will require macOS 10.14+ and Anime4KCPP requires a lot of extras so I'll come back to that later. As for waifu2x-ncnn-vulkan, I've looked into it before and it requires you to install another tool so that would be a bit more complicated to explain to users, I may revisit that at a later time as well.

[l33tmeatwad]

KNLMeansCL Denoiser combined with "Placebo" or "Very Slow" preset gives me this artifact in Hybrid. Bug in plug-in or in Hybrid or somewhere between?
What version of VapourSynth are you using?

[shph]

What version of VapourSynth are you using?
This is with VapourSynth-52

[shph]

MVTools v22 and v23 (same as before) don't works with all updates in Hybrid 2020 and VapourSynth-52.
MVTools v20 and v21 works.

[l33tmeatwad]

MVTools v22 and v23 (same as before) don't works with all updates in Hybrid 2020 and VapourSynth-52.
MVTools v20 and v21 works.Are you getting a crash log?

[shph]

I'll PM you full Log.
In Hybrid basic window it looks like this:
Helper(1) finished with exitCode: 11 and exitStatus: 1
-> 2020-08-24@04_36_58_2410_02_video crashed: Helper1, exitCode: 11
Aborting '2020-08-24@04_36_58_2410_02_video' due to: Helper1, exitCode: 11

[AdamCarter]

Added the following

CAS will require macOS 10.14+ and Anime4KCPP requires a lot of extras so I'll come back to that later. As for waifu2x-ncnn-vulkan, I've looked into it before and it requires you to install another tool so that would be a bit more complicated to explain to users, I may revisit that at a later time as well.

Thanks meatwad. For all the hard work.

Def hoping anime4k can be brought over. It’s the only thing i’m looking forward too.

[Selur]

@shph: Try the Vapoursynth Preview before encoding, that's the only way to get proper error messages in regard to using Vapoursynth in Hybrid.
The log (even the debug output log) will not be that informative to l33tmeatwad.

[l33tmeatwad]

@shph: Try the Vapoursynth Preview before encoding, that's the only way to get proper error messages in regard to using Vapoursynth in Hybrid.
The log (even the debug output log) will not be that informative to l33tmeatwad.
If it's the Hybrid log, yeah that's not very helpful to me. If it's the system crash log it does tell me what thread crashed and what was loaded in that thread so that is useful for finding out what piece of the puzzle is crashing, but it only narrows it down.

[AdamCarter]

Meatwad,
Selur looked at the crash with importing image sequences

His response was:
so my guess is that ImageMagick Writer-Reader (http://www.vapoursynth.com/doc/plugins/imwri.html) is missing in the Vapoursynth build.
Vapoursynth Preview should give an error message,...

Maybe shph can create a log of the crash.

[l33tmeatwad]

Meatwad,
Selur looked at the crash with importing image sequences

His response was:
so my guess is that ImageMagick Writer-Reader (http://www.vapoursynth.com/doc/plugins/imwri.html) is missing in the Vapoursynth build.
Vapoursynth Preview should give an error message,...

Maybe shph can create a log of the crash.
It's not missing, it just need XQuartz to be installed (as noted in the first post of this thread).

[AdamCarter]

Oh oksorry missed that

[shph]

Tested a lot of plug-ins today here https://forum.selur.net/showthread.php?tid=1495&pid=8710#pid8710 hope those logs may help to fix some plug-in related errors.

P.S. XQuartz was already installed on my system before, so it is not source of image sequence error.

[l33tmeatwad]

It seems that jpg decoding is not enabled by default in image magick, I'll have to recompile and make sure that format is enabled. I'll rebuild all the installers once I verify it's working.

[shph]

jpeg :)
Yes, i can confirm. Tested with PNG sequence and it works.

[shph]

Tif or Tiff import also don't works. You may check somehow other formats support if possible.
Failed to evaluate the script:
Python exception: Read: Failed to read image properties: vsViewer: NoDecodeDelegateForThisImageFormat `TIF' @ error/constitute.c/ReadImage/562

Traceback (most recent call last):
File "src/cython/vapoursynth.pyx", line 2244, in vapoursynth.vpy_evaluateScript
File "src/cython/vapoursynth.pyx", line 2245, in vapoursynth.vpy_evaluateScript
File "/Volumes/temp/Hybrid Temp/tempPreviewVapoursynthFile05_04_59_524.vpy", line 10, in <module>
clip = core.imwri.Read("/Users/shph/Desktop/untitled folder/%02d.tif", firstnum=1)
File "src/cython/vapoursynth.pyx", line 2069, in vapoursynth.Function.__call__
vapoursynth.Error: Read: Failed to read image properties: vsViewer: NoDecodeDelegateForThisImageFormat `TIF' @ error/constitute.c/ReadImage/562

[l33tmeatwad]

The R52 installer was updated with libimwri that supports jpg & tiff.

[AdamCarter]

Thanks meatwad.

[shph]

Image sequence works well! Thanks for update l33tmeatwad!

Wonder if someone here tested KNLMeansCL without Hybrid on macOS with some real footage. As you can see from my reports in Hybrid it only produce crazy artifacts and even kernel panic with computer restart.
But same time when i add test line to test.vpy script
# testing KNLMeansCL
clip = core.knlm.KNLMeansCL(clip=clip)
and run command
<PATH TO vspipe> --info <PATH to test.vpy> -
It gives me no any errors

[l33tmeatwad]

So there has been some useful feedback and such lately which I am grateful for, but I figured I should break down where certain problems should be reported so things can be streamlined and the correct people can be notified. There are 3 types of issues with the plugins/libraries:


Does not autoload & fails to load manually. It will generally let you know that it did not autoload with the error "No attribute with the name _ exists" and if you try to manually load it and it fails, that generally means there is either something wrong with the plugin itself or it has a dependency that is not loading. Either of these issues would be good to follow up with me about.

If a plugin loads but appears to be missing features that are listed or available on other platforms. This will generally give an error message, for example image reader had NoDecodeDelegateForThisImageFormat. This would also be a good one to follow up with me about as it may need some additional dependancies that I was not aware of at the time of compile.

If a plugin loads, but crashes when previewing or loading. I generally try to test and see if a plugin will load for more than just one frame, if it doesn't I usually won't upload it, however if this is happening for you this is generally an issue that you would want to follow up with the developer(s) about.

As for the issues with KNLMeansCL, that plugin is a graphics card accelerated plugin and based on some of the error messages you posted on the other forum, it appears there is a compatibility issue with your machine and what the plugin supports. You can follow up with the developer if you would like, however these issues are generally from graphics card drivers or just the card you have is not supported by the OpenCL features it is using.

[shph]

Great explanation!

KNLMeansCL give error when i select GPU or CPU as well, so i guess most likely problem somewhere in KNLMeansCL itself, or it is just not supported on Mojave.
I use i7-8700K CPU overclocked to 4.7Ghz, Radeopn RX580 GPU and macOS Mojave 10.14.6. No problem with OpenCL and Metal in other apps like DaVinci Resolve. QTGMC, NNEDI3 resizer and other VapourSynth filters on GPU/OpenCL also now woks well in last alpha version of Hybrid 2020.

Here are some test results:
Source VOB file (29.970 FPS duration 00:00:52.82) rendered to ProRes with QTGMC Placebo with BOB (59.94 FPS):
OpenCL render finished after 00:00:54.713
CPU render finished after 00:01:52.309

Source VOB file (29.970 FPS duration 00:00:52.82) rendered to ProRes with QTGMC Placebo with BOB (59.94 FPS) and upscaled to 1440x1080 with NNEDI3 (Neurons: 32, Network: 2, Prescreening: new)
OpenCL Render finished after 00:01:59.560
CPU render finished after 00:06:09.171

[shph]

l33tmeatwad, please see also some new reports https://forum.selur.net/showthread.php?tid=1495&pid=8735#pid8735
Strange problem with error "AttributeError: There is no function named SangNom" I try SangNom-r40 and SangNom-r41

[ChaosKing]

You could manually load the sangnom lib with std.LoadPlugin("path-to-file") and see what error code it returns. Maybe a dependency is just missing.

http://www.vapoursynth.com/doc/functions/loadplugin.html

[l33tmeatwad]

l33tmeatwad, please see also some new reports https://forum.selur.net/showthread.php?tid=1495&pid=8735#pid8735
Strange problem with error "AttributeError: There is no function named SangNom" I try SangNom-r40 and SangNom-r41
That's odd, I tested both on two systems and it appears to be fine. ChaosKing is correct, try loading it with the following and post the error:
core.std.LoadPlugin('/Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libsangnom.dylib')
Other things to check:

It is in the plugins folder and not the library folder.
OS security isn't picking it up and blocking it.
You aren't renaming the file.

[shph]

Plugin from l33tmeatwad Mediafile folder and copied to /Library/Frameworks/VapourSynth.framework/lib/vapoursynth/ same as all other plugins. Selur also report that it works on his system. Maybe it is not supported on Mojave?
:(
core.std.LoadPlugin('/Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libsangnom.dylib')
-bash: syntax error near unexpected token `'/Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libsangnom.dylib''

[l33tmeatwad]

Plugin from l33tmeatwad Mediafile folder and copied to /Library/Frameworks/VapourSynth.framework/lib/vapoursynth/ same as all other plugins. Selur also report that it works on his system. Maybe it is not supported on Mojave?
:(
core.std.LoadPlugin('/Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libsangnom.dylib')
-bash: syntax error near unexpected token `'/Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libsangnom.dylib''First off, that goes in a script, not terminal. Secondly, unless stated otherwise, ALL plugins support macOS 10.12+, AS STATED IN THE OPENING THREAD POST.

[shph]

Ah ok, not into Terminal :) I am just total noob when it goes to codes.
So is it possible to explain step by step how to run this?
Create text file, rename to .vpy, add core.std.LoadPlugin('/Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libsangnom.dylib') and run? how exact to run? Or add that line to to normal basic .vpy script?

Here is what i got when i add "core.std.LoadPlugin('/Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libsangnom.dylib')" to normal .vpy script taken from Hybrid and run "<PATH TO vspipe> --info <PATH to test.vpy> -" (as Selur explained me earlier)

/Library/Frameworks/VapourSynth.framework/bin/vspipe --info /Users/shph/Desktop/test.vpy -

Script evaluation failed:
Python exception: Plugin load of /Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libsangnom.dylib failed, namespace sangnom already populated by /Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libsangnommod.dylib

Traceback (most recent call last):
File "src/cython/vapoursynth.pyx", line 2244, in vapoursynth.vpy_evaluateScript
File "src/cython/vapoursynth.pyx", line 2245, in vapoursynth.vpy_evaluateScript
File "/Users/shph/Desktop/test.vpy", line 20, in <module>
core.std.LoadPlugin('/Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libsangnom.dylib')
File "src/cython/vapoursynth.pyx", line 2069, in vapoursynth.Function.__call__
vapoursynth.Error: Plugin load of /Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libsangnom.dylib failed, namespace sangnom already populated by /Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libsangnommod.dylib

[l33tmeatwad]

So it looks like you cannot have SangNomMod and SangNom in the autoload directory together, there is some kind of conflict.

[AdamCarter]

Meatwad a plugin developer had a question before making it mac compatible.

[ChaosKing]

So it looks like you cannot have SangNomMod and SangNom in the autoload directory together, there is some kind of conflict.

Both use the same namespace.

Use only SangNom https://github.com/dubhater/vapoursynth-sangnom and remove SangNomMod (https://github.com/HomeOfVapourSynthEvolution/VapourSynth-SangNomMod)

[shph]

Yep. I removed SangNomMod and MAA and AAF filters now works. Guess it is more-less ok to sacrifice SangNomMod Anti Aliasing filter in Hybrid yet.

But i still see problems with with Santiag Anti Aliasing filter:
No error, but empty preview window if i choose "Type: sangnom"
Error "TypeError: santiag() got an unexpected keyword argument 'typevh'" if i use "Type: selectHV"

[ChaosKing]

selectHV is not a valid type. Read the doc https://github.com/HomeOfVapourSynthEvolution/havsfunc/blob/e56f8f787bd4b679e6d14c9b08bf0460a3480ea4/havsfunc.py#L134

type = "nnedi3", "eedi2", "eedi3" or "sangnom"

[shph]

Ok, so seems current summary situation with missing/broken plug-ins is not so bad:

CAS just not compiled yet (i guess macOS 10.14+ is ok)

EdgeFixer is just a renamed legacy ContinuityFixer and just not compiled yet.

Interframe/SVP can't understand is it some sort of commercial plug-in? Or is it just don't compiled yet?

Anime4k probably the most distant plug-in because not yet available in Hybrid UI and as l33tmeatwad explained "need a lot of additional stuff to work"

---

KNLMeansCL may cause kernel panic and probably needs some fundamental fixes from developer and currently removed from Hybrid UI.

MVtools-v22 and v23 produce strange hangs during render and problem source is unknown yet (crashed: Helper1, exitCode: 11) Need global system report log to investigate. MVtools-v20 and v21 works well so probably new versions are not extra critical.

SangNomMod and SangNom compatibility problem source is known now. Hope someone will find some problem fix in future.

Santiag probably just needs a fix from Selur in Hybrid UI.

[l33tmeatwad]

Has anyone with actual Apple hardware had issues with MVTools v22 & 23?

[l33tmeatwad]

Added CAS r2 & EdgeFixer r2.

[shph]

So it is not 10.14+, it is 10.15+. too bad (for me) CAS seems like very interesting and unique tool.

[l33tmeatwad]

Additional note for EdgeFixer, it uses the same namespace as ContinuityFixer so both cannot be in the autoload directory.

[shph]

So i checked EdgeFixer and CAS on my 10.14.6 and both works well. No errors, no crashes. Render goes well. Is there any more scientific but real life way to check if something in these plugins don't work on 10.14.6?

[shph]

SangNom vs SangNomMod issue ticket https://github.com/HomeOfVapourSynthEvolution/VapourSynth-SangNomMod/issues/5

[l33tmeatwad]

SangNom vs SangNomMod issue ticket https://github.com/HomeOfVapourSynthEvolution/VapourSynth-SangNomMod/issues/5You don't need to report that here, if it's resolved and you need it compiled feel free to let me know, but reporting this kind of information just floods the thread.

[ChaosKing]

I'm curious: For what do you need SangNomMod? SangNom supports up to 32f precision while the mod version supports 8bit only. I don't see any reason to use the mod version.

[shph]

Agree. Plug-ins that support only 8 bit depth are unacceptable.

[l33tmeatwad]

Agree. Plug-ins that support only 8 bit depth are unacceptable.Considering the plugin in question is for interlaced material and that the overwhelming majority of content at this point that is interlaced is 8-bit, I think "unacceptable" is a bit silly. I'd honestly be surprised if you could find 10-bit or higher interlaced content, but I'm sure it probably exists out there somewhere...

[ChaosKing]

Sangnom is probably used in 80% of all antialiasing scripts and not just for deinterlacing ;)

So in this case it makes sense to support higher bit depth, but is does not mean every plugin should support it by default.