ffmpeg-static
ffmpeg-static copied to clipboard
eugeneware
provide ffprobe binaries again?
Would it be possible to keep the ffprobe executable and also export the path to ffprobe ?
I don't think putting it in the ffmpeg-static npm packages is a good idea, as they are nicely focused and already ~100mb in size.
Publishing a second ffprobe-static from this GitHub repo would work. Let's ask @joshwnj it they are willing to donate the ffprobe-static npm name for this.
@derhuerst absolutely! Makes a lot of sense.
I can also add a deprecation notice to https://github.com/joshwnj/ffprobe-static pointing people back here.
I've never changed ownership of an npm package before, is there a preferred way to approach it? If I invite you to be a maintainer will that be enough?
@derhuerst absolutely! Makes a lot of sense.
Cool!
I can also add a deprecation notice to https://github.com/joshwnj/ffprobe-static pointing people back here.
The idea is to use your npm package just like it is being used right now: to ship ffprobe binaries via npm. The difference is only that we will use one repo (i guess this one) and publish both ffmpeg-static and ffprobe-static.
I've never changed ownership of an npm package before, is there a preferred way to approach it? If I invite you to be a maintainer will that be enough?
Giving someone push access to npm for the package would be sufficient. This will be necessary once @sballesteros or someone has prepared this repo to publish both.
Great. In that case I'll keep an eye out here for when the new publishing approach is ready, and assign push access on npm then. Thanks!
By now the binaries are being downloaded on install from a GitHub Release; That changes the situation quite a bit, because the npm package won‘t be ridiculously large anymore. So let‘s add ffprobe.
Still, I‘d like to avoid downloading ffprobe unnecessarily, so adopting the ffprobe-static to be published from this repo as well would be my favorite setup. I think this can be done with a little bit of scripting:
- Change
install.jsto pick the name of the binary to be downloaded frompackage.json. - Add two directories for the two npm packaes, with minimal boilerplate inside.
- On publish, copy
install.jsand all other shared files (license, etc) into the packages‘ directories and publish them to npm.
A PR that makes these changes is very welcome!
Hello guys! Now that you're at it, any chance of doing the same for ffplay? I looked around and didn't find a solution as neat as this one...
I know it involves work, just wanted to drop the comment just in case 😅
I think once ffprobe support is added, then adding support for ffplay would be super simple, given that prebuilt ffplay binaries exist too in the source repos
Is there a MacOS ARM64 static build of ffprobe available anywhere?
- OSExperts don't seem to provide one
- http://www.zeranoe.com/ is dead, it seems
- evermeet.cx maintainer has said he has no intention to provide one
Hello,
I’m from a company called Storykit and we’re using both ffmpeg-static and ffprobe-static quite extensively for our different services so we’d thought this would be a nice way to contribute to the eco system by looking at this issue.
We’ll start of by forking this repository and get to work so we can publish the required binaries and whatnot in our own phase independent of your schedule and then we can just have a conversation along the way with our progress and the things we’ll require from you guys to finally get the changes to this repository.
I'm currently looking into where it's possible to download the the Darwin ARM64 for ffprobe, I've contacted the people at http://www.osxexperts.net/ (since we're downloading the ffmpeg binary from there) at [email protected] to see if they could provide it but they have not yet replied to me. Is there any suggestion/guidelines if we should move along without this or if anybody has an alternative source to download it from?
Current progress can be tracked in my PR: https://github.com/eugeneware/ffmpeg-static/pull/113
@joshwnj This repo is now ready for publishing [email protected], analogous to [email protected]. Can you give me (@derhuerst) write access to the npm package?
@derhuerst is this still an issue? I'm trying to install ffprobe using https://www.npmjs.com/package/ffprobe-static, but it downloads version 3.2.0 (which contains binaries for all oss) and not the one published by you. Please lmk if I'm doing something wrong
If @joshwnj can't give write access, then maybe @derhuerst can publish it under a different name?
