Git Product home page Git Product logo

ffmpeg-static's Introduction

static ffmpeg/ffprobe binaries

Static ffmpeg/ffprobe binaries for macOS, Linux, Windows.

Supports macOS (64-bit and arm64), Linux (32 and 64-bit, armhf, arm64), Windows (32 and 64-bit). The ffmpeg version currently used is 6.0.

npm version minimum Node.js version

Sources of the binaries

The binaries download script downloads binaries from these locations:

The script extracts build information and (when possible) the license file from the downloaded package or the distribution server. Please consult the individual build's project site for exact source versions, which you can locate based on the version information included in the README file.

Show your support

The npm packages include statically linked binaries that are produced by the following individuals, who have been doing this for many years. Please consider supporting and donating to them:

Building the project

The unzip, tar CLI executables need to be installed. On macOS, use brew install gnu-tar xz.

ffmpeg-static's People

Contributors

codetheweb avatar dependabot[bot] avatar derhuerst avatar douglassllc avatar emilsivervik avatar emyarod avatar eugeneware avatar jperl avatar mathieu-aubin avatar maxwellb avatar nklhtv avatar paulgalow avatar ravismsk avatar snyk-bot avatar stilist avatar thelastzombie avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

ffmpeg-static's Issues

npm registry reports dependency @derhuerst/http-basic as missing

I believe that's a NPM issue, but still it makes this package not usable ATM, so I hope the community will help somehow to work around this.

ffmpeg-static currently depends on @derhuerst/http-basic:

"@derhuerst/http-basic": "^8.2.0",

which NPM fails to install with 404 ATM :

> npm i @derhuerst/http-basic
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@derhuerst%2fhttp-basic - Not found
npm ERR! 404 
npm ERR! 404  '@derhuerst/http-basic@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/idudinov/.npm/_logs/2020-06-15T21_21_00_964Z-debug.log

Any ideas why that started happening ?
Maybe one need to just re-upload the package?

Hopefully tagging @derhuerst

thanks!

How to get absolute path?

With a electron app, when I require your module I get this object:

{
   path: "\bin\win32\x64\ffmpeg.exe"
}

The path is relative to the node_modules directory, how can I get the full absolute path?

Error: ffmpeg stream: write EPIPE

Not sure if I'm writing everything correctly. It could be an issue with my code but I'm getting an error with EPIPE.

Error: ffmpeg stream: write EPIPE at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:92:16) { errno: -32, code: 'EPIPE', syscall: 'write' }

Let me know if I possibly messed up somewhere because it is very possible. I'm using v4.1.0 of ffmpeg-static on macOS [not sure if that matters].

Multiple EACCESS errors at install.js

I recently updated the ffmpeg-static dependency in one of my projects, but I am now getting this while installing (on root user):

Error reading from cache: EACCES: permission denied, open '/root/.cache/ffmpeg-static-nodejs/718960d5a79e5a6263f198570f2db949106e38fa7c2bdb1e52fd47f7a6c6081d6d5157fe5e63a4d65baba222daf54c8f5be5958c2b34e4822d599b3b13231fb0.json'
Error reading from cache: EACCES: permission denied, open '/root/.cache/ffmpeg-static-nodejs/dd451afd5a3c5c3b643274afb5337daaae30d04dc25b2974538bb847aae4d3782cf97cb4b048ff7eb1b11d8ca1b0acbe86578291b244142e9fa5a8d280c698dd.json'
Error creating cache: EACCES: permission denied, mkdir '/root/.cache/ffmpeg-static-nodejs'
[Error: EACCES: permission denied, open '/usr/lib/node_modules/yt_mp3_downloader/node_modules/ffmpeg-static/ffmpeg'] {
  errno: -13,
  code: 'EACCES',
  syscall: 'open',
  path: '/usr/lib/node_modules/yt_mp3_downloader/node_modules/ffmpeg-static/ffmpeg'
}

