Prepare surtitles in Pockitle Cue with our dedicated editor, then export QLab-ready Text cues for venue projection in one click.
After deployment, Cloud Sync (beta) can mirror QLab subtitle jumps to audience phones.
Use the projection pack before deployment. Use Cloud Sync (beta) after deployment when phones should follow QLab.
Project subtitles locally from QLab
Export Text cues from the editor. No audience link, QR code, or phone subtitles.
Flow:
Pockitle Cue -> QLab -> Projector
Read export guide ->
Project locally and sync audience phones
Download from Deployment Cockpit. QLab keeps the venue timeline; Pockitle Cue Cloud updates phones.
Flow:
QLab -> Local projection -> Projector
QLab -> Pockitle Cue Cloud -> Audience phones
From subtitle preparation, to QLab triggering, to audience phone sync.
Projection pathPockitle Cue Editor→QLab Projection Pack→QLab Workspace→Projector
Cloud Sync (beta) pathQLab sync cue→Local Mac bridge→Pockitle Cue Cloud→Audience phones
When Cloud Sync (beta) is enabled, each Pockitle Cue subtitle imports as a QLab timeline Group. Each Group contains the Text cue for local projection and the sync cue that updates audience phones. Projection-only exports import QLab Text cues without connecting to Pockitle Cue Cloud Sync (beta).
This workflow is not meant to replace QLab. It lets Pockitle Cue generate subtitle cues that can be placed inside QLab.
Your sound, lighting, video, standby, and other show cues stay in QLab. With Cloud Sync (beta), keep each Pockitle Cue subtitle Group together: one Text cue projects locally, one sync cue notifies Pockitle Cue Cloud, and both refer to the same subtitle cue state.
QLab workflows need to be reliable, rehearsable, and reversible. Pockitle Cue keeps QLab local, avoids exposing credentials, and keeps the operator able to monitor the show from the Pockitle Cue console.
If the venue internet drops, audience phone sync may pause, but QLab can keep projecting subtitles locally. In-venue subtitle output is not immediately lost because of audience Wi-Fi, mobile network, or cloud connectivity issues.
The QLab Projection Pack does not include passwords, billing keys, runtime tokens, or backend credentials. Cloud Sync (beta) uses the already-open Pockitle Cue console on the operator’s Mac instead of writing sensitive data into the QLab show file.
Audience members keep using the same QR code or audience link. You can switch between QLab triggering and manual Pockitle Cue console control without republishing audience access.
QLab talks to the Pockitle Cue console already open on the operator’s Mac. Venue network routing usually does not need to change, and audience Wi-Fi does not need direct access to QLab.
QLab local cue triggering and audience phone delivery are separate parts of the workflow. Use real phones during technical rehearsal to confirm loading speed, subtitle sync, and venue network behavior under realistic audience conditions.
Learn when QLab-only local projection is enough, when audience phone subtitles are useful, and how both workflows differ during rehearsal, deployment, and live operation.
Step-by-step instructions for exporting subtitles from the Pockitle Cue Editor and running the AppleScript importer in QLab.
Learn how to deploy a show, open Pockitle Cue Bridge Helper, and send QLab cue changes to audience phones through Pockitle Cue Cloud.
QLab trademark note
QLab is a product and trademark of Figure 53, LLC. Pockitle Cue is not affiliated with, endorsed by, or partnered with Figure 53.
For the first test, use the QLab Projection Pack from the Pockitle Cue Editor and confirm that subtitles import, arrange, and project correctly in QLab. After deployment, bridge setup, and rehearsal with real audience phones, enable Cloud Sync (beta).
Discuss a QLab workflow