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

[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]

Originally Posted by 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.

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]

Originally Posted by 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.

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.