Open Source Components and Corresponding Source

CineX's media processing is built on open-source software. This page lists the components we embed, the licences that apply to them, and how to obtain their source code.

Embedded open-source components

CineX embeds the eight components below as dynamic frameworks (x264 and dav1d are statically linked into libavcodec). Versions are taken from the binaries themselves: FFmpeg is n6.0 — 6.0.2 is the CocoaPods release number of the wrapper, not an FFmpeg version.

Component Version Licence
ffmpegkit6.0GPL-3.0
libavcodecFFmpeg n6.0GPL-3.0
libavformatFFmpeg n6.0GPL-3.0
libavfilterFFmpeg n6.0GPL-3.0
libavutilFFmpeg n6.0GPL-3.0
libavdeviceFFmpeg n6.0GPL-3.0
libswresampleFFmpeg n6.0GPL-3.0
libswscaleFFmpeg n6.0GPL-3.0
x264ffmpeg-kit 6.0.LTS 内置GPL-2.0-or-later
dav1dffmpeg-kit 6.0.LTS 内置BSD-2-Clause

What each component does

ffmpegkit (GPL-3.0) — The FFmpeg wrapper layer, providing a command-style interface.

libavcodec (GPL-3.0) — The codec library (x264 and dav1d are statically linked into it).

libavformat (GPL-3.0) — Reading, writing and parsing of container formats.

libavfilter (GPL-3.0) — Filter-graph processing.

libavutil (GPL-3.0) — Shared utility functions.

libavdevice (GPL-3.0) — Device input and output.

libswresample (GPL-3.0) — Audio resampling and channel-layout conversion.

libswscale (GPL-3.0) — Video colour-space and pixel-format conversion.

x264 (GPL-2.0-or-later) — The H.264 software encoder — the key difference between the full-gpl and LGPL builds. Every source file says “either version 2 … or (at your option) any later version”, so it may be combined and conveyed under GPL-3.0.

dav1d (BSD-2-Clause) — The AV1 decoder. A permissive licence, so it does not change the licence of the whole; because it is statically linked, its source is part of the Corresponding Source.

Obtaining the corresponding source (GPLv3 section 6)

The eight frameworks above are licensed under GPL-3.0 (x264 under GPL-2.0 or later, dav1d under BSD-2-Clause; the three may be combined and conveyed). Under section 6 of GPL-3.0, when distributing in binary form you must enable recipients to obtain the corresponding source. You can obtain it here:

Corresponding source package (recommended, one file)

https://getcinex.app/cinex-corresponding-source.tar.gz

The full source of ffmpeg-kit 6.0.LTS, FFmpeg n6.0, x264 and dav1d, plus the build recipes for both platforms and a manifest (tar.gz, 18.6 MiB).

ffmpeg-kit (the wrapper and build actually used by this app)

https://github.com/arthenica/ffmpeg-kit

The project is archived (the author has stopped maintaining it), but the repository remains publicly accessible with the full source and build scripts. Note that upstream's own source offer covers only the binaries upstream published; the slices embedded in CineX are built by us, so the obligation is ours — the download above is authoritative.

FFmpeg itself

https://ffmpeg.org/download.html

The upstream official source site; download the n6.0 source by version number.

x264

https://www.videolan.org/developers/x264.html

The official VideoLAN source site.

dav1d

https://code.videolan.org/videolan/dav1d

The official VideoLAN repository.

If you need a build configuration or source package that exactly corresponds to the version embedded in CineX, write to support@getcinex.app and we will provide it within a reasonable period.

Full licence texts

The complete licence texts are distributed with the app: every embedded framework bundle carries its own LICENSE file (libavcodec also carries LICENSE.X264 and LICENSE.DAV1D). The in-app Account → Open Source Components and Corresponding Source page lists them verbatim — it reads them at runtime from the frameworks actually installed on the device, so the page cannot drift from what ships.

Related

The restrictions on reverse engineering in the Terms of Service do not apply to the components licensed under the open-source licences above; for those components the applicable open-source licence terms prevail. See the "License" section of the Terms of Service.

How we handle your data is set out in the Privacy Policy.