Competitive Analysis
This document places ORIX DJ 1.0 against the categories of DJ software that already exist. It is a feature-level comparison, written from the source code of ORIX DJ and from general knowledge of how DJ applications are built.
Two limits apply to everything below:
- No competing product was installed, measured or tested for this document. The columns that describe other software describe what is typical of a category, in general terms. They are not statements about the current feature list of any named product, and no product is named.
- The ORIX DJ column describes the code in this repository on 2026-11-21. Where a capability exists in code but has not been exercised on real hardware or judged by ear, that is stated. The measured figures are in performance; what is and is not tested is in testing.
Categories of existing software
| Category | What it is, in general terms |
|---|---|
| Professional performance applications | Desktop applications built around two to four decks, a mixer, an effects section and a library, usually sold with or alongside dedicated controllers, audio interfaces or timecode systems. They carry many years of controller mappings, hardware certification and beat-grid tooling. |
| Hardware-ecosystem preparation software | Library managers whose main job is to analyse tracks and export them, with cues and grids, to standalone players. Performance features exist but the centre of gravity is the hardware. |
| Open-source DJ applications | Community-maintained desktop mixers, typically with broad controller support through user-contributed mapping files and a scripting hook for controller mappings. |
| Consumer and mobile applications | Simplified two-deck applications, often built around a streaming catalogue and automatic mixing, aimed at casual use. |
| Automatic-mix and radio automation tools | Programs that sequence and crossfade a playlist unattended. The transition logic is normally a fixed set of options rather than something the user can read or edit. |
| Live-coding and music-programming environments | Languages and environments for generating or sequencing sound from code. They are programmable in depth but are not DJ tools: there are no decks, no library of analysed tracks and no mixer model. |
ORIX DJ 1.0 is a desktop application of the first kind in its layout (decks, mixer, effects, library, recording), far smaller in hardware and ecosystem support, with one element borrowed from the last category: a purpose-built programming language for the mix itself.
Feature comparison
"Typical" means commonly present in professional performance applications as a category. It does not mean every product has it.
| Area | Typical of professional DJ applications | ORIX DJ 1.0 |
|---|---|---|
| Decks | Two to four, sometimes more; sample decks or remix slots | Four decks (deckCount = 4 in RenderCore.swift). No sample decks or remix slots. |
| Audio I/O | Multi-channel interfaces, certified devices, often input channels for external sources | One Core Audio output device through a single AUHAL unit; master and cue output pairs selectable; no audio input of any kind. Multi-channel cue routing was verified only by offline rendering, because no multi-channel interface was attached during development. See audio engine. |
| Time stretching and key lock | Mature, usually licensed or long-refined algorithms, often with several quality modes | One in-house WSOLA time stretcher. Pitch accuracy and residual on a sine are measured; behaviour on transients and dense polyphonic music has not been evaluated by listening. See deck engine. |
| Beat grids | Constant and variable-tempo grids, manual grid editing, downbeat tools | Constant-tempo grid only (one BPM, one phase anchor, a downbeat index) with manual adjustment tools on the deck. No variable-tempo grids: tracks with tempo drift or live drumming will not stay on the grid. See analysis. |
| Key detection | Present, with harmonic-mixing notation | Chroma plus Krumhansl-Kessler profiles, Camelot codes. Agreement with published keys on real music is partial and is reported in analysis. |
| Sync | Tempo and phase sync, a master clock | Tempo sync with phase bend and a master clock; quantised actions. Measured on synthetic material in the tests. |
| Mixer | EQ, filter, crossfader curves, cue bus, often selectable EQ models | Three or four-band EQ, a combined filter knob, separate high-pass and low-pass, crossfader curves, cue bus with split cue, master limiter. One EQ model. See mixer. |
| Effects | Built-in effects, sometimes plug-in hosting | 18 built-in effect types, eight slots per channel rack and a master rack. No Audio Unit or VST hosting. See DSP. |
| Stems separation | Increasingly common | None. |
| Streaming services | Common, through catalogue partnerships | None, by design: the library is local files only, and DRM-protected files are rejected at import. |
| Video mixing | Present in some products | None. |
| DVS / timecode vinyl | Common in the professional tier | None. There is no audio input path. |
| Controllers | Large sets of ready-made mappings for specific hardware, jog wheels with high-resolution messages, displays, LED feedback | No bundled controller presets. The user builds a mapping profile with MIDI learn. MIDI input and output go through CoreMIDI; this was tested only with CoreMIDI virtual endpoints, never with a physical controller. HID controllers are not supported. |
| Library | Crates, playlists, smart lists, history, import from other applications' libraries | SQLite library with crates, playlists, smart crates, history and sessions. No import of other applications' libraries or cue data. See persistence. |
| Recording | Master recording, sometimes broadcasting | Master recording to a 32-bit float CAF take, then export to WAV, AIFF, AAC, ALAC or FLAC with trim, fades and gain. No broadcasting or network streaming output. See recording. |
| Automatic mixing | A fixed automix mode with a few options | Auto DJ that orders the queue deterministically from tempo and key and writes each transition as an ORIX Script the user can read before it runs. |
| Automation and scripting | Usually limited to controller mapping scripts or macro recording; general-purpose scripting of the mix is uncommon | A dedicated language, ORIX Script, with a compiler, a beat-time runtime, a sample-timestamped scheduler, a simulator and a step debugger. See automation. |
| AI assistance | Varies; where present it is usually a hosted feature of the vendor | Optional, with the user's own Anthropic API key. The model only proposes scripts; every proposal is compiled and simulated locally and is never run automatically. Tested against a local stub transport only, never the live API. See AI integration. |
| Platforms | macOS and Windows, often mobile companions | macOS 15 or later, Apple silicon only. |
| Track length handling | Streaming from disk, long mixes supported | Tracks are decoded fully into memory; files longer than 150 minutes are refused (TrackBuffer.maxSeconds). |
What ORIX DJ 1.0 lacks
Stated without qualification, because each is a real gap for someone coming from an established product:
- No streaming-service integration (deliberate).
- No stems separation.
- No video.
- No Audio Unit or VST hosting.
- No DVS or timecode control, and no audio input at all.
- No ready-made controller mappings; no HID support; nothing verified on physical MIDI hardware.
- No variable-tempo beat grids.
- No import of libraries, cues or grids from other DJ software.
- No sampler or remix decks.
- No Windows, Intel Mac, iOS or iPadOS version.
- No track record: the application has not been used in a live set, nobody has run a listening evaluation of the time stretcher, EQ or effects, and no long live session has been logged.
What is distinctive
The distinctive part of ORIX DJ is narrow and specific. It is the automation layer, not the audio path.
A language for the mix
ORIX Script is a small statically checked language whose values carry musical units (4bars, 1/4beat, -12dB,
200Hz, 50%). A script addresses the same parameter space as the on-screen controls and MIDI mappings, schedules
actions in beat time, ramps parameters, and reacts to engine events. The user documentation is in
docs/orix-script.
What makes this different from a mapping script or a macro recorder:
- The compiler checks types, units, ranges and capabilities before anything runs, and rejects unbounded programs (loop bounds, recursion, budgets). The limits are listed in automation.
- The runtime never executes on the audio thread. It runs ahead of the clock and emits control events stamped with the engine sample at which they apply; the render core splits its block at that sample. The benchmark report shows 687 timed commands with none late in an offline run (see performance).
- The language has no access to files, the network, processes or the host application beyond the mixer's own parameter schema. The threat model is in the security report.
Simulator and debugger
The same runtime drives a simulated rig (decks, mixer, effects, beat clock) without touching audio. A script can be run in the simulator to produce a trace and parameter curves, or stepped with breakpoints, before it is allowed near the live engine. Because the simulator and the live host share the runtime, a script's sequence of actions is the same in both; what the simulator cannot show is how the result sounds.
Auto DJ expressed as scripts
Auto DJ does not have a private transition engine. AutoDJPlanner orders the queue from the analysed tempo and
Camelot key with a deterministic rule, and generates each transition as ordinary ORIX Script (bass swap, smooth
blend, echo out, filter sweep, or a cut on the bar). The Auto DJ screen shows the exact script of the next transition.
Given the same queue, analysis results and settings, the plan is the same; there is no model and no network call in
this path.
Bring-your-own-key AI that only proposes
Claude Studio sends a request to the Anthropic Messages API with the user's own key, stored in the Keychain. The answer is treated as untrusted text: the proposed script is extracted, compiled, budget-checked and simulated locally, and shown with its results. Running it is a separate, confirmed user action. There is no vendor account, no telemetry and no other network use in the application.
One schema, several consumers
The effect catalogue and the script schema are single tables in code. The effect units, the rack interface, the compiler, autocomplete, the reference documentation and the language description sent to the model are generated from them, and a test compiles and simulates every example in the user documentation (150 examples in the test run of 2026-11-21). This is an engineering property rather than a user feature, but it is the reason the documentation and the behaviour can be expected to agree.
Reading this comparison correctly
- The distinctive features are about programmability and verifiability. They do not compensate for missing stems, streaming, DVS or controller support if a DJ needs those.
- Sound quality is not compared here at all. ORIX DJ's DSP is in-house and measured on synthetic signals; nobody has compared it by ear with any other product, and this document makes no claim about how it sounds.
- Stability under live conditions is unknown. The automated tests render offline; see the "not covered" list in testing.
Related documents
- Technology evaluation: the build-or-buy decisions behind the gaps and choices above.
- Architecture overview
- Brand guidelines