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
[BUG] CCExtractor incompatible with ffmpeg 5.0 #1418
Comments
This should probably be a short GSoC project. |
Just ran into that issue. Came here. The |
Hi, is there any plan to address this? Most distributions are busy to organize the switch to ffmpeg 5 and if ccextractor doesn't keep up, the package will end up removed. :-( Thank you for your work on maintaining ccextractor! |
I think it's happening or will happen as part of the hardsubx rewrite effort by @PunitLodha and @shashwat1002. I've seen references to FFmpeg 5 there. |
Yes, this will be a part of the HardsubX rewrite. While we are working on it, a short term solution would be to compile CCExtractor without HardsubX support. |
Thanks @PunitLodha for the tip! Any idea / rough guess of when the HardsubX rewrite will be ready? |
It should be ready before October |
Hi @PunitLodha,
No rush or anything. Just a friendly ping asking about the ETA. :) |
@utkarsh2102 |
Hello @PunitLodha,
Concerning Arch Linux, the AUR package is build from release versions. |
Hi @PunitLodha,
Concerning Debian, the Debian package is built (and which is what we generally want to stick to) from a new release. |
Any progress on ffmpeg5 compatibility? Debian's bookworm freezes are starting soon, and if ccextractor isn't in testing by early February it won't be part of bookworm. |
Any update on the hardsub/ffmpeg5 front? |
Looking at this issue now. Will update soon. |
Created a PR with a fix for this: #1479 |
CCExtractor version: 0.94 / master
Necessary information
Additional information
When building the AUR package for CCExtractor, building fails when the installed ffmpeg version on the system is 5.0.
FFmpeg released 5.0 January 17th, 2022 and seems to have quite some breaking changes.
The text was updated successfully, but these errors were encountered: