SPB Git

Repository Public

README.md 5.6 KB

# Examples

This chapter collects complete automations that you can copy, run in the simulator and adapt. Each example is on its own page with the full script, a description of what happens bar by bar, when it is useful, and what to check before running it live. All of them are different from the bundled presets, which are described in Presets.

Every script on these pages is compiled and run in the simulator by the test suite of ORIX DJ, so what you copy is known to be valid for this version of the language.

# The examples

Example What it does
Long EQ Blend A 12-bar transition that hands over highs, mids and bass one band at a time.
Reverb Tail Stop Ends a track with a tape stop into a long reverb tail on its own channel.
Tempo Shift Moves the tempo of the master deck to a new value over sixteen bars, with key lock.
Hot Cue Juggle Stores a hot cue on the bar and retriggers it faster and faster for three bars.
End Of Track Guard Watches deck A and starts a sixteen-bar blend to deck B when 32 bars are left.
Performance Pads A long-running automation that turns three pads into an echo throw, a loop roll and a reset.
Filter Wobble A rhythmic low-pass wobble drawn as a list of eight steps and played for four bars.
Acapella Layer Brings an acapella on deck C over the playing track for eight bars and takes it out again.
Crossfader Chop Cuts between two playing decks with the crossfader, following a sixteen-step pattern, for two bars.
Build And Drop Swap An eight-bar build on deck A with a noise riser and a loop roll, then a cut to deck B on the drop.
Back To Back Alternates between decks A and B indefinitely: when one track ends, the other starts and the finished deck loads the next track of the queue.
Sidechain Pump Ducks a deck on every beat and lets it swell back, for eight bars.
End Of Set Fade Fades the master output into reverb over sixteen bars, stops every deck and restores the master level.
Glitch Fills Adds a bar of beat-repeat fills at the end of every four-bar phrase, with slice lengths chosen by random().

# By technique

If you want to see Look at
Guards that refuse to start in the wrong situation Long EQ Blend, Tempo Shift, Acapella Layer
Several controls ramped together Long EQ Blend, Acapella Layer, End Of Set Fade
Ramp curves Reverb Tail Stop, Tempo Shift, Build And Drop Swap
at blocks overlapping a ramp Build And Drop Swap
every on a grid Hot Cue Juggle, Sidechain Pump
Arrays as patterns Filter Wobble, Crossfader Chop, Glitch Fills
Procedures with deck parameters Long EQ Blend, Back To Back
Event handlers End Of Track Guard, Performance Pads, Back To Back
MIDI pads through triggers Performance Pads
A third or fourth deck Acapella Layer, End Of Set Fade
Channel effects and master effects Reverb Tail Stop, Glitch Fills
Remembering and restoring settings Crossfader Chop, Sidechain Pump, End Of Set Fade

# How to use an example

  1. Copy the script into a new automation and save it. In the Docs tab of the application, an example can also be opened in the editor or run in the simulator directly.
  2. Run it in the simulator. Compare the trace with the bar-by-bar table of its page.
  3. Read the "Check before running it live" list and make the rig match it.
  4. Adapt it: deck letters, lengths and levels are at the top of each script or easy to find.
  5. Try it in headphones before using it in front of an audience.

A minimal starting point, if you prefer to begin from nothing:

orixdj
automation "My Automation" quantize bar {
    // 1. Check that the rig is in the state you need.
    if not deck.A.playing {
        print("Deck A is not playing.")
        stop
    }

    // 2. Set things up.
    let before = deck.A.filter.highpass

    // 3. Perform.
    over 4 bars { deck.A.filter.highpass -> 2kHz }

    // 4. Put back what you changed.
    deck.A.filter.highpass = before
}

# Conventions used in the examples

  • Settings that you are likely to change are constants at the top (let wet = 0.65).
  • An automation that needs a particular state checks it first and stops with a printed reason.
  • Effects are switched on with enable() and off with disable().
  • Whatever is changed on a deck that keeps playing is restored at the end.
  • Positions in the tables are counted from the automation's own start: with quantize bar, bar 1 is the first bar line after you start it.
Files main
Menu

Theme