SialkOperatourDownloadBeta

OperatourDocumentation

Learn it tonight.

Four short pages take you from nothing to a visual on a second screen, moving with the room. Everything else is here for the night you want it.

Today Operatour plays GLSL shaders, p5 sketches, Three.js scenes and video clips as layers you mix live; when a new kind lands, it says so plainly rather than loading it and hoping.

Start here

From nothing to a visual on screen, moving with the music. About ten minutes, and nothing to write.

  1. 01What Operatour isAnd what it is not, which is the faster half of the answer.
  2. 02Install and first runDownload, open it, and know what you are looking at.
  3. 03Your first visual on screenAdd a layer, mix it, put it on a second screen.
  4. 04Play music into itOperatour listens to an input device. Here is how to give it one.

How it works

Three ideas. Everything else in these pages is a detail of one of them.

  1. 01Layers, parameters, modulationThe whole model, in about a page.
  2. 02What Operatour playsGLSL, p5 and Three.js today, by name, and what happens to everything else.

Playing it

The surface, control by control.

  1. 01LayersAdding, mixing, ordering, removing.
  2. 02ParametersThe four every layer gets, and the ones your sketch declares.
  3. 03ModulationBase, reach, and the things that push a value around.
  4. 04The audioWhat Operatour hears and what it works out from it.
  5. 05Connect a DAWThe Sialk: Connect plugin, stems, the master, and your project’s exact tempo. Arrives with v1.
  6. 06The output and fullscreenThe window is the output, not a preview of it.
  7. 07Perform and BuildThe same controls, arranged two ways.
  8. 08Saving a showWhat a .slko file holds, and what it does not.

Writing a sketch

For the people who make the visuals. Sialk runs your code rather than a recording of it, so this is where the instrument gets interesting.

  1. 01A GLSL sketchOne folder, one sketch.glsl, no page and no loop.
  2. 02A p5 sketchOne sketch.js in global mode. p5 itself is supplied.
  3. 03Reading the audiowindow.sialk, the versioned surface your sketch is written against.
  4. 04A Three.js sceneOne scene.js that exports a function. three itself is supplied.
  5. 05Declaring parametersHand the performer a fader, a switch, a colour or a trigger.
  6. 06Your own control panellil-gui and dat.GUI, kept off the wall and put on the surface.
  7. 07Writing a sketch with AIPaste the contract into the assistant you already use, and drag the result on.

Reference

Tables to come back to.

  1. 01Keyboard referenceEvery key, and where they work.
  2. 02What is in the betaHonestly, and with the release each missing piece arrives in.
  3. 03When something goes wrongThe log, the messages along the bottom, and how to report it.