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

[Selur]

@l33tmeatwad: would be nice if ccd (https://github.com/End-of-Eternity/vs-ccd) could be added.

[l33tmeatwad]

I am adding things to the to-compile list, however compiling new stuff is still low priority at this time. If anyone else compiles anything feel free to share it and I'll add it to the larger share as well. Whenever time allows I'll try to get back to adding things.

[l33tmeatwad]

Since R58 is close to release I decided to start working on an update to the core dependancies. I will be updating some plugins and applications along with this update so keep an eye out for all of this. Additionally it would be wise to backup any scripts before installing as Python will be updated from 3.9 to 3.10.

[l33tmeatwad]

Some plugin additions and updates. I will probably transition the VapourSynth installer for R58 to only include the core application & dependancies with the individual plugins distributed separately, similar to the Windows distribution.

Updated Plugins:
FFMS2 w/ FFmpeg 5.0 Static Libs
LSMASHSource w/ FFmpeg 4.4.1 Static Libs
MiscFilters

New Plugin Downloads:
BestAudioSource w/ FFmpeg 5.0 Static Libs
EEDI3 (from VapourSynth R54)
ImageMagick Plugin (with Image Magick 7.1.0-28 Static Libs)
OCR w/ Tesseract 4.1.3
RemoveGrain
VIVTC

[Selur]

thanks for the updates. :) (hoping some of my suggestions also can get included *no hurry*)

[Cu Selur

[l33tmeatwad]

Removed Wobbly until it is compatible with the current API.
Updated D2V Witch to v5.

[Selur]

Nice, thanks!
btw. https://github.com/AmusementClub/assrender would be a good addition, since the https://github.com/vapoursynth/subtext has issues with newer .ass files.

Cu Selur

[l33tmeatwad]

Updated VapourSynth Editor to r19 Mod 5.1.

[l33tmeatwad]

Updated the following plugins:

BM3D
ColorBars
DeScale
DPID
FillBorders
GradCurve
MiniDeen
TBilateral
TimeCube
TTempSmooth

[l33tmeatwad]

Nice, thanks!
btw. https://github.com/AmusementClub/assrender would be a good addition, since the https://github.com/vapoursynth/subtext has issues with newer .ass files.

Cu Selur
Unfortunately out of the box it doesn't compile, to be fair I'm trying to use static libs so I think it's missing includes for the cmake.

[shph]

I noticed a problem with new version of libd2vsource (D2V Source w/ FFmpeg 5.0 Static Libs)
When i use some of my test VOB files, VSviewer icon jumps in the dock and VSviewer window can't be opened.
Or maybe libd2vsource (and other those newly compiled plugins) designed only for R58? (i currently use R57)
Here is test file if someone want to check https://drive.google.com/file/d/1OUCe9WN0RQEZm1KBWVdFSUlNNO5jd9Ry/view?usp=sharing

[l33tmeatwad]

Could you make a gif or video of the issue, I'm not sure I'm following.

[shph]

I use Hybrid.
Import VOB file
Click VapourSynth Preview (this should open VSviewer)
VSviewer can't be opened. Only icon jumps in dock.

No any problem with old version of libd2vsource

[shph]

In addition to oldest version (50KB size) i also checked D2VSource-v1.2 (16.1MB size) and it works well. So the problem only with D2VSource-v1.2-700523c (16.4MB size)

[l33tmeatwad]

D2VSource-v1.2-700523c has been removed for now, I'll try to rebuild with static libs later.

[l33tmeatwad]

Installer for R58 has been added, it does not include anything aside from VapourSynth, Python, Cython, Numpy, and Zimg.

EDIT: Python has been updated to 3.10, so backup your scripts, it will remove the old folder.

[shph]

Seems we need separate download for libsubtext.dylib
Or is it replaced with some other plugin in R58?

[l33tmeatwad]

If you're doing a fresh install, yes you will need to download that separately. Just like the Windows installer, all plug-in downloads are separate.

[shph]

Yes, i understand that. I mean that libsubtext.dylib seems currently not included in Plugin Downloads (and Mirror) collection in the first post

[l33tmeatwad]

I apparently forgot to upload it, however after testing, it appears to not work (nor has it worked for a while apparently as the copy included with R57 crashes as well).

As for D2VSource, I've recompiled it (with FFmpeg 4.4.1), tested, and uploaded it.

EDIT: Apparently it has not worked since R55, even with the old dylib that works with R54. Based on the error's I'm getting it's possible it is failing with the static libs, however it did work for R54, it will take further testing to figure out the best way to approach it.

[Selur]

Would be nice if you can switch Waifu2x NCNN Vulkan to https://github.com/HolyWu/vs-waifu2x-ncnn-vulkan

Cu Selur

[Selur]

Also new potential filters:
FrFun7: https://github.com/dubhater/vapoursynth-frfun7
Grayworld: https://github.com/Asd-g/AviSynthPlus-grayworld

Cu Selur

[Selur]

und noch einer:
ReduceFlicker: https://github.com/AmusementClub/ReduceFlicker

[l33tmeatwad]

R59 installer added.

[Selur]

and another one: https://github.com/dubhater/vapoursynth-median :)

[Selur]

Small question how to install vsutil when I used the R59 Vapoursynth installler?
On Windows and Linux I would use:
python3 -m pip install --upgrade pip
curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py
python3 get-pip.py
python3 -m pip install --upgrade pip
python3 -m pip install vsutil
but that doesn't seem to work as intended on MacOS,...

[l33tmeatwad]

Small question how to install vsutil when I used the R59 Vapoursynth installler?
On Windows and Linux I would use:
python3 -m pip install --upgrade pip
curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py
python3 get-pip.py
python3 -m pip install --upgrade pip
python3 -m pip install vsutil
but that doesn't seem to work as intended on MacOS,...
As stated in the first post of the thread:
IMPORTANT: The installer includes it's own copy of python separate from the system, to access that environment use the commands vspython3 or vspip3 in terminal.

[Selur]

Ah okay missed that. Thanks. :)

