-
Notifications
You must be signed in to change notification settings - Fork 101
Update for ffmpeg 6.0 #173
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
Conversation
For some codecs (x264) it's necessary to set the codec while the context is being created, otherwise the codec-specific defaults aren't applied.
aef2182
to
be52f1c
Compare
How aligned this is with the ffmpeg-next fork? |
…can directly cause memory unsafety
…rs, use coefficients_mut instead
…eeds_drop warning
… does nothing and is confusing
…ntext from stream metadata
…=Context> over AsRef
…rs from a codec context
through Encoder and Decoder
…ers from codec parameters
…ose if they don't
@kornelski Sorry for the frustrating delay. It is not aligned at all, as I didn't think to check ffmpeg-next (a combination of remembering that fork to be not-that-active either, and v6 being recent-ish). It probably would have saved me a lot of time. They do some backwards compatibility better than this PR does, and it appears they're sticking to the bitmask-only channel layout API (?). There's... some backwards compatibility in this PR, but it's not really tested. This is not a decision to never again support older ffmpeg versions, but I don't want to block v6 support on getting proper cross-version testing set up. |
Note that this breaks compatibility with older ffmpeg versions in multiple ways.
Assumes meh/rust-ffmpeg-sys#104 is used as
ffmpeg-sys
.