ffmpeg-the-third
ffmpeg-the-third copied to clipboard
shssoichiro
A fork of the abandoned ffmpeg-next crate which is a fork of the abandoned ffmpeg crate
Currently diffing the `bindings.rs` between 6.1 and 7.0, and I found the following things that are not showstoppers, but should be implemented after 7.0 compatibility: - [x] `av_channel_layout_retype` (#61) -...
Due to the ability of enums in C to be treated as basically just an integer with some predefined constants, it's probably not a good idea to treat all of...
current video is from `path`, which implemented called `format::input`, for example, ```rust pub fn clip(&self) -> Result { ffmpeg_next::init()?; let _ = self.mkdir(); let mut ictx = format::input(&self.path)?; let input...
libavresample is only supported up until FFmpeg 4.4.X and has been removed starting with FFmpeg 5.0. This is handled in the sys/build.rs by checking `ffmpeg_major_version()` in a few places. `ffmpeg_major_version`...
[context](https://blog.rust-lang.org/2024/05/06/check-cfg.html), this will be required with current nightly or stabilization of 1.80.0 (> 700 compile-time warnings)
Often, there are enums in the `ffmpeg` crate that have `From for Enum` implementations (and vice versa). These will automatically show missing variants due to non-exhaustive match statements whenever a...
I was looking to write a script that lists all of the video codecs, and I see both `format::register_all()` and `format::list()` https://docs.rs/ffmpeg-the-third/latest/ffmpeg_the_third/format/fn.register_all.html I noticed in the source that it has...
1. Does anyone actually use it? If no, can we drop it? 2. Are there any tests? 3. Create/expand tests 4. What are the compatibility guarantees around (de)serialization? Context is...
It's not obvious what needs to be changed in this project whenever FFmpeg releases a new version. Things I know of (some of these won't be caught by CI): -...
Metadata
Owner
Metadata
A fork of the abandoned ffmpeg-next crate which is a fork of the abandoned ffmpeg crate