6 releases (3 breaking)

0.4.0 Jul 13, 2022
0.3.0 Oct 22, 2019
0.2.0 Jun 16, 2018
0.1.2 Apr 2, 2018
0.1.1 Mar 24, 2018

#70 in Video

Download history 124/week @ 2024-07-21 210/week @ 2024-07-28 120/week @ 2024-08-04 161/week @ 2024-08-11 111/week @ 2024-08-18 162/week @ 2024-08-25 147/week @ 2024-09-01 104/week @ 2024-09-08 158/week @ 2024-09-15 170/week @ 2024-09-22 180/week @ 2024-09-29 156/week @ 2024-10-06 141/week @ 2024-10-13 185/week @ 2024-10-20 201/week @ 2024-10-27 208/week @ 2024-11-03

762 downloads per month
Used in 8 crates (4 directly)

MIT/Apache

2MB
43K SLoC

C++ 24K SLoC // 0.1% comments C 8K SLoC // 0.1% comments Rust 5K SLoC // 0.0% comments Visual Studio Project 2K SLoC Cython 2K SLoC // 0.0% comments Python 1K SLoC // 0.2% comments Pascal 288 SLoC // 0.0% comments Batch 270 SLoC Visual Studio Solution 167 SLoC Automake 157 SLoC Shell 22 SLoC

vapoursynth-rs

crates.io Documentation Actions Status

ChangeLog

Documentation for the master branch with all features enabled

A safe wrapper for VapourSynth, written in Rust.

The primary goal is safety (that is, safe Rust code should not trigger undefined behavior), and secondary goals include performance and ease of use.

Functionality

Most of the VapourSynth API is covered. It's possible to evaluate .vpy scripts, access their properties and output, retrieve frames; enumerate loaded plugins and invoke their functions as well as create VapourSynth filters.

For an example usage see examples/vspipe.rs, a complete reimplementation of VapourSynth's vspipe in safe Rust utilizing this crate.

For a VapourSynth plugin example see sample-plugin which implements some simple filters.

vapoursynth-sys

crates.io Documentation

ChangeLog

Raw bindings to VapourSynth.

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