This only happens on my server and with the latest ffmpeg. I am not sure what's going on.
Directly running npm install ffmpeg-static -g returns the same.

Filter missing

I have screen recorded a video where I got lot of black frames in start and end via node + ffmpeg-static

To remove the black frames I used the following command

ffmpeg -i input.mp4 -vf mpdecimate,setpts=N/FRAME_RATE/TB output.mp4

If I use this with a version installed with apt-get this command works fine, but when I use it with ffmpeg-static's ffmpeg version i got the following error.

Unable to find a suitable output format for 'mpdecimate,setpts=N/FRAME_RATE/TB' mpdecimate,setpts=N/FRAME_RATE/TB: Invalid argumen

Compress releases?

Would you be willing to compress the releases?

Using xz (LZMA2), which is usually on all Linux systems by default, the download size can be reduced by nearly 80%.

Using gzip (Deflate), which is included natively on Mac, Linux, and even Windows 10, the size can be reduced by 70%.

zip (Deflate) is supported by Windows 10 tar.exe. It's also supported by PowerShell... but the PowerShell implementation is very slow.

.rwxr-xr-x aj staff   71 MB Sun Aug 16 13:03:49 2020 ffmpeg-4.3.1-darwin-x64
.rwxr-xr-x aj staff 21.4 MB Sun Aug 16 13:03:49 2020 ffmpeg-4.3.1-darwin-x64.bz2
.rwxr-xr-x aj staff 22.7 MB Sun Aug 16 13:03:49 2020 ffmpeg-4.3.1-darwin-x64.gz
.rwxr-xr-x aj staff 15.7 MB Sun Aug 16 13:03:49 2020 ffmpeg-4.3.1-darwin-x64.xz
.rw-r--r-- aj staff 22.7 MB Wed Nov 18 17:21:51 2020 ffmpeg-4.3.1-darwin-x64.zip

One of the reasons that I like the idea of ffmpeg-static is that it saves having to download 400mb of brew. However, the size could be much smaller still.

error installing ffmpeg-static with npm command

Hi, i'm new using this node package, when i try to install it on my discord bot proyect i can't do it, cause every time i receive this error:

PS D:\Escritorio\main-bot> npm install ffmpeg-static
npm ERR! code ENOENT
npm ERR! syscall spawn git
npm ERR! path git
npm ERR! errno -4058
npm ERR! enoent Error while executing:
npm ERR! enoent undefined ls-remote -h -t ssh://[email protected]/derhuerst/http-basic.git
npm ERR! enoent
npm ERR! enoent
npm ERR! enoent spawn git ENOENT
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
this is my log file of that error
https://paste.ofcode.org/zx3pxqKd8XcDbDr5eYvUqy

Screenshot_28

support Electron: respect process.env.npm_config_arch & process.env.npm_config_platform

Because in v4 it only downloads the binary for the current operating system arch, how can I now build an electron app that includes the correct ffmpeg binary according to which target platform I am building for?

For example if I want to run electron-builder --mac --win --linux

Before v4, I would just include the correct binary from the right arch directory when building like this:

electron-builder package.json "build":

    "mac": {
...
      "extraResources": [
        "node_modules/ffmpeg-static/bin/darwin/**",
        "node_modules/ffprobe-static/bin/darwin/**"
      ],
    },
    "win": {
...
      "extraResources": [
        "node_modules/ffmpeg-static/bin/win32/x64/**",
        "node_modules/ffprobe-static/bin/win32/x64/**"
      ],
    },

See
https://github.com/mifi/lossless-cut/blob/74439d716db5ff550a1851fa5b58e30ba188c477/package.json#L108

But now this doesn't work. Any tips of how to cleanly solve this? Or isn't electron really supported by this module anymore?

Clarify possible relationship of binary builds to GPL

I am concerned that ffmpeg-static is presented by you as "BSD-3-clause" license, but you distribute ffmpeg, which is GPL/LGPL licensed. There is no source code or accompanying license for your ffmpeg static builds, so it is unclear what license they are under. This could present challenges for anyone consuming ffmpeg-static from NPM who might assume the package is under BSD-3-clause as listed.

