The software behind OverCue.

This website.

Read the full website copyright and license notices. This text retains notices from the installed JavaScript dependencies, fonts and Next.js bundled components, including supporting server and build tools. A listed framework component is not necessarily sent to your browser.

The hosting runtime also uses Sharp under Apache-2.0 and a platform-specific libvips build with LGPL and other dependency terms. Those image-processing binaries run on the server; they are not downloaded to your player.

Earlier Mac app: version 0.4.6.

This list comes from the earlier app's build scripts and third-party notices. It is not an audit of every available or historical download. Each release must include the complete notices and source materials required by the software it contains.

This software uses code of FFmpeg under the LGPL v2.1 or later. The project provides the FFmpeg 7.0 source archive and build script. The app’s build also places those materials beside the executables in its MediaTools resources. Before each release, we must verify that those materials match the files being distributed.

Read the cdj3k-root copyright and MIT license. Upstream permission for that code does not grant rights in manufacturer firmware, keys or other separate material.

New desktop app source: 2.0.0-beta.1.

The newer desktop app source is marked GPL-3.0-only and is built differently from the 0.4.6 Mac app. This list describes that source code; it does not mean these libraries are in the 0.4.6 download.

The source also integrates with stemd, a separate stem-separation service whose own code is offered under MIT or Apache-2.0. The desktop imports resampler data from that project. Hardware measurements and model weights need their own review of where they came from and how they may be used. The project's code license does not automatically cover those materials.

Build tools, platform-specific libraries, transitive packages and operating-system frameworks have additional terms. A lockfile may include packages that are not in a particular binary. The release inventory must identify what is actually distributed, including any native libraries, helpers, data and models.

Player software and installation tools.

The CDJ3000 source declares GPL-3.0-only for OverCue-owned code and retains the MIT notice for its modified cdj3k-root updater portions. These are separate from the CDJ3000X version in development described below. They do not confirm what is included in the 0.4.6 app or which players it supports.

ChronoBent · our independent audio library.

The current combined CDJ3000X Prepared Stems source uses ChronoBent 0.1.0, our independently developed C++17 pitch and tempo library. ChronoBent is MIT-licensed, with copyright © 2026 Nicolas Wehmeyer. It is integrated directly into the Stems worker and requires no external DSP library.

Read the complete ChronoBent copyright and MIT license. Retain that notice with copies or substantial portions of the library. The surrounding application, native runtime and other components retain their own licenses and distribution requirements.

ChronoBent 0.1.0 is experimental. Publishing its source and using it in development does not prove comparable audio quality, confirm that it has passed testing on real players, or mean it is included in older downloads. Older builds still need the notices and must meet the obligations of the components they contain.

Your rights under component licenses.

The applicable license text governs each component. A website acknowledgment is additional information; it does not replace license texts and notices supplied with the software, corresponding source where required, or other redistribution conditions. People entitled to the source must be able to access it. Keeping it in a private repository they cannot open does not meet that requirement.

OverCue’s legal and safety notice does not take away rights granted by those licenses, including applicable rights to inspect, modify, redistribute or obtain source. Our own terms cannot relicense somebody else’s code or extend a code license to separately owned data, models, firmware or keys.

If a notice is missing or you cannot access source you are entitled to, use the contact page and identify the component, release and relevant license. Do not include secrets, manufacturer keys, firmware dumps or private media. General inspiration and protocol-research references are listed separately in community credits.