Tap Tempo for Lighting Cues

Planning reference only

Tap tempo for lighting cues can give a provisional pulse during preparation or rehearsal. TapTempo.one does not connect to consoles, DMX, timecode, MIDI, network control, fixtures, playback, or automation. It must never be used as a live safety or show-control signal.

Authorized operators and established systems remain responsible for cues.

Choose a cue-relevant level

Tap the main musical pulse if cues follow beats. If cues occur every two beats, the half-time candidate may describe their spacing. Subdivision chases may relate to double time. Label the cue level rather than assuming the largest rate.

Reset between sections and programming ideas.

Worked rehearsal example

Gaps of 1,200, 1,190, and 1,210 ms convert to 50, about 50.42, and about 49.59 BPM. Median is 50. Half candidate is 25 and double is 100.

One cue every 1.2 seconds corresponds to 50 events per minute. A beat grid at 100 may place cues every two beats. This is arithmetic orientation, not a synchronization command.

Phase and downbeat

BPM alone does not specify when a cue fires. Phase, downbeat, phrase structure, programmed delay, fixture response, and operator timing matter. TapTempo.one supplies none of these.

Verify cue position through the show’s approved rehearsal and control workflow.

Tempo changes

Measure stable sections separately. A recent median cannot represent accelerando, tempo maps, timecode changes, or free passages. If a show track version changes, repeat verification against that exact authorized version.

Safety boundary

Lighting can involve electrical, rigging, visual, photosensitivity, venue, and audience safety considerations. This site offers no safety, medical, programming, compliance, or operational advice. Follow qualified personnel, venue rules, equipment documentation, and approved procedures.

Never operate a browser when attention must remain on a live show.

Documentation

For planning notes, state section, source version, tapped pulse, approximate rate, candidate used, and independent verification. Do not imply that the page drove a console.

Privacy and availability

No show file, cue list, venue, console, fixture, audio, URL, account, or control data is received. Current-page timestamps disappear on Reset or closure. The hosted page has no offline, uptime, latency, or show-readiness guarantee.

Table-read rehearsal scenario

During a planning session, a designer hears a repeated accent in a non-live rehearsal recording. They choose the quarter pulse, make six taps, and write “scene transition rehearsal reference, about 96.” The number is discussed as possible visual pacing, not sent anywhere. The designer then clears the sequence before the team considers a slower every-two-beat idea.

The second idea receives its own observation. Keeping concepts separate prevents a planning note from implying that one rolling sequence described several cue families. No browser tab remains open during live operation.

Cue-spacing arithmetic without control

At 96 BPM, one beat lasts 0.625 seconds. An every-two-beat concept is 1.25 seconds, corresponding to a 48-per-minute event rate. Those values can support a paper discussion, but fixture behavior, programmed fades, network conditions, and operator choices can change the visible outcome. The page emits no timed events and offers no way to transfer the sequence.

A written brief should say “provisional spacing idea” and name who must verify it. Do not label the estimate “console-ready,” “locked,” or “synced.”

Version and authority check

Confirm that the rehearsal source matches the version approved for programming. A new mix, edit, playback speed, or arrangement can invalidate an old note even if its title is unchanged. The authorized operator decides whether a planning observation is useful and how it is implemented in the actual system.

If another team member provides a different number, compare tapped event levels and source versions first. A factor-of-two disagreement may reflect cue grouping rather than a faulty calculation.

Pre-show boundary checklist

Before any show workflow begins, remove the browser estimate from the control path. Verify cues, phase, delays, fades, fixture response, accessibility considerations, and contingencies using approved procedures. Keep the timing page out of automation, network commands, and operator dependencies. It has no emergency mode, redundancy, audit trail, or recovery behavior.

For documentation, retain only the necessary planning note in the venue’s approved location. Do not email confidential cue lists or venue details to product support. If the browser result conflicts with qualified personnel or equipment documentation, the browser result is not authoritative.

The final planning record should identify its author and review state so a provisional observation cannot be mistaken for an approved operating instruction.

Frequently asked questions

Tap a rehearsal passage only for planning orientation, document the pulse, then verify and program through the authorized show-control workflow.