Comments (3)
snobu
commented on August 16, 2024
I would suggest a naming convention for the ffmpeg binary rather than additional metadata file.
from ffmpeg-static.
derhuerst
commented on August 16, 2024
True, that would work as well. We could follow the Go or Rust binary naming scheme here.
from ffmpeg-static.
terribleplan
commented on August 16, 2024
The benefits I see with something like an ffmpeg.json or similar is that it:
- Allows for for never having to list the directory and have conditional code for the platform as long is it is not changed between build/install time and runtime. (Store
"filename": "ffmpeg.exe"to make windows just work). Else you would have to list the dir, see what is in it, find something that starts with "ffmpeg-", detect platform and arch by splitting on "-", figure out what to do if there are multiple, etc... - Allows for drift detection. (Store
"hash": "sha256 of the file", allows for detecting if something has gotten weird/been modified/etc) Could be an interesting future feature, at least debugging tool somewhat.
from ffmpeg-static.
Related Issues (20)
- update to ffmpeg 5.1, 5.1.1, 5.1.2 & 6.0 HOT 20
- Python Runtime Environment? HOT 1
- npm install latest version 5.0.2, FFMPEG_BINARIES_URL variable is invalid HOT 1
- install issue HOT 1
- Build error - ffmpeg path not assignable to type string HOT 6
- Web hosting HOT 5
- Proposal: Put the binary under `node_modules/.bin/`
- When can the `ffmpegPath` be `null`? HOT 2
- Cannot install ffpmeg-static HOT 1
- I can't find cutting stream function on ffmpeg-static HOT 2
- How difficult would it be to create a similar package for libav? HOT 1
- Issue running on AWS Lambda HOT 1
- bug: Install Error On Linux (incompatiblity issues?) HOT 3
- bug: Error: spawn /home/container/node_modules/ffmpeg-static/ffmpeg EAGAIN HOT 9
- bug: unable to install with nvm HOT 3
- bug: Missing https protocol HOT 1
- update to ffmpeg 6.1 HOT 7
- ffmpeg file without the exe extension on window HOT 3
- bug: Can you update npm packages to 6.0 HOT 1
- bug: When, I'm trying to extract frames, it is working fine on localhost. But, after deployment on GCP, it is not extracting frames. How should I fix it?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ffmpeg-static.