Loading…
Documentation
Modulaser has a built-in web remote. Turn it on, open a browser on your phone or tablet, and you get a live operator panel for the running show: trigger clips, step cues, run the timeline, tap tempo, and arm lasers, all from your hand.
This is entirely over the local network, no cloud is involved.
Open Preferences, enable the web remote, and pick the port. Modulaser starts serving on your machine's network address, which it shows you so you can type it into a browser on another device.
Keep both devices on the same network. If the show machine is wired, put your phone or tablet on the matching Wi-Fi.
Every device pairs once. This keeps a random phone on the venue Wi-Fi from arming a laser.
Paired devices are listed in Preferences with a name and a last-seen time. Revoke one, or revoke all, whenever you want.
These are the features you can control with the remote:
Because everything routes through the same control core as MIDI and OSC, a change from any surface shows up everywhere. The remote is another way in, not a separate control path.
The remote can arm lasers. Arming acts at the DAC level, exactly like the desktop, so arming one laser arms every laser sharing that DAC. Never arm output unless you have checked projector position, output zones, and safety settings, and you are operating within local regulations.
Before you arm, the laser view shows each laser's DAC connection health, so you can see whether light will actually emit. A DAC connecting or dropping updates the view on its own.
Every output-affecting action from the remote passes through the same non-bypassable safety pipeline as the desktop: motion limits, blind zones, and arming interlocks all apply. A dropped connection or a malformed request never holds light on and never blocks output. Deliberate kill-switch duty still belongs to the venue's hardware E-stop, not to Wi-Fi.
Under the remote is a REST and WebSocket API for controlling a running instance from your own scripts or tooling. A running Modulaser serves interactive API docs at /docs on the same address, where you can explore every endpoint and drive the live instance to try them out.