Demos

Working programs, each in tests/demos/ in the repository. They take their paths on the command line so you can point them at your own layouts, and each writes to build/<demo>.tosc unless you pass -o.

Demo	What it shows
One of every control	Building all thirteen control types, and looking at them
Custom property	Storing configuration TouchOSC will keep and expose to Lua
Copy scripts	Pushing one Lua script onto many controls
Faders from JSON	Building a layout from external data, with OSC addresses
Control surface	The same idea in full: paged, labelled, MIDI and OSC
Image converter	Generating thousands of controls programmatically
Numpad	Nested layouts, Lua scripts and LOCAL message wiring
Rebuilding a template	Authoring a layout TouchOSC ships, from scratch
Reaper to TouchOSC	Driving the whole thing from a DAW

The scripts live in tests/demos/ and the layouts they read are in tests/data/, so the test suite runs each one on every commit -- if a demo stops working, CI fails.

Note

These were rewritten for py2tosc. If you are following a tutorial written for tosclib, see Migrating from 0.3.