AAutomation
Your folders, taught once.
Most music software can rename a file. OD Studio can be taught what a file is, where it belongs and what it should be called — and then do it, file by file, in your words. Every decision can be explained. Nothing happens without the authority you gave it.
01Main Automation
Teach a folder once. Watch it decide, file by file.
An automation lives on a folder. When something arrives, OD Studio reads it against your rule — what it is, where it came from, its code, tempo or key — then describes it, names it and files it, or waits for your yes. A fact it cannot read is never guessed: the rule says “can’t tell” and leaves the file alone.
Bounces from Logic are filed by year. Everything else is left where it landed.
Sort session exports
Files where it arrives from Logic and it ends .wav or .aif and OD Studio does not already have a copy of it in “Bounces”: move it to Exports / [Year] — waiting for your yes before anything touches the file.
OD Studio prepares each change and waits for your yes.1 waits for your yes
All of these must be true
Steps run in this order: descriptions first, then anything that touches the file, so it never moves wearing the wrong description.
- Exports
02Script Automation
When a rule isn’t enough, a script decides.
Scripts weigh several facts, take a name apart, choose between shelves — and ask you when they can’t tell. They are written in ODS Script, OD Studio’s own small language, and they can only ask for things OD Studio already knows how to do. Read one, then try it on a pretend file.
What it needs
The file it is run on.
What it may do
Move files
What it can never do
Reach the network, run shell commands, or read unrelated folders.
if file.tempo == null {
needsYou("Nothing knows this file’s tempo, so it cannot be shelved by speed.")
} else if file.tempo >= 140 {
moveTo(path("Samples", "Fast 140+"))
} else if file.tempo >= 100 {
moveTo(path("Samples", "Mid 100-139"))
} else {
moveTo(path("Samples", "Slow under 100"))
}
Quoted exactly as it ships in OD Studio’s examples. Scripts are written in ODS Script, OD Studio’s own small language: it can only ask for things OD Studio already knows how to do, and every request goes through the same careful mover as everything else — recorded, and undoable.
Try — plan it on a pretend file, change nothing
03Naming Intelligence
Untitled 7.wav deserves a better name.
A name is built from parts, and every part has a source: the project, role, key and tempo OD Studio knows; your clock; the next free version on disk — and, for the creative part, your own Name Vault. Pick a recipe and watch six careless names become useful ones.
A name from your own Name Vault — dealt once each, never your filenames or your library’s words.
- WAVUntitled 7.wavQuiet Harbour.wavproject Late Bloom · role Bass · A minor · 90 BPM
- WAVAudio_01_bip.wavArctic Flame.wavproject Harbour Lights · role Keys · D minor · 96 BPM
- WAVHM_Mix_V17.wavAncient Meridian.wavproject Harbour Lights · role Mix · 96 BPM
- WAVHeavy 128 BPM.wavPale Orbit.wav128 BPM (in its name)
- WAVbounce final FINAL.wavGlass Harbour.wavproject Night Bus · role Mix · 84 BPM
- MIDchords idea 14.midSilent Road.midE♭ major · 84 BPM
- ■ Your Name Vault
- ■ What OD Studio knows about the file
- ■ Your clock
- ■ The next free version on disk
- ■ Its original name
- ■ Fixed text in the recipe
Interactive demonstration with fictional files. In OD Studio the same recipes run from a key, the command palette, a right-click — or inside an Automation, where a filename plan can include a creative name.