-
Notifications
You must be signed in to change notification settings - Fork 4
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
Cannot build ffms2-rs on Ubuntu 24.04 #35
Comments
Yep, the |
Ok, thanks for the update. I am waiting for the new version. As workaround, I am calling the ffmsindex binary from rust, but I prefer to call FFMS2 via the bindings in ffms2-rs crate because it's more performant. Unfortunately, there are too many problems currently. Thus, I decided to go for the workaround. |
Yep, it's a good workaround, let's hope the third-party crate will be released soon, they are working on it |
Which crate is it? |
Ok, they have just released a new version https://crates.io/crates/ffmpeg-the-third, so we can go on with the refactoring |
BTW, since you are the maintainer of this crate you must have some knowledge in the FFmpeg area, and thus you might be able to answer a question: The only 2 things that I need about a video file for my use case are (1) a list of key frame numbers, and (2) the timestamp of each frame. Currently, I use ffmsindex to get this info. Are you aware of a more "direct" way to get this info? With "direct" I mean without using FFMS2? I tried out video-rs, for example. VBut this crate consumes quite some time to retrieve information about frames. Thanks! |
Actually, I've decided to port What is |
video-rs is yet another FFmpeg wrapper |
Sorry for the late reply, but I'm pretty busy in this period. If you want to speed up the release of a new Three things should be done in order to branch it in
You can open a pull request if you want and I can review it step by step. Feel free to rebase, squash my commits without any problem |
Hi,
when building ffms2-rs from the latest code version of the repo, I get the following error:
This error occurs with Ubuntu 24.04 on x86_64 and arm64. It does not occurs on Arch Linux, neither for x86_64 nor for arm64. Do you have any idea why that happens?
Thanks!
The text was updated successfully, but these errors were encountered: