They should be mostly compatible, but should you encounter any issue, you may want to use the real ffmpeg instead. Package, and they are actually rebranded avconv/avprobe executables (avconv is a fork of ffmpeg). Windows users: most probably ffmpeg and ffprobe willĭebian/Ubuntu users: the official repositories have the ffmpeg/ffprobe executable in the Most features should work when using avconv and avprobe instead of ffmpeg and ffprobe, but they are not officially supported at the moment. Similarly, fluent-ffmpeg will use theĮnvironment variable if it is set, otherwise it will attempt to call it in the

You must also have ffprobe installed (it comes with ffmpeg in most distributions). It may work with previous versions but several features won't be available (and the library is not tested with lower versions anylonger).Įnvironment variable is set, fluent-ffmpeg will use it as the full path to theĮxecutable. You will find a lot of usage examples (including a real-time streaming example usingįluent-ffmpeg requires ffmpeg >= 0.9 to work. Or as a submodule: $ git submodule add git:///schaermu/node-fluent-ffmpeg.git vendor/fluent-ffmpeg Usage You can still access the code and documentation for fluent-ffmpeg 1.7 This is the documentation for fluent-ffmpeg 2.x. Installed on your system (including all necessary encoding libraries like libmp3lame or libx264). In order to be able to use this module, make sure you have

This library abstracts the complex command-line usage of ffmpeg into a fluent, easy to use node.js module.

Fluent ffmpeg cannot find ffmpeg