VapourSynth Installer, Applications, & Plugins for macOS (Intel) [Archive] - Page 2

Frank Booth

29th January 2020, 11:24

If all of this is a little overwhelming I would recommend my VapourSynth 101 guide (http://www.l33tmeatwad.com/vapoursynth101) which goes step by step to walk you through how everything works and how to use filters. As for installing, the VapourSynth installer linked on the first post of this thread may be a good start, however if you do not want to deal with downloading plugins then AMVpack (https://www.amv101.com/software/amvpack) may be a good option as well. AMVpack was a project I started years ago that helps (AMV) video editors get started quickly and easily with advanced tools so they don't have to deal with the complications of setting everything up or compiling things.

I have followed your instructions and have VS working up to a point. I don't really know what I'm doing but I have the following script working because the preview works.

import vapoursynth as vs
core = vs.get_core()
video = core.ffms2.Source(r'/Volumes/music/forencoding/gabrielle.mov')
video.set_output()

When I attempt the following script (which I have simply copied from your thread)..

import vapoursynth as vs
core = vs.get_core()
import havsfunc as haf

clip = core.ffms2.Source(source="/Volumes/music/forencoding/gabrielle.mov")
clip = core.resize.Bicubic(clip=clip,format=vs.YUV422P8)
deint = haf.QTGMC(clip, Preset='Fast', TFF=True)
deint.set_output()

I get the following error:

Failed to evaluate the script:
Python exception: Resize error: Matrix must be specified when converting to YUV or GRAY from RGB

Traceback (most recent call last):
File "src/cython/vapoursynth.pyx", line 1847, in vapoursynth.vpy_evaluateScript
File "/Users/macbook/Desktop/first script.vpy", line 16, in
File "src/cython/vapoursynth.pyx", line 1739, in vapoursynth.Function.__call__
vapoursynth.Error: Resize error: Matrix must be specified when converting to YUV or GRAY from RGB

What I am trying to achieve is the highest quality deinterlace. I am not requiring any other functionality. Deinterlacing is my only goal. Can you please walk me through the steps, in language that would suit somebody who is completely over his head (filmmaker not programmer)? Also does the AMV pack include QTGMC, which I understand is the best deinterlacer? Thank you so much.

Lypheo

29th January 2020, 13:05

I get the following error:

Failed to evaluate the script:
Python exception: Resize error: Matrix must be specified when converting to YUV or GRAY from RGB

As the error message very clearly states, you need to specify a YUV matrix. Try:
core.resize.Bicubic(clip=clip,format=vs.YUV422P8, matrix_s="709")

l33tmeatwad

29th January 2020, 18:58

I will update my guide to point out RGB sources need to be converted to use certain filters earlier in the guide to avoid this in the future, thanks for catching that.

Myrsloik

29th January 2020, 20:05

I will update my guide to point out RGB sources need to be converted to use certain filters earlier in the guide to avoid this in the future, thanks for catching that.

Poke the script authors too, proper checks are more helpful.

Nico8583

14th February 2020, 11:55

Hi, I would like to try VapourSynth for Windows to replace AviSynth but I don't find FFMS2 or L-SMASH plugin. Any link to download ? Thank you !

shph

20th March 2020, 07:10

l33tmeatwad, i would like to appreciate you for sharing those plugins and installer packages. This definitely simplifies a lot of things.
As a new user, i attempt to connect VapourSynth to Hybrid.app on macOS and expect to use QTGMC deinterlace. I must admit that it was rather complicated adventure. I spend more than week to collect info from endless different forums to make it work. In the end i create package and guide that finally just works out of box:

VapourSynth + QTGMC Deinterlace + Hybrid UI FAQ for macOS. Currently it discussed and tested here https://forum.selur.net/showthread.php?tid=1279&pid=6894#pid6894 and here https://forum.blackmagicdesign.com/viewtopic.php?f=3&t=109259

I also have huge request for your VapourSynth Installer - Please include all plugins and Hybrid scripts inside.

It is total pain to download plugins one by one from Mediafire (it don't allow folder download for free).
People just lost inside those endless folders, versions and variations of Plugins and scripts, and this is the main source of problems: Missing Plugins, Missing Dependencies, Dependencies placed in wrong folder, Missing, Scripts, Wrong location, Alias link deleted by accident, Original .dylib file replaced and Alias link no more works. Error, Error, Error.

Why don't just include into VapourSynth installer all possible plugins, dependencies and scripts so it will work for any possible task and with any possible UI wrapper without additional adjustment? Full plugins package weights only 50MB but may save weeks and months of wasted time.

P.S. Hybrid is no more developed for macOS, but it still works ok. As you may see in Hybrid forum, i was able to update FFmpeg and MKVToolNix inside Hybrid. Selur also suggsted to update MP4Box binary and .dylib files, but he is not sure which files are safe to replace on macOS. Maybe you can suggest something here: https://forum.selur.net/showthread.php?tid=1279&pid=6903#pid6903

l33tmeatwad

20th March 2020, 15:22

I originally had started out with all the plugins compiled into one package, but that is a bit much if someone just wants to just upgrade VapourSynth. I understand it can be a pain to download all the plugins individually, however unless I find a better way to host them it is just how it has to be for now.

The installer was made with the software Packages (http://s.sudre.free.fr/Software/Packages/about.html), my recommendation to make it easier for others to use Hybrid would be to create a companion installer that has the dependencies and places them where they need to go. If you want I am more than happy to help you get started and answer any questions. I'm involved in a lot of different things and I just don't have the capacity to cater to every software that has certain dependancies, I actually haven't had enough time to keep up to date with all the plugins since no one else is contributing at this time.

As for upgrading stuff, I would not recommend replacing system files at all, I would replace things either in the app itself or self contain them like I did with the VapourSynth installer and create link files if needed. Dependency locations for dylib files can actually be changed, if you need any help with this feel free to contact me as I know it can get a bit complicated trying to avoid replacing anything on the system level.

shph

21st March 2020, 09:21

For those who just wants to upgrade VapourSynth, you may add option to installer to select VapourSynth with basic plugins or VapourSynth with all plugins selected with checkboxes. It is so simple. Almost every Mac installer pkg have option like this.

New versions of FFmpeg and MKVToolNix i replaced inside Hybrid works just great. Few people on forums (including me) tested it over week without any issues. The main reason for me to use updated FFmpeg - is updated version of ProRes codec with a lot of bugfixes.
As i understand MP4Box is sort of h264 related part so it is less critical for me. If replacing dylib files is not safe, let's keep things without changes yet.

Selur

21st March 2020, 09:30

to clarify about the .dylib files: the files I meant are not system files but files inside the MacOS folder of the Hybrid.app which would only influence tools in the Hybrid MacOS folder not system wide, so only thin that can break through replacing them is a tool in the Hybrid MacOS folder to not work

l33tmeatwad

28th March 2020, 20:27

VapourSynth R49 installer is now up with Zimg updated to 2.9.3 and Python updated to 3.7.6. Make sure to backup any added scripts from site-packages before installing as it will remove the Python 3.6 folders. You can access the site-packages folder from the "Add Scripts" shortcut in the VapourSynth desktop folder.

UPDATE: I may update this for Python 3.8 later, however I wanted to go ahead and get this out there and I had already updated my framework to 3.7 and knew it worked.

l33tmeatwad

10th May 2020, 04:10

I apologize for the delay on getting the R50 installer out, working on rebuilding the base libraries and upgrading Python to 3.8. Should have it out Monday or Tuesday due to my schedule.

l33tmeatwad

12th May 2020, 01:42

VapourSynth R50 Installer is up, lots of things were updated, which includes Cython (0.29.17), FreeType (2.10.2), Fribidi (1.0.9), LibWEBP (1.1.0), Python (3.8.2), and VapourSynth (R50). As with the last update, since it's moving from 3.7 to 3.8 (should be the last shift for a while) you will need to backup site-packages (the scripts shortcut on the desktop) before installing.

l33tmeatwad

13th May 2020, 15:10

Forgot I had not added it, but D2V Witch v3 is now available.

l33tmeatwad

14th May 2020, 03:41

Updated & recompiled the plugins D2VSource, FFMS2, LSMASHSource with static libs for the dependancies so that they won't need to be downloaded separately.

l33tmeatwad

17th May 2020, 00:52

While everyone should be using R50, I went ahead and updated the R49 installer to have Python 3.8 as well. In addition to that, I started the move away from shared dependancies for most things so it's a bit less complicated. I will be looking into updating some plugins that can be compiled with the dependencies build in to reduce some complications for less experienced users.

shph

17th May 2020, 01:33

Thanks for release again! Hope VapourSynth 50 on macOS will work in Hybrid same as 49 worked.
I see you upload a folder with scripts "havsfunc-200414" Are those scripts required for VapourSynth-R50? Should i put them to python "site-packages" folder?

shph

17th May 2020, 02:04

Updated & recompiled the plugins D2VSource, FFMS2, LSMASHSource with static libs for the dependancies so that they won't need to be downloaded separately.

So VapourSynth 50 Installer installs old versions of those plug-ins?
Should i just download new versions from MediaFilre folder and replace them?

This makes things even more complicated for new users...

l33tmeatwad

17th May 2020, 02:06

So VapourSynth 50 Installer installs old versions of those plug-ins?
Should i just download new versions from MediaFilre folder and replace them?

This makes things even more complicated for new users...
No, R50 should have the latest version, however with those I chose to use the shared libs as it would have bloated the installer. The downloadable versions are just there so if someone compiles VapourSynth or uses brew to install it they can just snag those plugins without the need for also snagging dependancies.

shph

17th May 2020, 02:09

Ok. Got it.
By the way it seems some mistake in naming:
VapourSynth R50: libffms2.dylib
Downloaded from Mediafire: libffms2.4.dylib

l33tmeatwad

17th May 2020, 02:16

Ok. Got it.
By the way it seems some mistake in naming:
VapourSynth R50: libffms2.dylib
Downloaded from Mediafire: libffms2.4.dylib
Just fixed that. I try to keep things the same across the board, but I messed that one up as it should just be libffms2.dylib.
Thanks for release again! Hope VapourSynth 50 on macOS will work in Hybrid same as 49 worked.
I see you upload a folder with scripts "havsfunc-200414" Are those scripts required for VapourSynth-R50? Should i put them to python "site-packages" folder?
I just uploaded that with the date I put the package together because someone on Twitter was having a hard time getting hasvfunc to work and I was trying to help them make sure they had everything.

l33tmeatwad

11th June 2020, 03:16

Added D2V Witch v4.

l33tmeatwad

12th June 2020, 21:55

BM3D, DCTFilter, DFTTest, EEDI3m, FFT3DFilter, MVTools, and NNEDI3CL were all just updated or recompiled using static libs for the dependancies so that the dependancies will not need to be downloaded separately. I have removed the previous versions and the dependancies to avoid confusion and issues.

shph

13th June 2020, 01:07

Thanks for update! Can you please explain further how to deal with your new "recompiled using static libs" updates? I just usually install all your plug-ins from MediaFire folder.
Is it enough just replace old versions with new versions of BM3D, DCTFilter, DFTTest, EEDI3m, FFT3DFilter, MVTools, and NNEDI3CL in vapoursynth folder?
Could it be a conflict if i didn't delete old dependencies? I'm not sure which exact dependencies use each of these plug-ins. What if some same dependencies used by other plug-ins?

l33tmeatwad

13th June 2020, 01:09

They just don't need the dependencies anymore, they are built in. This makes the files slightly larger, but prevents the need to download additional stuff. Replacing the old ones will work fine.

shph

13th June 2020, 02:20

Ok, seems works. I updated VapourSynth + Plugins + Scripts + Hybrid package here as usual: https://forum.doom9.org/showthread.php?t=181299

l33tmeatwad

15th June 2020, 19:30

Wobbly updated.

l33tmeatwad

16th June 2020, 15:59

Added or Updated the following plugins:
AddGrain
Descale
Fix Telecined Fades
HQDN3D
MinSharp
QRCodeSource
RemapFrames
Retinex
SangNom
SCrawl
SmoothUV
TCanny
ToneMap
VideoScope
W3FDIF

l33tmeatwad

17th June 2020, 04:36

l33tmeatwad

17th June 2020, 19:49

Added the following plugins:
MiniDeen
SceneChange
SurfaceBlur
TimeCube
tc2cfr
TNLMeans

l33tmeatwad

18th June 2020, 01:45

Small update, I've been working on a backlog of requests for a while and I'm close to finishing that, however there are a few that were requested that will not be added for following reasons:

depan: Depreciated
bilateralgpu: Depreciated
IT: Crashes
RemoveGrainSP: Crashes
DGMVSource: Windows Only
vcfreq: Windows Only
vcmod: Windows Only
vcmove: Windows Only
vctrans: Windows Only
VSFilterMod: Windows Only

This does not mean these will never be compiled and added, however I do not have the time right now to troubleshoot and submit pull requests or fixes for ones that are broken and some are just optimized for Windows so much that they might need to be entirely reworked.

shph

18th June 2020, 05:11

MinSharp and TimeCube archives are corrupted:
https://i.imgur.com/M5VEyRW.jpg
https://i.imgur.com/p1Dz0qJ.jpg

shph

18th June 2020, 06:11

Noticed the FFMS2 included in the installer was the old copy that links to Libz even though I had removed it in favor of using the static lib. While it still works without it is possible it may have some issues with random stuff so I updated the R49 & R50 installers with a new copy and also updated LSMASHSource to the latest release. There is also a new copy of LSMASHSource in the plugin downloads location with the static libs as well and that copy uses FFmpeg 4.3.

So if i install your new version of VapourSynth-R50 there is no need to install additional separate LSMASHSource FFMS2 plugins?

By the way is it ok that ffmsindex file installed by VapourSynth-R50 (/Library/Frameworks/VapourSynth.framework/bin/ffmsindex) and ffmsindex bundled in FFMS2-2.23.1 have different size?

How do you think, may static libs versions affect apps like Hybrid?

l33tmeatwad

18th June 2020, 15:24

Wow, thanks for catching that, not sure what happened but they are fixed now!

Okay, now for the static vs shared libs discussion...to over-simplify things, when using a static library that it's like that lib is copied into the plugin instead of just adding a location of where the external lib is. I have transitioned everything over to using static libs so that they are more portable since most of the libs they link to are not very large. That said, in the installer I choose for D2V Source, FFMS2, and LSMASHSource to link to FFmpeg libs to avoid having the installer size extra bloated. The static versions are available for download for users that installed via brew or compiled the source and want an easy way to snag those plugins. Most of the time I compile them at the same time so they are essentially the same plugin just one links and the other has the copy internally for FFmpeg libs.

Now, as for the updated installer, when I was previously linking to all the library files FFMS2 also linked to libz, which I had removed from the installer since all the other plugins that linked to it were built with the static version. I did however forget to swap out the ffms2 plugin, which means that it would not be able to run any functions built in that needed it, however that just means it would either error or run differently based on how it was actually programed. I ran a few tests on my test machine and it appeared to work normally, however it may be best to either re-install OR just snag the static version for now just to avoid any issues.

Hopefully this explanation clarifies a few things.

shph

22nd June 2020, 18:07

Ok, so if same D2V Source, FFMS2, and LSMASHSource included in installer, i will not touch same separate plug-ins.
So with new static plug-ins there is no need to install additional .dylib Dependencies to /Library/Frameworks/VapourSynth.framework/lib/ ?
I guess you removed those Dependencies from Mediafire
https://i.imgur.com/RZxxEHt.jpg

l33tmeatwad

22nd June 2020, 19:58

l33tmeatwad

22nd June 2020, 20:01

In light of the recent news from Apple, I will do what I can to continue this thread to make life easier for macOS users, however I doubt I will have the cash flow to acquire a new Mac when they come out. Anyone willing to help out by building things on the new hardware once it's out feel free to reach out to me.

l33tmeatwad

12th July 2020, 18:13

I've been having problems on Catalina where using any QTGMC option above medium leads to an instant crash.

This is the script that has been working fine until recently:

I don't think havsfunc itself is the problem because QTGMC options up to "medium" work, but anything above like "slower" doesn't. There is no error message, VS editor simply crashes.

FFmpeg reports:

This applies to both the AMVPack version and the standalone installer with plugins added.
Unfortunately I'm unable to replicate this issue, is there a crash log you could post so I can narrow down exactly what plugin is crashing for you and why?

l33tmeatwad

13th July 2020, 14:57

That does appear to be the issue, found some old copies you can try, they will need the dependency placed in the Library Directory.

MVTools v19 (http://www.mediafire.com/file/e8ybvc3i7t1mn51/MVTools-v19.tar.gz/file)
MVtools v20 (http://www.mediafire.com/file/orzv1wojih8i571/MVTools-v20.tar.gz/file)

Dependency: FFTW (http://www.mediafire.com/file/7v9hu8j3chrnn7g/FFTW3F-3.3.8.tgz/file)

l33tmeatwad

13th July 2020, 18:09

Tested and can confirm it does work with the older version.

It seems someone over at the Hybrid forum (https://forum.selur.net/showthread.php?tid=1279&page=5) also reported the same problem.
I'll compile a few of the older versions, if you don't mind testing to see what the last working version is that would be helpful for narrowing down the issue.

l33tmeatwad

14th July 2020, 20:06

The two older copies you posted work without problems. I believe the last one that worked without issues for me was the one included in January/May(?) release of AMVPack and the last 2-3 updates of Vapour already had the crashing issue.
There were releases since then, if you could test those after I compile them it would be helpful for sending information along to the developer. I also want to recompile those with the dependency built in to make sure that's not somehow causing the issue.

l33tmeatwad

19th July 2020, 21:36

Added MVtools versions 20 to 22 to the downloads, if anyone who had issues with v23 please test and post the results here.

shph

20th July 2020, 11:04

l33tmeatwad

20th July 2020, 13:15

I see the size is different. Old v20 was about 1 MB, new v20 and v21 are about 2MB. New v22 and v23 are about 4.5 MB Are they all self contained versions now?
By the way, from real life point of view what is the benefit to use newer version? Is it some improvement quality or speed? Or just some new special options? I guess dramatic changes in v22 and v23 size means some fundamental changes in plug-in. Maybe just stay with stable v20?
The old version had an external dependency (fftw) and these have it built in for simplicity as needing to download and place extra dependencies confused some users. As with any software, new versions add features and the goal is to improve speed, efficiency, quality, and stability, however sometimes random glitches pop up and only affect certain systems so developers don't realize there is an issue. In this situation finding out what version was the first to be broken will hopefully norrow down what the problem is so it can be fixed in future versions.

AdamCarter

24th July 2020, 03:28

HI all i think i noted the qtgmc slow, slower, slowest And placebo crash, but the mvtools fix seems to fix that. Ii also have crashes using denoisers. Only one that seems to work is fftd3d. Would l0ve to try mosquitoNR but its not available on the mac as far as i can tell.

l33tmeatwad

24th July 2020, 15:26

I all i think i noted the qtgmc slow, slower, slowest And placebo crash, but the mvtools fix seems to fix that. Ii also have crashes using denoisers. Only one that seems to work is fftd3d. Would l0ve to try mosquitoNR but its not available on the mac as far as i can tell.
What other filters are crashing for you? Also if there is a filter you'd like to see complied feel free to look to the source code here and I'll see what I can do.

AdamCarter

24th July 2020, 22:19

What other filters are crashing for you? Also if there is a filter you'd like to see complied feel free to look to the source code here and I'll see what I can do.

Hi l33tmeatwad
First off huge thanks. Secondly, i will be checking the otheR filters. I know MCTemporaldenoise wasn’t working, really any denoiser other than fftd3d causes crash.

For other filters, I have a ton of old 80s cartoons, that it’s clear that either the source material they pulled from was lacking or the effort they used to encode it was next to none.

I know the windows version of hybrid has the ability to use waifu2x-caffe Or the gpu accelerated version waifu2x-vulcan i am looking for that or anime4k. Not necessarily to increase the resolution, but i really like the built in AI denoising specific for animation. They really clean up the lines, etc.

https://github.com/lltcggie/waifu2x-caffe/releases

https://github.com/f11894/waifu2x-ncnn-vulkan-GUI

https://github.com/bloc97/Anime4K

Thank you in advance, i dont mind if it was stand alone, but ultimately would love for the above denoisers would work on the source material before i encode to x264 or 265, so having it built into hybrid would just make it easier.

Is this your website https://www.l33tmeatwad.com/vapoursynth101/using-filters-functions
OMG, OMG, OMG if it is

Dude i wan’t to pick your brain about animation encodes.

Like i said i have tons of 80s cartoons, that could do with a Bit of noise reduction, i have the PAL dvds of NTSC cartoons which were poorly converted with blended frames like smurfs and teen wolf. Would love to pick your brain on encoding settings too.

l33tmeatwad

27th July 2020, 02:07

AdamCarter

27th July 2020, 03:30

Yeah that's my website, feel free to hit me up on discord sometime. As for the waifu filters, caffe was depreciated and the other I was having a hard time getting that to work on older versions of macOS so I haven't gotten around to testing newer version yet. I'll look into the Anime4K one in the next few weeks as I find time.

Whats the discord link?

Anime4k will apparently incorporate this denoiser.
https://github.com/bloc97/Anime4K/blob/master/glsl/Denoise/Anime4K_Denoise_Heavy_CNN_L.glsl

AdamCarter

30th July 2020, 06:51

Yeah that's my website, feel free to hit me up on discord sometime. As for the waifu filters, caffe was depreciated and the other I was having a hard time getting that to work on older versions of macOS so I haven't gotten around to testing newer version yet. I'll look into the Anime4K one in the next few weeks as I find time.

Take a look at this
https://github.com/k4yt3x/video2x

Here is a demo
https://youtu.be/mGEfasQl2Zo