ReaClassical Terminal — Command Guide

The Terminal is a single text-entry dialog (run the “ReaClassical Terminal” script/action) that lets you type quick mixer adjustments and a handful of setup/utility commands instead of using the mouse or ImGui windows. It is built for screen-reader use: every command speaks a confirmation through Clara (or prints to the console if Clara isn’t installed).

The Terminal covers a deliberately small set of commands: fast, spoken-friendly power-mixer moves (mute/solo/pan/fader/peak/polarity), workflow conversion, importing audio, nudge/modifier amounts, and setup utilities (REAPER/Clara install, help, debug mode, GUI-window allow). Everything else in ReaClassical (project setup, recording, track/routing/FX editing, mixer snapshots, album/DDP metadata, rendering, stats/preferences) has its own dedicated reascript or accessible GUI — see the full ReaClassical manual.

How to use the Terminal

Run the script. A single-line input box appears: “Command:”.
Type a command and press Enter.
You can run several commands in one go by separating them with a semicolon: 1m;2m;3s mutes tracks 1 and 2 and solos track 3.
Commands are case-sensitive and must match the patterns below exactly (no extra spaces inside tokens, though spaces around commas/dashes in lists are tolerated, e.g. 1, 3 and 1 - 3 both work).
Every command below except reaper/reaper=..., clara, debug=on/debug=off, and help requires an existing ReaClassical project — create one first via Ctrl+N (Cmd+N on macOS).
Type help to open this guide (shipped with ReaClassical as an HTML page and also published at https://reaclassical.com/rcterminal.html) in your default browser. (Separately, the H keyboard shortcut opens the full ReaClassical manual as a single HTML page.)
Type ! on its own to repeat whatever command(s) you last ran. clara, reaper/reaper=..., and help are never saved as the repeat target, so ! always falls back to the last “real” command instead.
Only the commands documented below can be typed into the Terminal dialog directly (or repeated via !) — anything else is reported as “Unknown command”.

Target syntax used throughout

Every power-mixer command below takes a <target> — this is resolved consistently across all of them: - A plain number N = mixer track N (e.g. 3). - A list: 1,3 / 4-6 / 1,4-6 / * (all mixer tracks). - @N = aux track N; @ alone = the only aux track (if there’s exactly one); @1,2 / @* etc. for lists of auxes. - #N = submix track N; same rules as aux but with #. - rcm = the RCMASTER track. - refN = reference track N; ref alone = the only reference track (if there’s exactly one); ref1,2 for a list of references. Note: dash ranges (ref1-3) aren’t supported — use a comma list instead. - rt = the RoomTone track. - live = the LIVE track. - lb = the Listenback track.

Query naming convention

Any <target>?-style query (mute/solo/polarity/pan/fader/peak state) speaks just the value when it resolves to a single track — you already know which one you asked about. If the target expands to several tracks (a list, range, or *), each line is prefixed with that track’s name so you can tell the results apart, e.g. 1m? → "mute: on", but 1,3m? → "Mixer track Violin mute: on" / "Mixer track Cello mute: off".

1. Power Mixer

Mute / solo

Command	Effect
`<target>m`	Mute the target(s), e.g. `2m`.
`<target>um`	Unmute, e.g. `2um`.
`<target>s`	Solo (in addition to anything already soloed), e.g. `3s`.
`<target>us`	Unsolo, e.g. `3us`.
`<target>xs`	Exclusive solo: clears mute/solo on every mixer track first, then solos only the given target(s), e.g. `5xs`.
`<target>m?`	Speak mute state, e.g. `2m?`.
`<target>s?`	Speak solo state, e.g. `3s?`.

Pan

Command	Effect
`<target>p+N` / `<target>p-N`	Nudge pan by N percentage points toward right/left, e.g. `3p-10`.
`<target>p=N`	Set pan to an absolute percent, -100 (full left) to +100 (full right), e.g. `2p=15`.
`<target>p?`	Speak current pan (e.g. “25L”, “C”, “10R”), e.g. `2p?`.

Fader (volume)

Command	Effect
`<target>f+N` / `<target>f-N`	Nudge volume by N dB, e.g. `3f-1`.
`<target>f=N`	Set volume to an absolute N dB, e.g. `4f=-6`.
`<target>f?`	Speak current volume in dB, e.g. `2f?`.

Peak

Command	Effect
`<target>pk?`	Speak the peak hold level (dB, or “silence”) for one or more tracks, e.g. `4pk?`. Read-only — there’s no setter, only the query.

Polarity / phase

Command	Effect
`<target>i=y`	Invert polarity, e.g. `2i=y`.
`<target>i=n`	Normal polarity, e.g. `2i=n`.
`<target>i?`	Speak polarity state, e.g. `2i?`.

Other examples

1m, 1,3m, 4-6m, *m, @1m, #m, refm, rtm, livem, lbm, rcmm — every flavor of target syntax works the same way for mute (and equally for solo/pan/fader/polarity/peak): a single mixer track, a comma list, a range, all mixer tracks, an aux, a submix, the only reference/RoomTone/LIVE/Listenback track, and RCMASTER.
1,3m — Mute the first violin and cello sections to check what the rest of the ensemble sounds like alone.
4-6xs — Exclusive-solo the back-row tracks (4 through 6), clearing any other mute/solo state first, to spot-check that section in isolation.
1p+10 — Nudge the first violins 10% further right, a small adjustment relative to wherever they’re already panned.
1p=-30 — Pan the first violins to an absolute 30% left, regardless of where they were panned before, to widen the stereo image.
rcmp=0 — Recenter RCMASTER’s pan after an experiment.
2f+2 — Nudge the second violins up 2 dB, a small relative adjustment.
2f=-2.5 — Pull the second violins down to an absolute -2.5 dB relative to the rest of the mix.
rcmf? — Check RCMASTER’s current fader level before deciding whether to trim it.
1i=y — Invert polarity on track 1 because it’s out of phase with a spot mic.
1i=n — Revert it back to normal polarity once the phase issue is fixed elsewhere.
1pk? — Check track 1’s peak hold level after a take, without opening Meterbridge.

2. Workflow Conversion

Command	Effect
`convert=h`	Convert the current (vertical) project to Horizontal workflow.
`convert=v`	Convert the current (horizontal) project to Vertical workflow.

Other examples

convert=v — You started in Horizontal (quick setup) but the session turned into a multi-take recording project, so you switch to Vertical without losing existing work.

3. Importing Audio

Every import/import=smart,* command below starts its distribution at whichever folder track (D: or Sn:) is currently selected in the arrange view, working through the folders below it (creating new ones as needed). Select the Destination folder first to land takes there; select nothing (or a non-folder track) and it starts at S1:.

Command	Effect
`import`	Smart Import: scan the project media folder for new audio files and import them, one folder per take.
`import=smart,1`	Same as plain `import` (one folder per take).
`import=smart,2`	Round-robin distribute new takes across the current number of source folders.
`import=smart,3,N`	Round-robin distribute across N folders (creating folders as needed), e.g. `import=smart,3,4`.
`import=N`	Import only take number N, placed at the edit cursor, e.g. `import=20`.
`import=N,session`	Same, restricted to the named session, e.g. `import=20,Beethoven9`.
`import=N-M`	Import takes N through M, e.g. `import=3-5`.
`import=N-M,session`	Same, restricted to the named session, e.g. `import=3-5,Beethoven9`.

Other examples

import — You recorded several takes that landed in the project media folder; pull them all in, one folder per take.
import=smart,2 — Distribute newly recorded takes round-robin across your existing source folders (starting from whichever folder you have selected).
import=12,MahlerSym5_Mvt1 — Only take 12 from the “MahlerSym5_Mvt1” session is missing from the timeline; import just that one at the edit cursor.

4. Nudge & Modifier Amounts

Command	Effect
`nudge=ms`	Set the ReaClassical project-level nudge amount, in milliseconds, used by the “Nudge Marker Left”/“Right” and “Nudge Item Left”/“Right” reascripts, e.g. `nudge=20`. REAPER’s own item-nudge amount/unit isn’t exposed to ReaScript, so this is tracked independently per project. Defaults to 5 ms if never set.
`nudge?`	Speak the current nudge amount.
`mod=n`	Set the multiplier applied by the “+ modifier” scripts (Nudge Marker Left/Right + modifier, XFM Shift Crossfade Left/Right + modifier), e.g. `mod=10`. These scripts move by nudge amount × modifier, so with `nudge=5` and `mod=10` each press moves 50 ms. Defaults to 5 if never set.
`mod?`	Speak the current modifier value.

Other examples

nudge=10 — Switch to 10 ms steps for fine-tuning a marker position, then nudge it with the “Nudge Marker Left”/“Right” reascripts (these select a marker automatically after auditioning from/to it). The same amount also drives “Nudge Item Left”/“Right”, which shift the selected item (and its synced peers across tracks in the same folder) and ripple every later item in that folder along with it.

5. Setup Utilities

Command	Effect
`help`	Open this guide (the HTML copy installed with ReaClassical) in your default browser.
`clara`	Download and install the Clara screen-reader accessibility plugin (Windows/macOS only), removing any old OSARA plugin found in UserPlugins along the way, then restart REAPER.
`reaper`	Download and install the REAPER version ReaClassical currently recommends/tests against. Closes all open projects (you’ll be prompted to save unsaved work) and restarts REAPER once the install finishes. Same as `reaper=rec`.
`reaper=latest`	Install the latest public (main-release) REAPER version rather than the recommended one.
`reaper=VERSION`	Install a specific (main-release) REAPER version, e.g. `reaper=752` or `reaper=7.52` (both mean 7.52; the dot is optional). Searches the full version archive with no cutoff, so older versions work too (provided they are recommended version or higher).
`reaper=rec`	Synonym for the bare `reaper` command (also accepts `reaper=recommended`).
`debug=on` / `debug=off`	Display console messages in addition to Clara announcements. Stored per project, so a new project always starts with debug off.
`debug?`	Speak whether debug announcements are currently on or off for this project.

Other examples

clara — Setting up a brand-new machine; install the screen-reader plugin before doing anything else.
reaper — Match REAPER to the version ReaClassical is actually tested against (the safe default).
reaper=latest — Keep REAPER itself current with the latest public release.
help — Open this guide in your browser to look something up.

Suggested learning order for a new user

Power mixer: 1f=-3, 2p=-20, 1m, 2pk? — the everyday moves.
Workflow: convert=v / convert=h if you need to switch mid-session.
Importing (if recorded outside the session, or doing a second pass): import or import=smart,2.
Fine-tuning steps: nudge=10, mod=5 before using the Nudge/Modifier reascripts.
Setup: clara, reaper, debug=on/off as needed.