pietrop / ffmpeg-static-electron

ffmpeg static binaries for Mac OSX and Linux and Windows

ffmpeg-static-electron

The module returns a file path to the binary for the target operating system.

It is a modified version from the original ffmpeg-static to use electron-builder file macros in package.json, where OS name are mac, linux or win

In ffmpeg-static, recognising the target OS is done with os.platform() where mac os x is recognised asdarwin rather then mac.

The need to tailor ffmpeg-static to use with electron-builder came from a use cases such as that of autoEdit.io.

See here for more info on How to package ffmpeg with the fluent-ffmpeg node library in electron, so that you only ship the binaries for the target operating system

There is also ffprobe-static-electron

---

ffmpeg static binaries for Mac OSX and Linux and Windows

Installation

This module is installed via npm:

$ npm install ffmpeg-static-electron

Example Usage

Returns the path of a statically linked ffmpeg binary on the local filesystem.

var ffmpeg = require('ffmpeg-static-electron');
console.log(ffmpeg.path);
// /Users/eugeneware/Dropbox/work/ffmpeg-static/bin/darwin/x64/ffmpeg

Currently supports Mac OS X (64-bit), Linux (32 and 64-bit) and Windows (32 and 64-bit).

Currently version 3.1 is installed for Mac and Linux, and 3.0.1 for Windows.

I pulled the versions from the ffmpeg static build pages linked from the official ffmpeg site. Namely:

• 64 bit Mac OSX
• 64 bit Linux
• 32 bit Linux
• 64 bit Windows
• 32 bit Windows

NB: Open to pull requests to update this module with the latest versions.

Ideally I'd like to dynamically pull the latest version down, but this requires access to 7-zip which and being able to untar xz files.

And I couldn't find a good js-only decoders for these files either.

So, for now it's just embedded binaries.

ffmpeg-static-electron's Issues

thanks so mush

太棒了，感谢你们成功解决我的bug

License Concerns

So this repo seems to be licensed under a custom BSD like license.

But you're clearly dependent on FFmpeg, which is GPLv2/GPLv3 and (or if properly compiled and documented, LGPLv2/LGPLv3).

I see you're re-distributing binaries for FFmpeg. Not only that, you're re-distributing binaries built by Zeranoe. All of the Zeranoe builds are expressly (L)GPLv3 (with nightly builds available only under GPLv3):

FFmpeg has some notes on license compliance, and I'm not convinced your project is compliant. Worse, by licensing your project under a BSD-like license without any mention that the FFmpeg binaries you're distributing are GPLv3, I think you mislead others who might use this project to include FFmpeg in projects that aren't compatible with GPLv3.

I would recommend you reach out to the FFmpeg project to see what changes they might recommend. The easiest paths are probably to re-license this project under GPLv3 or stop distributing FFmpeg binaries and instead automate the fetching of those binaries. Either way, I do think you need to be explicit about what license FFmpeg is using.

Why does electronic report an error after packaging ？

please update ffmpeg version, windows mouse hidpi issue has been repaired in new version

please update ffmpeg version, windows mouse hidpi issue has been repaired in new version

Cannot find the ffmpeg in dist_electron

After installing the library the ffmpeg file cannot be found in dist_electron in a newly created electron 3 project making the application fail.