OTYPEroadmap21 october 2026scripting for the octatrackoctatrack

OType scripts are small functions written in plain text, copied to the card and run on the Octatrack: they change the pattern, the sample pool, the part, and audio files on the card, in one gesture.

Version 1.1 runs on a real Octatrack MKI, inside the OT1 firmware, tested by hand at every step. The computer side is complete: checker, simulator, VS Code extension and this reference. The engine is published as firmware sources with no interface of its own: each firmware builds its menu around it.

Where OType stands

  1. languagesyntax, checker, VS Code extension, command reference
  2. simulatorrun a script on a copy of your bank and card, see the pattern before and after
  3. on the unittrigs, locks, p-locks, LFOs, effects, scenes, conditions, micro timing, retrigs, sample slots, tempo, patterns
  4. audio, experimentalsave a take, Flex slots, sliced chains from a folder, normalise through the .ot gain
  5. live scriptsin clock, in note, in cc, in trig: a script runs with the sequencer; var keeps state, launch sets its first wake
  6. MIDInotes, CC, program changes and NRPN out; note, velocity and CC in
  7. recorderrt.add and rec.src / len / trig / loop / arm: rec.arm starts a take from the inputs, MAIN, CUE or a track
  8. linked scriptsgate, in gate, out and cv wire one script to another; pat.copy copies a pattern
  9. now1.2: the project autoload, script trigs, the audio package

Next

  • autoload: scripts that start by themselves when a project loads (auto, in load:, the project's own SCRIPTS folder)
  • script trigs: trigs sent by another firmware, in trig t script:
  • the audio package: the audio operators as an optional package, OType audio
  • confirm the audio operators on the unit, then drop their experimental mark