TL;DR
FFmpeg posted on Twitter that, after nearly two years of unresolved concerns, one of its developers took action over alleged copying of FFmpeg source into a Rockchip driver. The project says thousands of lines were copied and that the code’s license was changed in a way it calls a violation of the LGPL.
What happened
FFmpeg used its official Twitter account to call out @IloveRockchip for what it describes as wholesale copying of FFmpeg source into a Rockchip multimedia driver. The tweets state the project waited almost two years for the problem to be fixed before “one of the FFmpeg developers acted.” FFmpeg alleges that thousands of lines of its code were copied into the repository and that the copied files had their license altered in a manner FFmpeg says breaches the LGPL. The post includes a link to a specific file in the rockchip-linux/mpp GitHub repository (mpp/codec/dec/av1/av1d_cbs.c). The tweet thread shows posting metadata and engagement metrics; the visible timestamps reference Feb. 23, 2024 within the thread and a Dec. 26, 2025 posting time on the tweet shown.
Why it matters
- Allegations of copying and relicensing raise open-source license compliance questions that can affect redistribution and downstream projects.
- If true, copying large amounts of code and changing license terms could require remediation such as re-licensing, attribution, or code removal.
- Public enforcement actions by prominent projects can set precedents for how LGPL and similar licenses are interpreted and enforced.
- The situation puts attention on hardware vendor driver repositories and how they incorporate third-party open-source code.
Key facts
- FFmpeg publicly posted complaints on Twitter about code copied into a Rockchip driver repository.
- The tweets assert the project waited nearly two years for @IloveRockchip to address the issue before action was taken by an FFmpeg developer.
- FFmpeg says 'thousands of lines of code' were copied into the Rockchip mpp repository.
- The tweets accuse the Rockchip-linked repository of changing the original FFmpeg license in a way that violates the LGPL.
- A specific file was linked in the thread: github.com/rockchip-linux/mpp/blob/fdeb8c378b79d4b4ef80457e4431815de89dc417/mpp/codec/dec/av1/av1d_cbs.c.
- The visible tweet metadata includes a Feb. 23, 2024 reference in the thread and a displayed timestamp of Dec. 26, 2025.
- The tweet shows public engagement, including view counts and replies in the embedded metadata.
What to watch next
- Whether the linked GitHub file will be removed, amended, or relicensed — not confirmed in the source
- Any formal notices (for example a DMCA or other takedown request) filed against the repository — not confirmed in the source
- Public responses from @IloveRockchip or maintainers of the rockchip-linux/mpp repository addressing the allegations — not confirmed in the source
Quick glossary
- FFmpeg: An open-source project that develops libraries and tools for handling multimedia data (audio, video, and related formats).
- LGPL: The GNU Lesser General Public License, a free-software license that allows linking from proprietary software under certain conditions and imposes obligations on distribution of modified versions.
- GitHub: A web-based platform for hosting and collaborating on software projects using the Git version control system.
- DMCA: The U.S. Digital Millennium Copyright Act, which includes a process for copyright holders to request removal of allegedly infringing content from online service providers.
Reader FAQ
Did FFmpeg file a DMCA takedown on GitHub?
not confirmed in the source
What exactly does FFmpeg allege was done?
FFmpeg alleges thousands of lines of its code were copied into a Rockchip driver and that the copied code’s license was changed in a way FFmpeg says violates the LGPL.
Which repository and file are referenced?
The tweet links to a file in the rockchip-linux/mpp repository: mpp/codec/dec/av1/av1d_cbs.c.
Has @IloveRockchip publicly responded?
not confirmed in the source
FFmpeg @FFmpeg After nearly two years of waiting for @IloveRockchip to fix their FFmpeg copyright violation, one of the FFmpeg developers acted. Thousands of lines of code were copied from…
Sources
- FFmpeg has issued a DMCA takedown on GitHub
- DMCA Takedown Policy
- I'm an open source maintainer, so I empathize with the …
- Guide to Submitting a DMCA Takedown Notice
Related posts
- ZJIT is now available in Ruby 4.0 — new JIT compiler built into YARV
- How to Embed Files in C/C++ Binaries: Tools, Preprocessor, and ASM
- C/C++ Embedded Files: Methods to Include Resource Data Inside Binaries