10 releases

0.4.1 Sep 15, 2024
0.4.0 Jul 13, 2022
0.3.0 Oct 22, 2019
0.2.2 Jun 16, 2018
0.1.0 Jan 29, 2018

#208 in Video

Download history 234/week @ 2024-07-28 123/week @ 2024-08-04 163/week @ 2024-08-11 113/week @ 2024-08-18 166/week @ 2024-08-25 149/week @ 2024-09-01 103/week @ 2024-09-08 405/week @ 2024-09-15 207/week @ 2024-09-22 208/week @ 2024-09-29 158/week @ 2024-10-06 141/week @ 2024-10-13 183/week @ 2024-10-20 199/week @ 2024-10-27 215/week @ 2024-11-03 128/week @ 2024-11-10

745 downloads per month
Used in 9 crates (via vapoursynth)

MIT/Apache

2MB
39K SLoC

C++ 24K SLoC // 0.1% comments C 8K SLoC // 0.1% comments Visual Studio Project 2K SLoC Cython 2K SLoC // 0.0% comments Python 1K SLoC // 0.2% comments Rust 717 SLoC // 0.0% comments Pascal 289 SLoC // 0.0% comments Batch 271 SLoC Visual Studio Solution 168 SLoC Automake 158 SLoC Shell 23 SLoC // 0.1% comments

Contains (obscure autoconf code, 22KB) source-files/vapoursynth/configure.ac

vapoursynth-sys

crates.io Documentation

ChangeLog

Raw bindings to VapourSynth.

Check out vapoursynth-rs for a safe Rust wrapper.

Supported Versions

All VapourSynth and VSScript API versions starting with 3.0 are supported. By default the crates use the 3.0 feature set. To enable higher API version support, enable one of the following Cargo features:

  • vapoursynth-api-31 for VapourSynth API 3.1 (R26)
  • vapoursynth-api-32 for VapourSynth API 3.2 (R27)
  • vapoursynth-api-33 for VapourSynth API 3.3 (R30)
  • vapoursynth-api-34 for VapourSynth API 3.4 (R30)
  • vapoursynth-api-35 for VapourSynth API 3.5 (R38)
  • vapoursynth-api-36 for VapourSynth API 3.6 (R47)
  • vsscript-api-31 for VSScript API 3.1
  • vsscript-api-32 for VSScript API 3.2

To enable linking to VapourSynth or VSScript functions, enable the following Cargo features:

  • vapoursynth-functions for VapourSynth functions (getVapourSynthAPI())
  • vsscript-functions for VSScript functions (vsscript_*())

Building

Make sure you have the corresponding libraries available if you enable the linking features. You can use the VAPOURSYNTH_LIB_DIR environment variable to specify a custom directory with the library files.

On Windows the easiest way is to use the VapourSynth installer (make sure the VapourSynth SDK is checked). The crate should pick up the library directory automatically. If it doesn't or if you're cross-compiling, set VAPOURSYNTH_LIB_DIR to <path to the VapourSynth installation>\sdk\lib64 or <...>\lib32, depending on the target bitness.

License

Licensed under either of

at your option.

Dependencies