Introduction
ORIX Script is the automation language of ORIX DJ. A script describes, in musical time, what should happen to the decks, the mixer and the effects: "start deck B on the next bar, sweep a high-pass on deck A over eight bars, then pause deck A". ORIX DJ checks the script completely before it runs, then performs it in time with the master clock.
This manual describes version 1.0 of the language. The console command version prints the version built into your copy of ORIX DJ.
> version
ORIX Script 1.0What a script looks like
automation "Eight Bar Blend" quantize bar {
deck.B.sync(true)
deck.B.volume = -12dB
deck.B.play()
over 8 bars {
deck.A.filter.highpass -> 12kHz
deck.A.volume -> -60dB
deck.B.volume -> 0dB
}
deck.A.pause()
deck.A.filter.highpass = 20Hz
deck.A.volume = 0dB
}Read it from top to bottom, the way you would read a set list:
- The automation waits for the next bar line (
quantize bar). - Deck B is synced, set 12 dB down and started.
- For eight bars, three controls move together: the high-pass of deck A rises, deck A fades out, deck B fades in.
- When the eight bars are over, deck A is paused and its controls are put back.
Values carry their unit (-12dB, 12kHz, 8 bars), so a script reads like the labels on a mixer.
What ORIX Script is for
- Transitions that must land on a bar line: blends, bass swaps, cuts, echo exits.
- Effect moves that need more than two hands: several parameters ramped together, restored at the right moment.
- Rhythmic tricks on a grid: stutters, loop rolls, gate patterns.
- Reactions to what happens in the set: a track ending, a deck starting, a pad being hit.
- Repeatable routines: the same move, performed identically every time.
What a script can do
A script can only use what is listed in the reference chapters:
- read and set deck parameters and call deck actions (Deck Commands);
- read and set the mixer and read the master clock (Mixer Commands);
- set up, switch and automate effects in the master rack and in each channel rack (Effects Commands);
- wait, schedule, ramp, loop, branch and react to events;
- print text to the automation log with
print(…).
What a script cannot do
These limits are part of the design; they are what makes it reasonable to run a script in front of an audience.
- No file, network, shell or system access. The language has no statement or function for any of them. The only link to your music library is
deck.X.load("title")anddeck.X.loadNext(), which ask ORIX DJ to load a track that is already in the library. - It never runs on the audio thread. The runtime works on its own scheduler thread and only sends time-stamped parameter changes and actions to the audio engine. A slow or failing script cannot interrupt the sound.
- It cannot run forever by accident. Every loop has a bound, functions cannot call themselves, and the runtime counts the work a script does. See Performance Guidelines.
- It cannot read MIDI, the keyboard or the screen. It can react to sixteen numbered triggers, which you map to pads or keys. See MIDI Integration.
- It cannot define new effects or process audio. It controls the effects that exist.
Checked before it runs
A script is compiled before any of it is executed. The compiler verifies every name, every type and unit, every constant value against the range of its parameter, the bound of every loop, and the use of every timing statement. If there is one error, nothing runs. Each message has a line, a column and a stable code such as E-RANGE; the codes are explained in Error Handling.
deck.A.volume = 6dB6 dB is outside the range of 'deck.A.volume' (-60 dB … 0 dB). [E-RANGE]Some things can only be known while the script runs, for example whether a track is loaded. Those are run-time errors: the automation is cancelled, the effects it had switched on are switched off, and the audio keeps playing.
Deterministic
The same script started in the same situation does the same thing. Time is counted in beats of the master clock, not in timer ticks, and even random() produces the same sequence on every run of an automation. That is why a script can be tried in the simulator first and trusted to behave the same way live.
One language, several ways in
Everything in ORIX DJ that automates the mix uses this same language, the same compiler and the same runtime:
| Where | What it does with ORIX Script |
|---|---|
| Automation Studio | The editor, the console, the simulator, the debugger, the presets gallery and the visual builder in one place. In the editor you write and save automations. Saved scripts can be exported as .orixdj text files and imported again. |
| Console | Each line you type is compiled as a small anonymous automation and run at once. See Console Usage. |
| Presets | The 24 bundled presets are ordinary scripts that you can open, read and change. See Presets. |
| Visual builder | It generates ORIX Script text, which goes through the same compiler and has the same limits as a script typed by hand. |
| Docs tab | This documentation, inside the application. Examples can be opened in the editor or run in the simulator from there. |
| Claude Studio | Claude writes or corrects a script as text. ORIX DJ compiles it and runs it in the simulator on your Mac before showing it to you; it is never executed directly. See Security Model. |
| Auto DJ | The transition between two Auto DJ tracks is a generated script, run like any other. |
| Simulator and debugger | Run a script against a simulated rig, without touching the audio. See Debugging. |
Because they share one runtime, what you learn in one place applies everywhere: a line that works in the console works in a script, and a preset is a good starting point for your own automation.
Files
- A script file is UTF-8 text with the extension
.orixdj. - A file contains one or more
automation "Name" { … }blocks, and optionally constants (let) and functions (fn) shared by them. - A file exported by ORIX DJ starts with a short comment header (
// ORIX DJ Script v1, then name, tags and dates, then// ---). The header is made of comments, so the file is still a valid script. - Projects (
.orixdjproject) store the scripts they use together with the language version.
How to read this manual
If you have never programmed, read Quick Start, First Automation, Timing and Beats and Bars in that order, then browse the Examples. If you program already, Language Syntax, Types and Automation Scheduling contain the precise rules.