Skip to content

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

Merged
merged 63 commits into from
May 24, 2023
Merged

Update for ffmpeg 6.0 #173

merged 63 commits into from
May 24, 2023

Conversation

tilpner
Copy link
Collaborator

@tilpner tilpner commented Apr 25, 2023

Note that this breaks compatibility with older ffmpeg versions in multiple ways.
Assumes meh/rust-ffmpeg-sys#104 is used as ffmpeg-sys.

tilpner added 3 commits April 24, 2023 22:33
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.
@tilpner tilpner force-pushed the v6 branch 4 times, most recently from aef2182 to be52f1c Compare April 26, 2023 15:15
@kornelski
Copy link
Collaborator

How aligned this is with the ffmpeg-next fork?

tilpner added 21 commits May 23, 2023 12:53
tilpner added 25 commits May 23, 2023 12:55
@tilpner
Copy link
Collaborator Author

tilpner commented May 24, 2023

@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.

@tilpner tilpner merged commit 4486c6d into meh:master May 24, 2023
@tilpner tilpner deleted the v6 branch May 24, 2023 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants