Synchronization Is More Than Sending an On Command
Phones differ in processing speed, browser behavior, and network conditions. Sending a command at the instant a light should appear would expose some of those delivery differences to the audience.
Luma Crowd uses a scheduled start time. The server distributes a light command ahead of its cue, and participating devices follow that schedule. This is intended to make ordinary network variation less visible; it does not promise identical timing on every device under every condition.
The Live Command Path
The operator prepares an event in Studio and opens its live session. Pressing Play starts a selected item or the event flow. The live session gives commands the context they need, so commands from an old session do not belong to the current show.
The schedule contains the light behavior as well as its start time. A phone can then follow the prepared sequence instead of waiting for a separate message for every visible transition.
Device Capability Matters Too
- Compatible phones can use rear-flashlight control.
- Other phones use screen light, including when camera permission is declined.
- Screen color, torch response, and browser behavior can look different across devices.
- Loss of connection, leaving participation, and session end must clear active lights and pending commands.
See security and permissions for a plain-language explanation to share with guests.
Prepare for the Venue Network
An operator laptop on a reliable connection does not prove that the audience has adequate coverage. Rehearse where guests will stand or sit, using the intended Wi-Fi or cellular path.
Discuss audience density, available coverage, and the expected connected population with the venue's network team. The platform administrator sets account capacity and timing configuration. Confirm those settings before planning the live audience invitation.
Avoid assuming that a published venue capacity equals tested simultaneous phone capacity. Any production-scale performance claim should be supported by a relevant test or documented deployment.
Rehearsal Questions
| Question | What to observe |
|---|---|
| Can guests open the QR page? | Actual coverage and join behavior |
| Are phones ready before the cue? | Connected and ready participant states |
| Does the musical cue look aligned? | A representative mix of devices in the audience area |
| Does Stop cancel the remaining flow? | Audio, light effects, and queued items |
| Does End event return guests to waiting? | Session closure and participant state |
| What happens after a connection returns? | Current session state without an unexpected show restart |
Some rehearsal observations are manual; they should not be confused with metrics already available in the panel.
Start With an Understandable Cue
A sustained color, gradual pulse, or short entrance sequence is easier to evaluate than a dense effect with many transitions. Build complexity after the basic audience journey and control behavior have been verified.
Request a demo to explore the timeline and discuss a rehearsal plan for your venue.
