New FFmpeg IronWorker Stack For Easy Video Processing
FFmpeg is the leading cross-platform solution to record, convert and stream audio and video. Dealing with audio and video can eat up resources, making the activity a great fit for IronWorker by moving the heavy lifting to the background.
In the past, usage of FFmpeg with IronWorker would require that our users include and install the dependency within each worker environment. In order to streamline that process for developers, we’ve included FFmpeg in an IronWorker stack as a custom runtime environment specifically meant for video processing.
The possibilities are endless with the flexibility of FFmpeg and the processing power of IronWorker. Here are a few examples we’ve come across in working with our users, which will give you a baseline for the capabilities.
- Format Encoding
- Audio Normalization
- Audio/Video Optimization
- Metadata Analysis
- DRM Encoding/Decoding
- Screencapture Production
- Resize, Reformat and Crop Video
- Change Aspect Ratio
$ ffmpeg -i input.mp4 output.avi
pre-built libraries: ffmpeg-2.3, GPAC-0.5.1, , x264-0.142.x
supported runtimes: php-5.3, node-0.10, ruby-1.9.3p0, python-2.7
Find out more detailed info about the FFmpeg stack here.
To use, simply include “ffmpeg-2.3” in your .worker file using the stack option:
Here are a few examples of how to use the FFmpeg stack in the supported languages.
Using Ruby runtime + FFmpeg stack
Using Node.js runtime + FFmpeg stack
Using Python runtime + FFmpeg stack
Using PHP runtime + FFmpeg stack
More flexibility for our developers
Making deployment and dependency management painless is a top priority for our team. Supporting a diverse range of languages, frameworks, and packages provides our users what they need to make their Iron.io implementation successful.
We’d love to hear feedback or to even feature tutorials written by you! send me a message at: firstname.lastname@example.org.
Are there supposed to be code examples under the ‘Using Ruby..’ etc.headings at the end of the article?
Hey Dan… apologies, we just migrated our blog and the gist format changed. All examples should show up now. Cheers.
Thanks, all good now. Working like a dream so far 🙂