Stefan-Olt / vs-plugin-build

VapourSynth plugin build system for Linux/macOS
GNU Lesser General Public License v2.1
3 stars 1 forks source link

vs-plugin-build

VapourSynth plugin build system for Linux/macOS. It is recommended to use vsrepo to install the plugins. Currently most plugins included are simple to compile (no dependencies and standard build system). Other plugins will be added over time (feel free to open pull requests).

Plugin compatibility

Default requirements:

If a plugin has higher or other requirements this is shown in the list.

Plugin list

For each category the number of currently available plugins in this repo and the total number of plugins in vsrepo is given. For a nice list of all plugins (and scripts/wheels) with more details, see the VapourSynth Database.

Name Linux (x86_64) macOS (Intel) macOS (Apple Silicon)
Color/Levels (2/5)
Curve
MatchHistogram
Deinterlacing (6/10)
Bwdif
EEDI2
NNEDI3
SangNom
TDeintMod
Yadifmod
Denoising (15/38)
Bilateral
BM3D
Cnr2
degrainmedian
DFTTest
FFT3DFilter
FluxSmooth
Frfun7
HQDn3D
MiniDeen
RemoveGrain
TBilateral
TemporalMedian
TemporalSoften2
TTempSmooth
Dot Crawl and Rainbows (6/8)
Bifrost
DeCross
DeDot
SmoothUV
SSIQ
TComb
Inverse Telecine (2/3)
IT
TIVTC
Other (23/75)
AddGrain
AWarpSharp2
CTMF
DCTFilter
Deblock
DeblockPP7
DeLogo
DePan
FieldHint
fillborders
Histogram
LGhost
Median
Miscfilters (obsolete)
MotionMask
MSmoosh
MVTools
NoiseGen
RemapFrames
Retinex
TCanny
TEdgeMask
vs-noise
Resizing and Format Conversion (4/13)
Descale
fmtconv
JincResize
Tonemap
Sharpening (2/2)
ASharp
CAS - Contrast Adaptive Sharpening ✅ (10.13)
Source/Output (4/13)
BestSource ✅ (10.15)
ColorBars
FFmpegSource2
QRCodeSource
Subtitles (0/5)

Plugin issues

Not all plugins with build definitions in the repository build correctly on all platforms at the moment:

linux-glibc-x86_64

currently all plugins can be build

darwin-x86_64

darwin-aarch64

Howto fix build issues:

These are a few ideas how to fix build issues on Darwin/macOS:

If you like to help fixing these issues it is recommended that you open an issue on the plugin repository (or create an pull request that fixes the issue there) with the hope the author will release a new version with a fix. If the plugin is unmaintained (or the maintainer does not respond) you can may open an issue here, so the patch can be included in the build system (less desirable option).