Version Compatibility
This manual describes ORIX Script 1.0. It is the first version of the language. There is no earlier version, so there is nothing that 1.0 is, or needs to be, compatible with yet. This chapter states what is versioned, where the version is recorded, and what is and is not promised for the future.
Finding the version
> version
ORIX Script 1.0The version is a property of the language built into the application, not of a script. A script does not declare the version it was written for, and there is no statement to do so.
Where versions are recorded
| Place | What is recorded | Checked when read? |
|---|---|---|
| A compiled program | The language version of the compiler that produced it | Not applicable: programs are compiled each time, never stored |
A project (.orixdjproject) |
formatVersion (1) for the project format, and languageVersion ("1.0") for the scripts it contains |
The format version is checked. The language version is stored for future use and is not checked by version 1.0 |
An exported script (.orixdj) |
The first comment line // ORIX DJ Script v1, which identifies the layout of the export header |
The header is recognised by this line; a file without it is imported whole as script text |
| A request to Claude Studio | ORIX Script version: 1.0 in the context |
Not applicable |
Projects
A project stores its scripts as text (also written as individual .orixdj files inside the project package), together with the language version of the application that saved it.
- A project whose format is newer than the application understands is refused with a clear message:
This project was saved by a newer version of ORIX DJ (format N).It is reported as newer, not as damaged. - The language version stored in the project is informational in 1.0. Scripts restored from a project are compiled like any other script when they are run; if a script does not compile, you get the ordinary compiler messages.
Exported scripts
An exported .orixdj file is plain UTF-8 text:
// ORIX DJ Script v1
// name: My Bass Swap
// tags: transition, bass
// origin: user
// favorite: false
// created: 2026-11-21T10:00:00Z
// updated: 2026-11-21T10:05:00Z
// ---
automation "My Bass Swap" quantize bar {
…
}The header consists of comments, so the whole file is also a valid script. On import, the name, tags, origin and favourite flag are read from the header; an import never overwrites an existing script (a taken name becomes "Name 2", "Name 3"…). A text file without the header is imported as it is, named after the file.
The v1 in the first line is the version of this header layout. It is not the language version.
Script history
Saved scripts keep a history of their previous sources in the library. That history is about your edits; it is unrelated to the language version.
What 1.0 consists of
For the purpose of compatibility, "the language" means:
- the grammar described in Language Syntax;
- the types, units and operator rules of Types and Units;
- the timing semantics of Timing, Beats and Bars and Automation Scheduling;
- the parameters, actions, events and builtin functions of the Complete API Reference, with their types and ranges;
- the diagnostic codes of Error Handling;
- the limits of Performance Guidelines.
The reference chapters (Deck Commands, Mixer Commands, Effects Commands, Complete API Reference) are generated from the same table the compiler uses, and a test verifies that they match it. For a given build they are exact by construction.
Compatibility policy, as implemented
Stated honestly, this is what exists today:
- There is one language version, 1.0, and one compiler. The compiler does not have modes for other versions.
- Scripts are stored as source text and compiled when run. A script therefore always means what the compiler of the running application says it means.
- Projects record the language version they were saved with. Version 1.0 does not act on that field. It is there so that a later version can recognise projects written for 1.0.
- Project format versions are enforced in one direction. An older application refuses a project of a newer format instead of misreading it.
- No automatic migration of scripts exists, because there is no earlier version to migrate from.
What is not promised by the code today: that a future version will accept every 1.0 script unchanged, or that it will convert them automatically. When a second version exists, Migration Guides will describe each difference and how to adapt a script.
Writing scripts that age well
Nothing here is required, but these habits reduce your exposure to any future change:
- Use documented paths only, spelled as in the reference. The compiler already enforces this.
- Write units explicitly.
deck.A.volume = -6dBis unambiguous; a bare number given to a gain control relies on the linear-level convenience. - Do not depend on details marked as subtle in this manual, such as the order of two tasks due at the same beat. Write the script so that the order does not matter.
- Restore what you change at the end of an automation, and state your assumptions with guards at the top. A script that checks its preconditions fails clearly instead of behaving differently.
- Keep a copy as text. Exported
.orixdjfiles are plain text that you can read, compare and archive. - Keep the simulator result in mind. A script that passes the simulator with the same trace before and after an update behaves the same.
Checking a script against your build
Every build can check any script without running it live:
- open it in the script editor, which shows the compiler's diagnostics with their line and column;
- start it with
run "Name"in the console: it is compiled first, and errors are listed instead of running; - from the repository,
swift run orix-dj-bench check file.orixdjcompiles and simulates a file.