These objects contain an internal instance of the native C structure, have a type property providing the type name, and use getters and setters to expose the underlying native properties. Values are automatically marshalled and unmarshalled between native and Javascript representations. In design, each of the main structures ( struct) of FFmpeg have mappings to Javascript objects.

Note that the eventual aim is that every example in the FFmpeg source tree will have a corresponding example for Node.js. use ( async ( ctx ) => run ( ) įor mode examples, see the examples folder. For example, to access a key frame near to 42.5 seconds from the start of a file called GOPR9502.MP4: Beam coder uses promises and so the code for the server works well with koa:Ĭonst beamcoder = require ( 'beamcoder' ) const Koa = require ( 'koa' ) const app = new Koa ( ) app. The following code snippet is an app that allows a user to access key frames of video from the current folder, e.g.MP4 media files on a camera memory card, as JPEG images in a browser. Long running media processing operations are asynchronous, running as promises that execute native code separately from the main event loop. Work is configured with Javascript objects and jobs execute over data buffers that are shared between Javascript and C. Rather than using the filesystem and controlling the FFmpeg as an external command line process, the beam coder executes functions of the FFmpeg libav* libraries directly. The aim of this module is to facilitate access to the capabilities of FFmpeg - including media muxing, demuxing, encoding, decoding and filtering - from Node.js applications.

Node.js native bindings to FFmpeg with support for asynchronous processing via streams and promises.

Ffmpeg documentation doxygen download