These are my personal concerns and opinions. I am not a lawyer, and received no legal advice for this issue, nor should this issue be construed as legal advice. Thank you for your consideration.

Adding git versions

FallingSnow@917aaf3

What do ya think? For now only linux works, have to write the unzipping part for windows.

It seems that adding download support for linux ffmpeg stable will also be possible using this method.

In electron platform detected as `browser`?

Trying to package this inside an electron app and getting unsupported platform issue.

When looked into it, it turns out that for some reason it detects the platform as browser as anyone else come across this?

var os = require('os')
var platform = os.platform()
console.log(platform)
//browser

Install ffmpeg executable manually?

Hey,
I have a question regarding the usage of this wrapper, currently installed this module using npm/yarn and i see ffmpeg exec in the node modules folder.

Should the executable be run manually? I was hoping this wrapper would also execute the binary, how do i run the exec file to install ffmpeg in the respective container? (Example: when deploying to PCF or any server)

Install via npm fail on Ubuntu

▐ ╢░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╟
WARN engine [email protected]: wanted: {"node":">=10"} (current: {"node":"8.10.0","npm":"3.5.2"})
WARN engine [email protected]: wanted: {"node":">=10"} (current: {"node":"8.10.0","npm":"
> [email protected] install /usr/local/lib/node_modules/ffmpeg-static
> node install.js

/usr/local/lib/node_modules/ffmpeg-static/install.js:52
  url = new URL(url)
  ^

ReferenceError: URL is not defined
    at normalizeS3Url (/usr/local/lib/node_modules/ffmpeg-static/install.js:52:3)
    at Object.<anonymous> (/usr/local/lib/node_modules/ffmpeg-static/install.js:61:3)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3)
    at Function.Module.runMain (module.js:693:10)
    at startup (bootstrap_node.js:188:16)
    at bootstrap_node.js:609:3
npm ERR! Linux 4.15.0-1065-aws
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "-g" "ffmpeg-static"
npm ERR! node v8.10.0
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE

npm ERR! [email protected] install: `node install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node install.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the ffmpeg-static package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node install.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs ffmpeg-static
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls ffmpeg-static
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/ubuntu/npm-debug.log```

```1983 silly install [email protected] /usr/local/lib/node_modules/.staging/ffmpeg-static-dbdeacf8
1984 info lifecycle [email protected]~install: [email protected]
1985 verbose lifecycle [email protected]~install: unsafe-perm in lifecycle false
1986 verbose lifecycle [email protected]~install: PATH: /usr/share/npm/bin/node-gyp-bin:/usr/local/lib/node_modules/ffmpeg-static/node_modules/.bin:/usr/local/lib/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
1987 verbose lifecycle [email protected]~install: CWD: /usr/local/lib/node_modules/ffmpeg-static
1988 silly lifecycle [email protected]~install: Args: [ '-c', 'node install.js' ]
1989 silly lifecycle [email protected]~install: Returned: code: 1  signal: null
1990 info lifecycle [email protected]~install: Failed to exec install script
1991 verbose unlock done using /home/ubuntu/.npm/_locks/staging-3a08f0df5026584d.lock for /usr/local/lib/node_modules/.staging
1992 silly rollbackFailedOptional Starting
1993 silly rollbackFailedOptional Finishing
1994 silly runTopLevelLifecycles Starting
1995 silly runTopLevelLifecycles Finishing
1996 silly install printInstalled
1997 verbose stack Error: [email protected] install: `node install.js`
1997 verbose stack Exit status 1
1997 verbose stack     at EventEmitter.<anonymous> (/usr/share/npm/lib/utils/lifecycle.js:232:16)
1997 verbose stack     at emitTwo (events.js:126:13)
1997 verbose stack     at EventEmitter.emit (events.js:214:7)
1997 verbose stack     at ChildProcess.<anonymous> (/usr/share/npm/lib/utils/spawn.js:24:14)
1997 verbose stack     at emitTwo (events.js:126:13)
1997 verbose stack     at ChildProcess.emit (events.js:214:7)
1997 verbose stack     at maybeClose (internal/child_process.js:925:16)
1997 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
1998 verbose pkgid [email protected]
1999 verbose cwd /home/ubuntu
2000 error Linux 4.15.0-1065-aws
2001 error argv "/usr/bin/node" "/usr/bin/npm" "install" "-g" "ffmpeg-static"
2002 error node v8.10.0
2003 error npm  v3.5.2
2004 error code ELIFECYCLE
2005 error [email protected] install: `node install.js`
2005 error Exit status 1
2006 error Failed at the [email protected] install script 'node install.js'.
2006 error Make sure you have the latest version of node.js and npm installed.
2006 error If you do, this is most likely a problem with the ffmpeg-static package,
2006 error not with npm itself.
2006 error Tell the author that this fails on your system:
2006 error     node install.js
2006 error You can get information on how to open an issue for this project with:
2006 error     npm bugs ffmpeg-static
2006 error Or if that isn't available, you can get their info via:
2006 error     npm owner ls ffmpeg-static
2006 error There is likely additional logging output above.
2007 verbose exit [ 1, true ]```

Allow binary to be downloaded via proxy

It looks like the install script doesn't support downloading the binary via proxies. Would it be possible to utilize simple-get's proxy support to check for yarn/npm proxy environment variable?

conversion slow with bundled ffmpeg binary

Why is running ffmpeg from this package is more than double so slow than running the command directly on the Machine?

I can't find any solution for this.

If i run the following code it takes 35s to convert a 13min webm video to mp3.
If i run the command logged in the "start" event directly on my machine it takes only 14s

const moment = require("moment");
const ffmpegStatic = require("ffmpeg-static");
const ffmpeg = require("fluent-ffmpeg");
ffmpeg.setFfmpegPath(ffmpegStatic);

let outfile = fs.createWriteStream("music.mp3");
let infile = fs.createReadStream("video");

let startTime = moment().unix();
ffmpeg()
    .input(infile)
    .outputOptions([
        "-f mp3",
        "-vn",
        "-b:a 192k",
    ])
    .on('start', (commandLine) => {
      console.log(commandLine);
    })
    .on('error', (err, stdout, stderr) => {
        console.log(err);
    })
    .on('progress', (info) => {
        //console.log(info);
    })
    .on("end", () => {
        let endTime = moment().unix();
        console.log("Finished after " + (endTime - startTime) + "s");
    })
    .pipe(outfile);

output video is black on linux

hey i trying to record my screen using ffmpeg static but the output video is black . this my code and i am using linux ubuntu 20
i dont know this is because of linux i dont know help
this is my code

const ffmpeg = require("ffmpeg-static");
const { spawn } = require("child_process");
console.log(ffmpeg)
const process = spawn(
    ffmpeg,
  ["-probesize", "10M", "-f", "fbdev", "-r", "60", "-i", "/dev/fb0", "-f", "avi", "-"],
  { stdio: "pipe" }
);
const stream = process.stdout;


const { createWriteStream } = require("fs");

const file = createWriteStream("capture.avi");
stream.pipe(file);

Error creating cache

I try to install on docker node node:lts-slim

but gives an error:

> [email protected] install /app/node_modules/ffmpeg-static
> node install.js

Error creating cache: ENOENT: no such file or directory, mkdir '/root/.cache/ffmpeg-static-nodejs'

how to properly install it on docker? thanks

Permissions for static executables?

Probably not your issue, but how do I ensure that the executables have the proper permissions when I distribute this? In my dev environment, I had to manually set the file to executable (linux, ubuntu). How do I remove this step?

spawn \ffmpeg.exe ENOENT with nw.js (create-nw-react-app)

I'm using ffmpeg-static on a React/nw.js project and instead of const ffmpeg = require('ffmpeg-static') or import ffmpeg from 'ffmpeg-static' giving me a path to the exe it just returns \ffmpeg.exe, I've reinstalled the module, deleted node_modules and nothing worked.

I dont think nw.js is the problem since another nw.js project of mine uses ffmpeg-static and it works fine.

  • Error output
node:internal/child_process:276 Uncaught (in promise) Error: spawn \ffmpeg.exe ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:276:19)
    at onErrorNT (node:internal/child_process:476:16)
    at processTicksAndRejections (node:internal/process/task_queues:80:21)

