Pulse
Ask most show-control software about its own state, and it has to go check first. It polls a device, waits for a response, then answers you. Pulse is why Showcaller doesn't work that way. It keeps a live picture of the state your connected devices report. It keeps updating in the background while you're live.
No prior integration or training needed.
01
A mirror, not a lookup
Pulse keeps a live picture of the state each connected device reports: what's live, what's loaded, what just changed. When you ask Showcaller a question, it doesn't start a fresh round trip to a device and wait. You get an answer from state it already has, because it keeps watching.
02
Always watching, not just reacting
This is also why Showcaller feels less like software you operate. It feels more like a crew member who's actually paying attention. You don't need to narrate what's happening for it to keep up. It keeps up, the same way a good second engineer would.
A delay of even a second or two adds up across every question asked over a few hours. That friction makes a tool feel like it's working against you instead of with you. Pulse is built to remove that friction.
03
What Pulse makes possible elsewhere
Awareness isn't just a convenience. Two other features use it. Tally checks each command against the state the device reports. Its confirmed values go back into Pulse, so the picture stays current. And Quick Rig's onboarding can see a device connect as soon as it's added. It doesn't wait for a manual test.
Awareness first
Everything else Showcaller does depends on knowing what your devices report. That includes checking a command, recording a show and answering a question mid-set. Keeping that knowledge current is Pulse's entire job. It runs quietly in the background of every show.
See what Pulse makes possible in Tally → See how shows get connected in the first place →