-
-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
provide ffprobe binaries again? #19
Comments
I don't think putting it in the Publishing a second |
Ha yes great idea! |
@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? |
Cool!
The idea is to use your npm package just like it is being used right now: to ship
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! |
@derhuerst great, i can probably send a PR within the next 10 days. |
Any updates on this? 😄 |
Ping. Any update? |
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 Still, I‘d like to avoid downloading
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
|
|
Hello, I’m from a company called Storykit and we’re using both 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. |
What's the progress on this? I'm also in need of ffprobe |
I'm currently looking into where it's possible to download the the Darwin ARM64 for Current progress can be tracked in my PR: #113 |
fixes #19 closes #113 Co-Authored-By: Jannis R <[email protected]>
fixes #19 closes #113 Co-Authored-By: Jannis R <[email protected]>
@joshwnj This repo is now ready for publishing |
bump @joshwnj would be great to have this all in one package |
bump @joshwnj :) |
🙏 @joshwnj |
@derhuerst is this still an issue? I'm trying to install |
If @joshwnj can't give write access, then maybe @derhuerst can publish it under a different name? |
Would it be possible to keep the ffprobe executable and also export the path to ffprobe ?
The text was updated successfully, but these errors were encountered: