Rockchip and FFmpeg: A Deep Dive into Open-Source license Violations and teh DMCA Takedown
The world of open-source software relies on a delicate balance of collaboration and respect for licensing agreements. Recently, this balance was disrupted as GitHub was forced to disable Rockchip’s Media Process Platform (MPP) repository following a Digital Millennium Copyright Act (DMCA) takedown notice. This action, filed on December 18, 2025, stems from accusations that the Chinese chipmaker illegally incorporated code from the widely-used FFmpeg project into its own software.This incident highlights the critical importance of adhering to open-source licenses and the potential consequences of non-compliance. This article will provide a complete overview of the situation, exploring the technical details, legal implications, and broader impact on the open-source community.
Did You Know? The LGPL (Lesser General Public license) allows for the use of code in proprietary software, but requires attribution and allows users to modify and redistribute the code under the same license.
The Core of the Dispute: FFmpeg and Rockchip’s MPP
FFmpeg is a free and open-source project consisting of a vast collection of libraries and programs for handling video, audio, and other multimedia files. It’s a cornerstone of many popular applications, including video editors, streaming platforms, and media players. The accusation leveled against Rockchip centers on the alleged unauthorized copying of thousands of lines of code from FFmpeg’s libavcodec library – specifically, decoders for crucial video formats like H.265 (HEVC), AV1, and VP9.
The core issue isn’t simply using FFmpeg code, which is permissible under certain licenses. The problem, as outlined in the DMCA notice, is that Rockchip allegedly:
* Removed original Copyright Notices: Stripped away the attribution to the original FFmpeg developers.
* Falsely Claimed Authorship: Presented the copied code as their own original work.
* Changed the License: Redistributed the code under the Apache 2.0 license, a permissive license, instead of the original LGPL (Lesser General Public License) used by FFmpeg.
this shift in licensing is notably significant. The LGPL requires that any modifications or redistributions of the code remain under the LGPL, ensuring continued openness and user rights. The Apache 2.0 license, while also permissive, offers different terms and doesn’t mandate the same level of openness.
Pro Tip: Always carefully review the licensing terms of any open-source code you intend to use in your projects. Understanding the obligations and restrictions is crucial for avoiding legal issues.
A Timeline of Events: From Accusation to Takedown
The controversy didn’t erupt overnight. Here’s a breakdown of the key events:
* February 2024: FFmpeg publicly accused Rockchip of “blatantly copy and pasting” FFmpeg code into its drivers via a post on X (formerly Twitter). Link to the original tweet.
* Following Months (Feb 2024 – Dec 2025): Despite the public accusation, Rockchip offered no ample response or indication of intent to rectify the situation. This lack of engagement fueled the frustration within the FFmpeg community.
* December 18, 2025: A formal DMCA takedown notice was filed with GitHub, requesting the removal of the infringing code or the restoration of proper attribution and an LGPL-compatible license.
* December 27, 2025: GitHub complied with the DMCA notice and disabled the Rockchip MPP repository.
This timeline demonstrates a pattern of alleged infringement followed by a prolonged period of inaction,ultimately leading to legal intervention.