editly
editly copied to clipboard
mifi
Include ffmpeg
Might add the ffmpeg-static dependency, then no need for system ffmpeg. (with an option to use a custom ffmpeg path) But it does not work on raspberry pi, need to see if it crashes npm install or what happens
looks like ffprobe is separate
https://github.com/eugeneware/ffmpeg-static/issues/19
??
https://github.com/joshwnj/ffprobe-static
Yeah, I'm thinking about building a reusable ffmpeg GitHub Action and a repository that can build ffmpeg for many platforms in many different variants and allow users to fork the repo for their own build configuration, but it's kind of a big job.
looks like someone has done something similar before:
https://github.com/vot/ffbinaries-api https://github.com/vot/ffbinaries-node
I found that one too, but there seems to be some issues with those builds not really being static builds. I haven't tried them myself and I'm not sure where he gets the builds from, but I think that the official builds from ffmpeg.org are preferred because they are well tested by a lot of people. And it seems kind of abandoned, also it doesn't have the latest 4.2.2 version: https://github.com/vot/ffbinaries-prebuilt/releases
oh... for some reason I thought this repo https://github.com/vot/ffbinaries-api included the code for automatically compiling from nightly builds or something :/
no. it just contains references to downloads from the other repo. So the question is, how are the ffmpeg-prebuilt being built. I've created an issue for that
@mifi since You're discussing FFMPEG builds we're using these: https://johnvansickle.com/ffmpeg/
And they're always bringing a warning to console because editly complains on
'Unknown version string'
It's because they don't have same build string as official FFMPEG builds (e.g. ffmpeg version N-50742-ga7245adee3-static https://johnvansickle.com/ffmpeg/....
Can You please take a look on these?
FFMPeg binaries on windows don't have the same version string. I am getting this - N-101088-g6f80953554