[Selur]

Now I got:
vspip3 install vstutil
Defaulting to user installation because normal site-packages is not writeable
ERROR: Could not find a version that satisfies the requirement vstutil (from versions: none)
ERROR: No matching distribution found for vstutil
:/
"vspip3 install --upgrade pip" didn't help either.
Problem is newer havsfunc versions use vsutil. :(

[Selur]

Okay,

cd /Library/Frameworks/VapourSynth.framework/bin
./python3.10 -m pip install vsutil

worked.

[l33tmeatwad]

From user point of this is very confusing. I updated VS, Install Hybrid... and it don't works. So i send bug report, and then 2 days later it appears that now every new update i need to that code in Terminal. Probably every other user will be confused in same way.
Why change things like this? It all worked easy and simple earlier versions.
It's always been that way, the intention is to keep a bottled version of Python so that if the user happens to upgrade their system version it won't break VapourSynth.
Now I got:
vspip3 install vstutil
Defaulting to user installation because normal site-packages is not writeable
ERROR: Could not find a version that satisfies the requirement vstutil (from versions: none)
ERROR: No matching distribution found for vstutil
:/
"vspip3 install --upgrade pip" didn't help either.
Problem is newer havsfunc versions use vsutil. :(
You'll need to sudo as the folder requires admin permissions, not sure why running it directly from the folder made a difference, but I assume it made you enter your password to get write access.

[l33tmeatwad]

Have no idea why but cd /Library/Framworks/VapourSynth.framework/bin don't works on my system.

I got this:
-bash: cd: /Library/Framworks/VapourSynth.framework/bin: No such file or directory

I still use macOS 10.14.6. Is it compatible?
There's a typo in your path, it should be "Frameworks" not "Framworks".

[Selur]

fixed the typo,..
UPDATE: seems some bug in Hybrid VS viewer related to MOV container only...
VS viewer hasn't changed since last release,...
Works fine here. It's more likely an issue with your system.

[Selur]

¯\_(ツ)_/¯
no clue, your source is displayed fine in my mac vm with nearly the same script (no opencl since the vm doesn't support it).

[Selur]

I tried all presets and can't reproduce your issue:
https://i.ibb.co/9wXjTg8/placebot-again.png (https://ibb.co/9wXjTg8)
on Windows, Mac and Linux.

[Selur]

@shph: please don't spam this thread, your issue has nothing do to with l33tmeatwad project,... (issue is related to changed in havsfunc and it's dependencies, no clue which since I can't reproduce it)

[Selur]

Okay, cause of the issue was a bug in Vapoursynth R59 (see: https://github.com/HomeOfVapourSynthEvolution/havsfunc/issues/69) which is fixed in R60_RC1.
This also explains why I couldn't reproduce it in my MacOs VM since it has no AVX2 support. ;)
-> @l33tmeatwad: could you compile a R60_RC1 installer for MacOS?

[l33tmeatwad]

I usually stick to the major releases instead of the release candidates, if there aren't bugs from R58 that caused the upgrade to R59 I would suggest going with that for now, I'll try to get R60 compiled as soon as the main release is out.

[Selur]

fair enough :)

[Selur]

@l33tmeatwad: Vapoursynth R60 is release. :)

[l33tmeatwad]

R60 installer is now up.

[Selur]

Thanks! :)

[Selur]

Could you also add akarins vapoursynth plugin? (https://github.com/AkarinVS/vapoursynth-plugin)

Cu Selur

[l33tmeatwad]

R61 installer is now up.

[Selur]

Thanks, any plans for further updates?

[l33tmeatwad]

I'll do a yearly roundup of plugin updates closer to the end of the year, but I don't have plans to add much new, I'm trying to get ahold of a ARM Mac so I can start building that out as that's going to be more helpful for the future, although I'll continue to support the Intel machines for the base installer and common plugins until they are updated in a way where they won't compile.

[groucho86]

I'll do a yearly roundup of plugin updates closer to the end of the year, but I don't have plans to add much new, I'm trying to get ahold of a ARM Mac so I can start building that out as that's going to be more helpful for the future, although I'll continue to support the Intel machines for the base installer and common plugins until they are updated in a way where they won't compile.

Hi l33tmeatwad, first off, a big thank you for all your hard work simplifying the life of Mac users!!

The M1/M2 systems are working really well for the most part, but as soon as there is asm code, the builds obviously break.

For mvtools and and nnedi3, I found this:
https://github.com/Stefan-Olt

But currently have not found anyone solve the asm code for eedi3 (and I don't have the skill set to figure it out either). Hoping you might have some idea?

[l33tmeatwad]

Unfortunately I do not have a solution for that, as soon as I'm able to get my hands on an ARM based Mac I'll start building for that. Compiling things isn't too hard, I've got some detailed instructions in the early posts of this thread if you wanna try out compiling. Since these builds are separated from the typical install path you don't have to worry about breaking anything, I would just rename your current VapourSynth.framework folder so you have a backup of that. If you can get through setting up the framework it shouldn't be too hard to get plugins compiled too.

[sevenrats]

Unfortunately I do not have a solution for that, as soon as I'm able to get my hands on an ARM based Mac I'll start building for that. Compiling things isn't too hard, I've got some detailed instructions in the early posts of this thread if you wanna try out compiling. Since these builds are separated from the typical install path you don't have to worry about breaking anything, I would just rename your current VapourSynth.framework folder so you have a backup of that. If you can get through setting up the framework it shouldn't be too hard to get plugins compiled too.

I have an M2 we could use for this purpose. Would you be willing to collaborate on matrix or discord? Alternatively, we could just go back and forth with error messages here, but it would be easier to DM or just give you shell access.

[l33tmeatwad]

I apologize for the delay on R63, there were some changes that will require a higher minimum OS version. This means I'll have to do some testing and build a new base, which I haven't had time to deal with. I'll try to get to it ASAP.