Performance setups: controllers, projectors and browser notes

[kawaiipantsu]

Describe a setup that helps you perform: browser/OS, audio interface, screen/projector arrangement and any MIDI controller. Real hardware observations are useful because automated browser tests cannot certify physical latency or MIDI timing.

Controls → Connect MIDI requests permission explicitly. MIDI learn maps a CC to a named control; use macro("cutoff",1200) in an ordinary Strudel parameter. System-exclusive messages are blocked.

Hydra needs WebGL. OSC needs a separate bridge; the site does not run a Node/OSC backend. WebSerial availability depends on browser restrictions.

A useful post includes a small score and what you measured, rather than a claim that a browser or device always works.