Says to say goodbye to ffmpegkit. To January 6, 2025, ffmpegkit is … | by Tener Sener | Jan, 2025

As January 6, 2025,, Ffmpegkit Officer retirement.

This decision is not easy, especially considering years of time and effort I invested in the project. But after evaluating all the challenges, I know it is no longer possible for me to keep on the project.

I want to share the story behind this decision, as well as the outline of what is happening in the next few months, and explain what users need to know. If you are here for specific guidance, don’t worry to skip the relevant sections below.

“Time is one of the two main challenges to maintain FFMPegkit.”

Since late 2022, I struggle to dedicate enough time to project due to other commitments. As I made the best to review the issues reported by Github every few months, the FFmpegkit has updated with a new time on the FFmpeg than I am reasonable to rise.

FFmpegkit update to support new versions of FFMPeg always the most difficult part of the project’s maintenance. It involves;

1. Adaptation of Api Changes
2. Solve architectural problems
3. And tried everything for all platformades supported

nobody is easily or easy. Unfortunately, I don’t have time to do it myself, and we do not receive enough contributions from the community to fill the gap.

Yes, we have PRSs, and I am very grateful to debug developers in debug issues and give detailed analysis of problems they have experienced. Their work helped to develop the ffmpegkit in many ways, and others have made new features. But the FFmpeg Wrapper Layer (The core of the ffmpegkit API) does not receive considerable support. I understand, it’s a complex piece of project. Maybe I wouldn’t be surprised, but the result is that FFmpegkit fell behind the FFMPeg in terms of supported versions.

In 2023, we are released Ffmpegkit 6.0the final version. To do this happen, I outstood the work of contractors since I didn’t have time to do it myself. I pay an important amount to cover their efforts, and as they give the update, release is not as smooth as I expected. It does not test well and required patches after release. However, I was relieved that in the end A promise I made to users in the first year.

At 2024, I can’t get to change again, so I try to update myself to the ffmpegkit. I began to migrate the branch of the progress of FFmpeg 6.1 in November. The process is slow and frustrating, with the challenges of architecture and workarounds required for new structures indicated by FFMPeg. As I progressed, and the branch is now strong, it still needs a correct test that I haven’t long.

What else is the complex things that are more than FFMPeg 6.1 isn’t even the newest version. The FFmpeg moved into versions 7.0 and 7.1, and the gap is getting better. The effort required to keep FFMPegkit so far is more than I can do now or in the future.

“Other important factors are the legal complexity of the FFMPeg work.”

The ffmpeg is a strong tool, but there is a significant challenges, especially when it comes to licenses and patents. The distribution of ffmpeg haries, as the ffmpegkit, brings a unique set of hazards.

When I moved the ffmpegkit under my company, Arthenica LtdI contacted MPEG LA to clarify the project position. In time, MPEG LA confirmed the FFmpegkit, as a software component in the above software, is not subject to patent fees. That certainty gives me confidence to continue investing in the project and even plan for commercial services around it.

However, in 2023, MPEG LA got Awayand everything has changed. When I arrived at Via-La in late 2024 to confirm FFmpegkit’s position under their terms, I did not receive an answer.

To obtain clarity, I consulted with a law of IP law. Their review produces concerns about potential risks related to licensing and patents. They recommend retirement to the project and remove older binaries as the safest choice. They suggest some alternative paths, but those choices have a significant time, effort, and money, wherever I can.

At that point, the decision of the retirement of the ffmpegkit is unavoidable.

FFmpegkit now retires Kamahir. While the source code and release archives remain available, all native binaries (for Android, IOS, Macos, and TSI) Will be deducted from repositories according to the following schedule:

• Versions older than 6.0: Take February 1, 2025
• Version 6.0: Take April 1, 2025

As for the Summit and Reaction native Versions, I plan to lower it if possible. However I explore what platforms can do and have not yet created concrete plans.

The challenges of the legal and patenthesis are set above apply to me and my company only. If you use FFMPegkit or FFmpeg in your applications, I strongly recommend consulting a IP professional to assess your specific situation.

Since FFmpegkit binaries are no longer available to repositories after the specified dates, your CI / CD tubes may fail if they trust in these binaries. To avoid disruption, you need to build the ffmpegkit locally and use the manufactured binaries in your applications. the structure Section of the project Wiki provides detailed instructions for this process. If you have trouble finding information, use GitHub search part.