example usage?

does this include an ffmpeg wrapper? How do I use this? Can you include an example in the readme?

FFMPEG 4.3 Audio Choppiness when Streaming or Recording WebCam

When using FFMPEG 4.3 with AVFoundation to livestream from a webcam over RTMP, the audio ends up playing back choppy. What does that sounds like? Imagine every second someone unplugging your surround sound speakers and then plugging them back in very quickly while you're trying to watch a movie almost like a heart beat. After about a day of searching around the net and trying different parameters, I decided to give my brew version of FFMPEG a try with the same settings. Low and behold, the audio didn't sound choppy! What was different? Version 4.1 installed on my system, that's what. Since there doesn't seem to be a 4.1 of ffmpeg-static, I tried the next best thing: 4.2.2. This actually solved my problem, even though someone on the issue tracker mentions that it didn't work for them in 4.2.2.

https://trac.ffmpeg.org/ticket/4513

It looks like there was a patch in older version of FFMPEG that never got applied to newest version of FFMPEG. I don't know how that didn't get merged (they use archaic source control SVN). Since 4.3 seems to be the highest version, the best plan is to rollback your version to 4.2.2. I do realize the ffmpeg-static library maintainers probably won't rollback 4.3 to 4.2.2, but for anyone coming along, hopefully this information is helpful.

Here is my test command:

node_modules/ffmpeg-static/ffmpeg -f avfoundation -framerate 30 -video_size 1280x720 -i "0:0" -vcodec libx264 -preset ultrafast -tune zerolatency -pix_fmt yuv420p -thread_type slice -slices 1 -r 30 -g 60 -b:v 2.5M -minrate:v 900k -bufsize:v 5M -maxrate:v 2.5M -acodec aac -b:a 128k -ac 2 -ar 48000 -af aresample=async=1 -bufsize 5000k -f flv rtmp://myserver.example.com:1935/live/teststream

Question about ffmpeg over http proxy

Hello, I try download video stream over http proxy and pass proxy address over -http_proxy argument (i read this in ffmpeg documentation) but this not get any effect. What i do wrong ? Please explain how i can download some stream video over proxy server ?
Thanks

support prefetched binaries via env var

I am trying to package an app which app this library as a dependency.
I cannot download anything at install-time. Everything needs to be prefetched.
It seems as if this library is not capable of having the binary prefetched.
It would be nice if it could do that.
I know only little about the whole ecosystem, but this could be relevant.

ReferenceError: URL is not defined

Cannot install npm install ffmpeg-static return error ReferenceError: URL is not defined at /node_modules/ffmpeg-static/install.js:29:3. How can I fix this?

this library license problem?

Can I use this library for commercial software?

What is the difference between this library and "node-fluent-ffmpeg"?

I now use "node-fluent-ffmpeg" and call ffmpeg binary file to do h.264 file conversion

But the ffmpeg binary file contains libx264

libx264 is a GPL license

If I use libx264 in ffmpeg

Do I also have to follow the GPL?

The question I want to ask is whether there is libx264 in the binary file of the library?

add macOS + ARM binaries from osxexperts.net

I have heard that Apple will soon release ARM based Macbooks. Which version of FFmpeg will run in this scenario ? Will the Linux based binary for ARM64 will be compatible with ARM64 Macbooks ?

Better version control

It would be nice to have more granular control over which version of ffmpeg is used. We could do this by tagging releases that include different versions of ffmpeg builds.

I'm not super familiar with publishing npm modules, but ideally, the version of the npm module would correspond with the version of ffmpeg builds. e.g. ffmpeg v2.8.3 == git release tag 2.8.3 == npm module v2.8.3

We probably don't need 100% coverage, so maybe just including the most popular versions would be ok.

Thoughts?

Gatekeeper on macOS 11 Big Sur causes SIGKILL

$ node
Welcome to Node.js v12.14.1.
Type ".help" for more information.
>
> var ffmpeg = require('fluent-ffmpeg');
undefined
> ffmpeg.setFfmpegPath(require('ffmpeg-static'))
undefined
> var proc = ffmpeg().input('public/SHTUIntro/skd.mp3')
undefined
> proc.output("output.mp3").run()
undefined
> Thrown:
[Error: ffmpeg was killed with signal SIGKILL] {
  domainEmitter: FfmpegCommand {

Intel CPU Macbook Pro.

But the script works on macOS Catalina.

Failed to download the ffmpeg README and LICENSE

During the installation these two warnings popup, nothing critical but would be awesome to either hide or fix these.

> [email protected] install /backend/node_modules/ffmpeg-static
> node install.js

Error creating cache: ENOENT: no such file or directory, mkdir '/root/.cache/ffmpeg-static-nodejs'

Failed to download the ffmpeg README.
Failed to download the ffmpeg LICENSE.

version: 4.1.0

store platform & arch information next to installed binary

#35 made clear that, in a cross-platform-packaging project using ffmpeg-static as a dependency, a second npm install should install an ffmpeg binary for a different platform/arch than before.

To enable this, install.js needs to

  1. write the platform & arch next to the binary (e.g. to ffmpeg.json).
  2. check if there's a ffmpeg.json in place, with a different platform/arch than desired. If platform & arch are equal, it can exit successfully.

install.js ELIFECYCLE error

Whenever I try to install ffmpeg-static, i get this error. I assume it has something to do with my architecture ¯_(ツ)_/¯. I'm using

Ubuntu.
Here's the full error:
`
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "i" "ffmpeg-static"
npm ERR! node v8.10.0
npm ERR! npm v3.5.2
npm ERR! code ELIFECYCLE

npm ERR! [email protected] install: node install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node install.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the ffmpeg-static package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs ffmpeg-static
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls ffmpeg-static
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /home/airone/Documents/Marsia/scr/npm-debug.log
`

I'm probably not telling enough details about this, since I've never actually created an Issue on Github and It's a little intimidating, so feel free to ask anything.

Wrong darwin/x64 version (3.3.3 - should be 3.4.2)

Version of ffmpeg-static
2.2.0

Version of ffmpeg
3.3.3

Verified manually
Extract https://registry.yarnpkg.com/ffmpeg-static/-/ffmpeg-static-2.2.0.tgz

./node_modules/ffmpeg-static/bin/darwin/x64/ffmpeg -version

ffmpeg version 3.3.3-tessus Copyright (c) 2000-2017 the FFmpeg developers
built with Apple LLVM version 8.0.0 (clang-800.0.42.1)
configuration: --cc=/usr/bin/clang --prefix=/opt/ffmpeg --extra-version=tessus --enable-avisynth --enable-fontconfig --enable-gpl --enable-libass --enable-libbluray --enable-libfreetype --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopus --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzmq --enable-libzvbi --enable-version3 --disable-ffplay --disable-indev=qtkit
libavutil      55. 58.100 / 55. 58.100
libavcodec     57. 89.100 / 57. 89.100
libavformat    57. 71.100 / 57. 71.100
libavdevice    57.  6.100 / 57.  6.100
libavfilter     6. 82.100 /  6. 82.100
libswscale      4.  6.100 /  4.  6.100
libswresample   2.  7.100 /  2.  7.100
libpostproc    54.  5.100 / 54.  5.100

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.