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

[l33tmeatwad]

Originally Posted by groucho86

Are these new for Intel only still? Meaning any asm code will not work on M1/M2/M3?

These are still for Intel, I will change the topic once I'm able to get my hands on an ARM Mac and can start compiling for those.

[l33tmeatwad]

Small update, since I have switched to 10.15 a few plugins that would compile but for some reason wouldn't autoload are now working. I will slowly be updating plugins, however they will only work on macOS 10.15+.

[l33tmeatwad]

Added VapourSyth Editor r19 mod 6.3 and it will require macOS 10.15 or newer. I have combined Job Server and Job Server watcher into the same app so that it's easier to use and I also included a script to create links to enable vsedit-previewer so that it is accessible from Terminal.

[anonymlol]

I've compiled a few of the plugins and scxvid-standalone (Apple Silicon).

Some of the plugins I couldn't compile (errors here and there...)

I have tested scxvid-standalone and it works fine. I didn't have time to test the plugins yet.

Plugins

[l33tmeatwad]

Originally Posted by anonymlol

I've compiled a few of the plugins and scxvid-standalone (Apple Silicon).

Some of the plugins I couldn't compile (errors here and there...)

I have tested scxvid-standalone and it works fine. I didn't have time to test the plugins yet.

Plugins

Awesome! One thing I would recommend is that you fix your dependancies, for example BestAudioSource is looking for the ffmpeg libs in "/opt/homebrew/opt/ffmpeg/lib/", you should compile the ffmpeg static libs instead so they are built in and BAS don't need them. You can use otool -L to check the libs plugins are using. Anything in /usr/lib is fine as all systems share those. Also, I would recommend compiling the minimum version as 11 for compatibility.

[anonymlol]

I really should have read your setup post till the end. Thanks for the advice. I'll read up on it and try again.

Can you tell me how you compiled VSEdit? Whenenver I compile it, it's full of bugs and can't find the library/plugins directory.

I'm also getting an error when compiling libass (following your guide). Something about the 'freetype' version being too low.

[l33tmeatwad]

Unfortunately I don't get any errors so it may be that some code might need to be changed for ARM. As for finding the plugins directory, did you install VapourSynth via Brew?

[anonymlol]

I tried brew, but then it also wouldn't find the plugins even though I followed the instructions in your first post.

Your installer is the only thing that works. Even compiling VapourSynth + VSEdit myself (following your guide), it can't find/load the plugins.

[l33tmeatwad]

Did you manually create the default plugins path? Since VapourSynth doesn't come with any plugins anymore it doesn't create it by default.

[anonymlol]

I see, maybe I made a mistake somewhere with the folders. I'll experiment a bit.

The installer creates the folders in a different location than your instructions on the first post. Maybe I should try the same location as the installer.

Installer folder locations:

VS Plugins
/Library/Frameworks/VapourSynth.framework/lib/vapoursynth

VS Scripts
/Library/Frameworks/VapourSynth.framework/lib/python3.11/site-packages

VS Libraries
/Library/Frameworks/VapourSynth.framework/lib

VS Executables
/Library/Frameworks/VapourSynth.framework/bin

And for brew (according to first post)

ln -s /usr/local/lib/vapoursynth $HOME/Desktop/VapourSynth/Plugins
ln -s /usr/local/lib/python3.9/site-packages $HOME/Desktop/VapourSynth/Scripts

[l33tmeatwad]

So /usr/local/lib/VapourSynth is the default autoload path. Normally I'll create a symbolic link because I create a framework as opposed to a regular install so updates don't break the install.

EDIT: I just realized you left out the first part for brew users:

mkdir -p /usr/local/lib/vapoursynth
mkdir -p "$HOME/Library/Application Support/VapourSynth"
touch "$HOME/Library/Application Support/VapourSynth/vapoursynth.conf"
echo UserPluginDir=/usr/local/lib/vapoursynth >> "$HOME/Library/Application Support/VapourSynth/vapoursynth.conf"
echo SystemPluginDir=/usr/local/lib/vapoursynth >> "$HOME/Library/Application Support/VapourSynth/vapoursynth.conf"

[anonymlol]

Yeah I skipped it on purpose because I didn't want to make the post unnecessarily long.

I'll have a closer look at everything when I have more time.

For now I'd like to share my new (quick and dirty) script to automate the first part of your guide (setting up tools). I'll do the rest (setting up the vs framework) later.

edit: updated script is now on github
edit2: finally done on the script to build vapoursynth framework, see here
edit3: libass works now, it failed before because it was missing: PKG_CONFIG_PATH=/Library/Frameworks/VapourSynth.framework/lib/

Btw, VSEdit still throws errors. The folders and links are created via the script according to your instruction post.

VapourSynth plugins manager: Failed to load vapoursynth library!
Please set up the library search paths in settings.
Failed to load vapoursynth script library!
Please set up the library search paths in settings.
Failed to load vapoursynth script library!
Please set up the library search paths in settings.

[anonymlol]

From your post here

sudo ln -s /Library/Frameworks/VapourSynth.framework/lib/libvapoursynth.dylib /usr/local/lib/libvapoursynth.dylib
sudo ln -s /Library/Frameworks/VapourSynth.framework/lib/libvapoursynth-script.dylib /usr/local/lib/libvapoursynth-script.dylib
sudo ln -s /Library/Frameworks/VapourSynth.framework/lib/libvapoursynth-script.0.dylib /Library/Frameworks/VapourSynth.framework/lib/libvapoursynth-script.0.dylib
sudo ln -s /Library/Frameworks/VapourSynth.framework/lib/vapoursynth /usr/local/lib/vapoursynth
sudo ln -s /Library/Frameworks/VapourSynth.framework/lib/pkgconfig/vapoursynth.pc /usr/local/lib/pkgconfig/vapoursynth.pc
sudo ln -s /Library/Frameworks/VapourSynth.framework/lib/pkgconfig/vapoursynth-script.pc /usr/local/lib/pkgconfig/vapoursynth-script.pc
sudo ln -s /Library/Frameworks/VapourSynth.framework/bin/vspipe /usr/local/bin/vspipe
sudo ln -s /Library/Frameworks/VapourSynth.framework/include/vapoursynth /usr/local/include/vapoursynth

This is probably a bug (same path). I guess it's supposed to be:

sudo ln -s /Library/Frameworks/VapourSynth.framework/lib/libvapoursynth-script.0.dylib /usr/local/lib/libvapoursynth-script.0.dylib

I still can't get plugin autload to work (in vsedit). Any idea what I'm doing wrong/missing? (My build script)
The vapoursynth.conf file doesn't help either. And I noticed your installer doesn't even create it. How did you solve the autload issue? Or did you do something special when compiling vsedit?

[l33tmeatwad]

Ah, yeah that is a mistake, I'll get that fixed up. As for you script, I'll try to take a look over it soon, been super busy lately so it might take a minute to look into, nothing is looking super off from the quick glance I took.

[l33tmeatwad]

The R66 installer is now available.