completely disable logging (optional, defaults to false) set a custom () logging instance (optional, default null which will cause fluent-ffmpeg to spawn a winston console logger) default priority for all ffmpeg sub-processes (optional, defaults to 0 which is no priorization) timout of the spawned ffmpeg sub-processes in seconds (optional, defaults to 30) You have to supply an config object to the constructor containing at least the input source (either a ReadableStream or a filepath). Basicsįluent-ffmpeg is always initialized using the returned class of your initial (and only) require call. You find a lot of usage examples (including a real-time streaming example using flowplayer and express!) in the examples folder. Make sure your ffmpeg installation is up-to-date to prevent strange assertion errors because of missing codecs/bugfixes. If you want to re-generate the test coverage report (filed under test/coverage.html), run

To run unit tests, make sure have mocha installed on your system (registered as devDependency in npm config).įor constant checking your test install grunt globally ( npm uninstall -g grunt & npm install -g grunt-cli & npm install grunt)

$ git submodule add git:///schaermu/node-fluent-ffmpeg.git vendor/fluent-ffmpeg Tests Now including input streaming support (means you can convert on-the-fly using an input- and an outputstream)! Sorry for the long period of inactivity, i had to settle some private stuff! Now back in full effect :) Installation In order to be able to use this module, make sure you have ffmpeg installed on your system (including all necessary encoding libraries like libmp3lame or libx264). This library abstracts the complex command-line usage of ffmpeg into a fluent, easy to use node.js module.

Node fluent ffmpeg