Stage sync tests
In our measurements on real devices, after the leader changed the song the members' screens followed in about 0.1–0.2 seconds over Wi-Fi and in at most 0.21 seconds over Bluetooth. In a test with one leader and four members, 46 song switches went through with no loss and no errors.
This page backs up the “song switch in under a second” line on the home page. These are our own measurements, not an independent lab test — which is why we also write down how they were taken, which devices were used and what has not been measured yet.
Core measurements
| Measurement | Result |
|---|---|
| Song switch — Wi-Fi | About 0.11–0.18 s |
| Song switch — Bluetooth | At most 0.21 s (with two members) |
| Joining the stage — Wi-Fi | About 0.22 s |
| Joining the stage — Bluetooth | 2.7–4.2 s |
| 5 devices (1 leader + 4 members, Bluetooth, 24-song set) | About 0.18 s end to end. The spread between sends to the four members averaged 2.5 ms, at most 6 ms. 46 switches, 0 lost, 0 errors. More members did not add latency |
| Fast back-and-forth navigation | 38 switches over Bluetooth, 0 lost |
| Long session | 26 minutes over Bluetooth without interruption |
| Song missing from the member's library | Arrived from the leader with its full content (44 times in this test); members did not need the song beforehand |
| Wrong stage code | Rejected — 5 ms over Bluetooth, 0.53 s over Wi-Fi |
Bad conditions
What matters on stage is that the band doesn't drop out when something goes wrong. In every case below, no member had to reconnect by hand.
| Situation | What happened |
|---|---|
| Leader sent the app to the background — Bluetooth | 35.5 s in the background, no member dropped |
| Leader sent the app to the background — Wi-Fi | The member was cut off for 42 s and reconnected on its own when the leader came back |
| iPad leader, screen locked — Wi-Fi | Three rounds: gaps of about 14, 74 and 9 s; it reconnected on its own every time |
| iPad leader, screen locked — Bluetooth | No dropout |
| Leader's Bluetooth switched off and on mid-set | Broadcast repaired itself in 0.29 s (Android leader); an iOS leader also recovered without any action. Members reconnected in 1.3–1.4 s |
| Member walked out of range and back | Came back on its own |
| Bluetooth page-turner pedal while the leader broadcasts over Bluetooth | Consecutive switches with no loss, the broadcast kept running |
Known limits
What we saw in testing and what you should know before you go on stage:
- Some devices' Bluetooth buffers packets and delivers them in bursts. On one Android tablet in our tests, roughly one packet in four arrived 4 seconds late, while a phone connected to the same leader at the same time saw no delay at all. Moving that tablet to Wi-Fi made the delay disappear. The fix: a shared Wi-Fi network or a hotspot from the leader's phone.
- With battery saver on, Android puts the Wi-Fi and Bluetooth radios to sleep; songs can arrive a few seconds late, at worst 10 seconds. The app warns about this before the stage is set up.
- Over Wi-Fi, if the leader's screen locks, members drop for a while and reconnect on their own once the leader is back. If the leader won't be looking at the phone, Bluetooth is the sturdier choice.
- Guest networks and corporate networks with “client isolation” stop devices from seeing each other. In such a venue, start a hotspot on the leader's phone.
- Over Bluetooth the practical limit is 7–8 devices within about 10 metres. For bigger bands or longer distances, use Wi-Fi.
Not measured yet
- Wi-Fi under heavy radio load (many access points on the same channel, heavy video traffic). On a shared network with about 15 connected devices we saw no problems, but that run was not timestamped, so we give no number.
- Bands with more than eight devices.
- Continuous pedal use for more than ten minutes.
- Battery drain over a long gig.
How it was measured
- Devices: iPad (iPadOS), Xiaomi 14T Pro and Redmi Pad SE (Android) — iOS and Android mixed. The 5-device test was led by the Xiaomi 14T Pro.
- The developer build of the app logs every stage event with a millisecond timestamp. Latency is the gap between the moment the leader sends and the moment the member applies the song; the clock offset between devices was derived from a shared pair of events (the member's join request and the leader's acceptance).
- Tests were run in August 2026. A real page-turner pedal was tried separately in October 2026.
- The log never records the stage code, the code proof or any lyrics. In the released app this log is switched off entirely.
Measured in: 2026-08