You must also have ffprobe installed (it comes with ffmpeg in most distributions). Otherwise, it will attempt to call ffmpeg directly (so it should be in your PATH). If the FFMPEG_PATH environment variable is set, fluent-ffmpeg will use it as the full path to the ffmpeg executable. It may work with previous versions but several features won't be available (and the library is not tested with lower versions anylonger). Prerequisites ffmpeg and ffprobeįluent-ffmpeg requires ffmpeg >= 0.9 to work. You will find a lot of usage examples (including a real-time streaming example using flowplayer and express!) in the examples folder. We have no need for it, so we do not support it.$ git submodule add git:///schaermu/node-fluent-ffmpeg.git vendor/fluent-ffmpeg Usage The code itself should build FFmpeg on Cedar-14 but it requires more complicated setup. We use Docker with Heroku-18 build image. We expect to find binary archives with these keys: ffmpeg/$STACK/$FFMPEG_. It defaults to kc-heroku-buildpack-binaries. The AWS S3 bucket can be overridden by setting FFMPEG_S3_BUCKET config var. It defaults to whatever we have seen as the last stable version which is 4.1.1 as of this writing. Heroku stack your app is running on is something you have to configure yourself.ĭesired FFmpeg version cat be set by FFMPEG_VERSION config var. Building FFmpeg from sources during this phase is something that would be great but it is not implemented. In this phase we download pre-build binaries from AWS S3 for specified FFmpeg version and Heroku stack. We utilize only bin/compile script expected by Heroku Buildpack API.
# configuration: -prefix=/app/.ffmpeg -enable-nonfree -enable-gnutlsĪs you can ffmpeg and other FFmpeg binaries are accessible via PATH environment variable. # ffmpeg version 4.1.1 Copyright (c) 2000-2019 the FFmpeg developers # Running ffmpeg -version on ⬢ kc-ffmpeg.
0 kommentar(er)
