vapoursynth-sys

Crates.iovapoursynth-sys
lib.rsvapoursynth-sys
version0.4.1
sourcesrc
created_at2018-01-29 16:55:44.233692
updated_at2024-09-15 11:11:42.401234
descriptionRust bindings for vapoursynth and vsscript.
homepage
repositoryhttps://github.com/YaLTeR/vapoursynth-rs
max_upload_size
id48806
size3,338,834
Sergey Bugaev (bugaevc)

documentation

https://docs.rs/vapoursynth-sys

README

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.

Commit count: 271

cargo fmt