Tutorials & guides

Operating system: Windows 10 or 11 (64-bit)
Processor: Intel i5 / AMD Ryzen 5 or better (quad-core recommended)
RAM: 8 GB minimum, 16 GB recommended for large shows
Disk: 500 MB free space for installation, SSD recommended
Display: 1920×1080 minimum
Network: Ethernet recommended for Art-Net, sACN and Remote
Audio: Any ASIO or WDM audio interface for LTC
USB: For Explo TX2-70K (RS232/USB adapter)

OnCue Timecode is a native Windows desktop application — no cloud, no browser, no internet connection required to run your show.

1. Download the installer from the Download page or your account portal.
2. Run the .exe installer as Administrator.
3. Follow the setup wizard — choose your install directory (default: C:\Program Files\OnCue Timecode).
4. Launch OnCue Timecode from the Start menu or desktop shortcut.
5. Go to Settings → Licence and enter your licence code (received by email after purchase).
6. Click 'Activate' — OnCue will verify your licence online (one-time).
7. You're ready to go! The app runs fully offline after activation.

Tip: Keep your licence code safe. You can deactivate and reactivate on a different machine from your account portal.

1. Create a new show: File → New Show. Give it a name and set the frame rate (25fps for PAL, 30fps for NTSC).
2. Add cues: Click '+' in the cue list or press Ctrl+N. Set the timecode, name, and action for each cue.
3. Choose your timecode source: Settings → Timecode. Select 'Internal' to use OnCue as master, or 'LTC Input' to follow external timecode.
4. Test: Press Play (Space) to run through your cues. The timeline shows your progress in real-time.
5. Arm the show: Click the Arm button when you're ready for the live run.
6. Go live: Press Go (Enter) or let timecode trigger your cues automatically.

Save regularly with Ctrl+S. OnCue also auto-saves every 60 seconds.

The OnCue interface has four main areas:

• Toolbar (top): Transport controls (Play, Stop, Go, Arm), timecode display, and quick settings.
• Cue List (centre): Your show's cue list with columns for timecode, name, action, zone, status, and notes.
• Timeline (bottom): Visual representation of your cues on a time axis. Drag to reposition, scroll to zoom.
• Sidebar (right): Properties panel for the selected cue, output monitors, and health dashboard.

Keyboard shortcuts:
- Space: Play/Pause
- Enter: Go (fire next cue)
- Escape: Stop
- F12: Emergency Stop
- Ctrl+N: New cue
- Ctrl+S: Save
- Tab: Next cue
- Shift+Tab: Previous cue

Your OnCue licence is tied to one machine at a time. You can deactivate and reactivate freely.

Activate: Settings → Licence → Enter code → Activate
Deactivate: Settings → Licence → Deactivate (frees the seat)
Transfer: Deactivate on the old machine, then activate on the new one.

You can also manage your licence from the online account portal: view your subscription, change payment method, or download invoices.

If you lose access to the old machine, contact support — we can remote-deactivate for you.

OnCue checks for updates automatically when connected to the internet. You'll see a notification in the toolbar.

1. Click the update notification or go to Help → Check for Updates.
2. Download the new installer.
3. Close OnCue Timecode.
4. Run the installer — it will upgrade in place without removing your shows or settings.
5. Relaunch OnCue.

Your shows, templates, and settings are stored in your user profile folder and are never deleted during updates. We recommend backing up before major version upgrades.

LTC (Linear Time Code) is the most common timecode format in live events.

1. Connect an LTC source to your audio interface's line input.
2. In OnCue: Settings → Timecode → Source → LTC Input.
3. Select your audio device (ASIO recommended for lowest latency, WDM also supported).
4. Choose the input channel (left or right).
5. Set the frame rate to match your source (24, 25, 29.97, 30 fps).
6. The timecode display will show incoming TC in real-time.

Troubleshooting:
- No signal? Check cable connections and audio interface gain.
- Dropouts? Use ASIO driver with buffer ≤ 256 samples.
- Wrong time? Verify frame rate matches the source.
- Recommended interfaces: RME (lowest latency), Focusrite, Behringer.

OnCue can generate timecode for your entire production:

LTC output:
1. Settings → Timecode → Output → LTC.
2. Select your audio output device and channel.
3. OnCue will output SMPTE audio on that channel.

MIDI MTC output:
1. Settings → Timecode → Output → MIDI MTC.
2. Select your MIDI output port.
3. MTC is sent continuously while the transport runs.

Art-Net timecode:
1. Settings → Timecode → Output → Art-Net.
2. Set the target IP or broadcast address.
3. Art-Net timecode packets are sent over Ethernet.

You can output multiple formats simultaneously — e.g., LTC for the audio team and Art-Net for the lighting desk.

For large shows with multiple operators or backup machines:

Master machine:
1. Settings → Sync → Mode → Master.
2. Set the sync port (default: 7000).
3. The master broadcasts timecode and cue state over the network.

Slave machine(s):
1. Settings → Sync → Mode → Slave.
2. Enter the master's IP address and port.
3. The slave follows the master's timecode frame-accurately.

The slave displays a sync status indicator (green = locked, yellow = syncing, red = lost).
If the master disconnects, the slave can continue autonomously until reconnected.

Best practice: Use a dedicated Ethernet switch for sync traffic, separate from Art-Net/sACN.

OnCue supports all standard SMPTE frame rates:

• 24 fps — Film and cinema
• 25 fps — PAL/European broadcast (most common in EU live events)
• 29.97 fps (drop-frame) — NTSC broadcast
• 29.97 fps (non-drop) — NTSC production
• 30 fps — Common in US live events

Choose the frame rate that matches your production pipeline. For European live events, 25 fps is standard. For US events, 30 fps is most common.

Important: All devices in your chain must use the same frame rate. Mismatched rates cause drift and sync issues.

Drift and jitter can occur with poor clock sources or long cable runs.

Drift (timecode slowly goes out of sync):
- Check that all devices share the same frame rate.
- Use a single master clock for the entire production.
- For LTC: use a high-quality audio interface with stable clock.
- OnCue's drift compensation can correct up to ±2 frames.

Jitter (timecode jumps erratically):
- Reduce audio buffer size (ASIO: 128-256 samples).
- Avoid USB hubs for audio interfaces — connect directly.
- Shield LTC cables from DMX and power cables.
- Check audio input levels — too low causes read errors.

OnCue logs all timecode anomalies in the health dashboard for post-show analysis.

The cue list is the heart of your show.

Adding cues:
- Click '+' or Ctrl+N to add a cue.
- Set: timecode (when), name (what), action (which output/device).
- Actions include: fire pyro zone, send OSC, send DMX, trigger MIDI, webhook, etc.

Editing:
- Double-click any field to edit in-place.
- Drag rows to reorder (or use Alt+↑/↓).
- Right-click for context menu (duplicate, delete, group, tag).

Tags & filtering:
- Assign colour tags to categorise cues (pyro, lighting, audio, video).
- Filter the list by tag to focus on specific departments.

Templates:
- Save a cue list as a template for reuse across shows.
- Templates preserve all settings except show-specific timecodes.

The timeline gives you a visual overview of your entire show.

- Horizontal axis: timecode (scrollable and zoomable).
- Cues appear as blocks on the timeline, colour-coded by tag.
- Drag cues left/right to change their timecode.
- Drag the edges to set duration (for sustained actions like DMX fades).
- Scroll wheel to zoom in/out.
- Hold Shift and drag to select multiple cues.
- The playhead shows current position during playback.

Timeline lanes:
- Each output type gets its own lane (pyro, DMX, OSC, etc.).
- Collapse/expand lanes to manage complex shows.
- Overlap detection warns you about timing conflicts.

Quick Launch lets you fire cues out of sequence:

1. Press Q to open Quick Launch.
2. Type the cue number or name.
3. Press Enter to fire immediately.

Default hotkeys:
- Space: Play/Pause transport
- Enter: Go (fire next armed cue)
- Escape: Stop transport
- F12: Emergency Stop (all outputs)
- Ctrl+G: Go to timecode
- 1-9: Fire cue by number
- Ctrl+1-9: Arm/disarm cue

Customise hotkeys in Settings → Shortcuts. You can also map external MIDI notes or Stream Deck buttons to any action.

Import:
- File → Import → Select CSV, XML, or JSON file.
- OnCue maps columns automatically (timecode, name, action, notes).
- Preview and adjust mapping before importing.
- Supports cue lists from other show control software.

Export:
- File → Export → Choose format (CSV, XML, JSON, PDF).
- CSV is compatible with Excel and Google Sheets.
- PDF export creates a print-ready cue sheet.

Rentman integration:
- Import equipment and crew lists directly from Rentman.
- See the Integrations section for setup details.

Cue groups let you manage related cues as a unit:

- Select multiple cues → Right-click → Group.
- Groups can be armed/disarmed, moved, and duplicated together.
- Collapse a group to see it as a single row.

Sequences:
- A sequence is a group that fires automatically in order.
- Set delays between cues within the sequence.
- Trigger the sequence with a single Go command.
- Useful for complex pyro effects that need precise inter-cue timing.

The Explo TX2-70K is a professional pyrotechnic ignition system.

Connection:
1. Connect the TX2-70K to your PC via RS232/USB adapter.
2. Install the USB-to-serial driver (included with OnCue or from the adapter manufacturer).
3. In OnCue: Settings → Pyro → Device → Explo TX2-70K.
4. Select the COM port (usually COM3-COM9).
5. Click 'Connect'. The status indicator turns green when connected.

Safety check procedure:
1. OnCue runs a continuity check on all connected zones.
2. Green = circuit OK, Red = open circuit or short.
3. Review all zone statuses before arming.
4. Arm the system only when all safety checks pass.

Important: Always perform a visual safety inspection of the firing area before arming. OnCue is a tool — the operator is ultimately responsible for safety.

Zones organise your pyrotechnic effects by physical location or firing group.

Creating zones:
1. Settings → Pyro → Zones → Add Zone.
2. Name the zone (e.g., 'Stage Left', 'Finale Rack 1').
3. Assign the TX2-70K output channels to the zone.
4. Set the NEM limit per zone (based on safety distance calculations).

Assigning products:
- Each zone can hold multiple products from the product database.
- OnCue calculates total NEM per zone and warns if limits are exceeded.
- Products include article number, NEM value, category, and safety distance.

Zone status during show:
- Armed (ready to fire)
- Fired (all products ignited)
- Partial (some products fired)
- Error (continuity issue)

OnCue includes a built-in product database for pyrotechnics.

For each product you can store:
- Article number and name
- Manufacturer
- NEM (Net Explosive Mass) in grams
- Category (F1, F2, F3, F4, T1, T2)
- Safety distance (m)
- Effect type (mine, comet, cake, single shot, etc.)
- Duration and calibre
- Custom notes

Import/export:
- Import products from CSV or Excel.
- Export your library for sharing with team members.
- Products can be assigned to zones in the cue list.

The database persists across shows — build it once, use it everywhere.

The emergency stop (E-Stop) immediately halts all pyrotechnic firing.

Trigger methods:
1. Keyboard: Press F12 (default hotkey).
2. OnCue Remote: Tap the E-Stop button (available to Operator and E-Stop roles).
3. Hardware: Physical E-Stop button on the TX2-70K.
4. Stream Deck / Companion: Dedicated E-Stop button.

What happens:
- All firing commands stop immediately.
- The TX2-70K disarms all zones.
- The cue list pauses (transport stops).
- A red E-STOP banner appears across the interface.
- The event is logged with timestamp.

Recovery:
- Clear the E-Stop in the app (requires confirmation).
- Re-run safety checks before re-arming.
- The fire log preserves which cues were fired and which were not.

OnCue automatically generates NEM reports for your shows.

Report contents:
- Total NEM per zone and for the entire show
- Product list with NEM values and categories
- Safety distances per zone
- Fire log (what was fired, when, by whom)
- Continuity check results

Export formats:
- PDF (print-ready, professional layout)
- CSV (for spreadsheets and further analysis)

Use these reports for:
- Insurance documentation
- Local authority permits
- Post-show debrief
- Regulatory compliance (EU pyrotechnics directive)

The report is generated automatically after each show and can also be created manually at any time.

OnCue logs every firing event with precise detail:

- Timecode at which the cue was fired
- Zone and channel
- Product name and NEM
- Operator who triggered the cue (or 'auto' for timecoded)
- Firing method (timecode, manual Go, Quick Launch, Remote)
- Any errors or misfires

The fire log is saved automatically with your show file and included in the post-show report. It cannot be edited or deleted — this ensures a tamper-proof record for insurance and compliance purposes.

OnCue Remote lets you control and monitor your show from any phone, tablet or laptop.

1. In OnCue: Settings → Remote → Enable Server.
2. Set a port (default: 8080) and choose your network interface.
3. OnCue displays a QR code on screen.
4. On your phone: scan the QR code with your camera.
5. The Remote opens in your browser — no app needed.

Requirements:
- Both devices must be on the same network (WiFi or Ethernet).
- A dedicated WiFi access point is recommended for reliability.
- The server can handle up to 10 simultaneous connections.

Tip: For outdoor events, use a portable WiFi router with a strong signal.

OnCue Remote supports role-based access control:

Operator:
- Full control: Go, Stop, Pause, Arm, Disarm, E-Stop.
- Can see and fire any cue.
- Requires a 4-digit PIN.

Viewer:
- Read-only: sees live timecode, cue list, and status.
- Cannot trigger any actions.
- Requires a separate PIN (or no PIN for open access).

E-Stop:
- Can only see live timecode and the E-Stop button.
- Designed for safety personnel who need emergency access.
- Requires its own PIN.

Set PINs in Settings → Remote → Roles. Change PINs for every show as a security best practice.

The Remote display shows:

- Large timecode readout (real-time, < 20ms latency on LAN)
- Current cue name and status
- Next cue preview (name, timecode, countdown)
- Transport status (playing, stopped, armed)
- Zone status (for pyro shows)
- Health indicators (sync, connections, errors)

The display automatically adapts to your screen size. On tablets, you get a more detailed view with the cue list visible.

Dark mode is default (optimised for backstage use). A high-contrast mode is available for bright environments.

Art-Net lets you send DMX data over your Ethernet network.

1. Settings → Outputs → Add → Art-Net.
2. Set the target IP (unicast) or use broadcast (2.255.255.255).
3. Choose the Art-Net universe (0-32767).
4. Set the update rate (default: 40 Hz, max 44 Hz).

In your cues:
- Assign Art-Net actions to set channel values.
- Support for fades: set start value, end value, and duration.
- Snap actions for instant changes.

Works with any Art-Net node: Enttec ODE, ChamSys, ETC, ADJ, Luminex, etc.

Tip: Use unicast for reliable delivery; broadcast for quick testing.

sACN (Streaming ACN, ANSI E1.31) is the modern standard for professional lighting:

1. Settings → Outputs → Add → sACN.
2. Choose multicast (default, auto-joins the right multicast group) or unicast.
3. Set the universe (1-63999).
4. Set priority (default: 100; higher priority wins if multiple sources).

Advantages over Art-Net:
- Built-in priority system for source takeover.
- Multicast reduces network traffic.
- No 4-universe-per-subnet limit.

OnCue outputs up to 16 sACN universes simultaneously.

OSC is the most flexible protocol for inter-app communication.

Sending OSC from OnCue:
1. Settings → Outputs → Add → OSC.
2. Set the target IP and port.
3. In your cue action, set the OSC address (e.g., /cue/1/go) and arguments.

Receiving OSC in OnCue:
1. Settings → Inputs → OSC → Enable.
2. Set the listen port (default: 8000).
3. Map incoming OSC addresses to OnCue actions (Go, Stop, fire cue, etc.).

Common integrations:
- QLab: /cue/{number}/go, /cue/{number}/stop
- Resolume: /composition/link/values, /layer/1/clip/1/connect
- TouchDesigner: custom addresses
- Ableton Live: via OSC plugin

OnCue supports all standard MIDI protocols:

MIDI Notes:
- Send note-on/off to trigger external gear.
- Receive notes to trigger OnCue cues.
- Map any note/channel combination.

MIDI MTC:
- Send MIDI Time Code (see Timecode section).
- Receive MTC for external sync.

MIDI Show Control (MSC):
- Send MSC commands: Go, Stop, Resume, All Off, etc.
- Target specific devices by device ID.
- Receive MSC commands from external controllers.

Setup: Settings → MIDI → Select your MIDI port(s). OnCue detects all connected USB MIDI interfaces automatically.

The WebSocket protocol enables real-time two-way communication.

1. Settings → API → WebSocket → Enable.
2. Set the port (default: 9000).
3. Connect from any WebSocket client (browser, Node.js, Python, etc.).

Message format: JSON

Incoming commands:
- {"action": "go"} — fire next cue
- {"action": "stop"} — stop transport
- {"action": "fire", "cue": 5} — fire specific cue
- {"action": "estop"} — emergency stop

Outgoing events:
- Timecode updates (configurable rate)
- Cue fired / cue complete events
- Transport state changes
- Error and warning events

Use this to build custom control panels, dashboards, or integrate with any programming language.

MQTT connects OnCue to IoT platforms and smart devices.

1. Settings → Outputs → Add → MQTT.
2. Set broker address, port, username/password.
3. Configure topics for publishing and subscribing.

Publishing (OnCue → devices):
- Topic: oncue/cue/fired — payload: cue data as JSON
- Topic: oncue/transport/state — payload: playing/stopped
- Topic: oncue/timecode — payload: current TC

Subscribing (devices → OnCue):
- Topic: oncue/command/go — trigger Go
- Topic: oncue/command/fire/{n} — fire cue n

Use cases: trigger haze machines, activate LED strips, control motorised scenery, integrate with home automation (Home Assistant, etc.).

Webhooks send HTTP requests when events occur in OnCue.

1. Settings → Outputs → Add → Webhook.
2. Set the URL, method (POST/GET), and headers.
3. Choose which events trigger the webhook (cue fired, show started, E-Stop, etc.).

Payload: JSON with event type, timecode, cue data, and timestamp.

Integration examples:
- Zapier: trigger automations from OnCue events.
- Make (Integromat): complex workflows with multiple steps.
- n8n: self-hosted automation.
- Slack/Teams: post show status updates to a channel.
- Custom API: trigger any web endpoint.

Webhooks are fire-and-forget — they don't block the show if the endpoint is slow or down.

Bitfocus Companion bridges OnCue to physical button panels.

Setup:
1. Install Bitfocus Companion on the same machine or network.
2. In Companion: Add connection → OnCue Timecode.
3. Enter OnCue's IP address and WebSocket port.
4. Companion connects automatically.

Available actions:
- Go, Stop, Pause, Resume
- Fire specific cue by number
- Arm/Disarm
- Emergency Stop
- Next cue / Previous cue

Feedback:
- Current cue name and number
- Timecode display
- Transport state (playing/stopped/armed)
- E-Stop status

Works with Elgato Stream Deck (all models), X-Keys, and any other Companion-supported device.

Connect OnCue to your Rentman account for seamless project management.

1. Settings → Integrations → Rentman → Connect.
2. Authorise OnCue with your Rentman API key.
3. Select a project to import.

Imported data:
- Equipment list with quantities and serial numbers.
- Crew assignments and contact details.
- Project dates and venue information.
- Custom fields (mapped to OnCue cue notes).

This helps you prepare shows faster — equipment lists become your starting cue list, and crew info is available in the show file for reference.

Note: Rentman integration requires an active Rentman account with API access.

QLab and OnCue communicate over OSC.

OnCue → QLab:
1. Add an OSC output pointing to QLab's IP and port (default 53000).
2. In your cue action: OSC address /cue/{number}/go, /cue/{number}/stop, etc.
3. OnCue triggers QLab cues at the right timecode.

QLab → OnCue:
1. In QLab: send OSC to OnCue's IP and port.
2. Use /oncue/go, /oncue/fire/{n}, etc.
3. QLab can trigger OnCue actions.

Common setup: OnCue as master timecode, triggering both QLab (for audio/video) and pyro simultaneously.

After each show, OnCue generates a detailed show report.

Contents:
- Show name, date, venue, and crew
- Total runtime and cue count
- Every event in chronological order (cues fired, errors, E-Stops)
- Timecode accuracy analysis (drift, jitter, dropouts)
- Pyro report: NEM totals, fire log, zone status
- Integration events: OSC, Art-Net, MIDI messages sent

Export as PDF for archiving or share with your production team.

The report is generated automatically when you stop the show. You can also generate it manually at any time from File → Export → Show Report.

The health dashboard shows live system status:

- Timecode: signal quality, frame rate, drift
- Network: Art-Net/sACN nodes connected, latency
- MIDI: ports active, message count
- Pyro: TX2-70K connection, zone continuity
- Remote: connected clients, latency
- CPU and memory usage

Colour indicators:
🟢 Green = healthy
🟡 Yellow = warning (investigate)
🔴 Red = error (action needed)

All health data is logged and included in the post-show report.

OnCue can email show reports automatically after each performance.

1. Settings → Reports → Email → Enable.
2. Configure SMTP settings (server, port, credentials).
3. Add recipient email addresses.
4. Choose what to include: full report, summary only, or PDF attachment.

The email is sent automatically when you end the show. Useful for keeping remote stakeholders, production managers, and insurance contacts informed.

Post-show analysis tools help you improve future performances.

Heatmaps:
- Visual timeline showing cue density and timing.
- Red zones indicate high-activity moments.
- Helps identify potential bottlenecks or overloaded sections.

Statistics:
- Average cue-to-cue timing
- Cue accuracy (how close to target timecode)
- Response times (manual triggers)
- Error rate per zone/output

Compare across shows to track improvement over time. Export charts as images for presentations or debriefs.

A well-designed network is critical for reliable show control.

Recommendations:
- Use gigabit Ethernet switches (not WiFi) for Art-Net, sACN, and sync.
- Separate traffic: dedicated VLAN or switch for show control vs. internet.
- Use static IP addresses for all show-critical devices.
- Disable sleep/hibernate on the OnCue PC.
- Disable Windows Firewall for the show control network interface (or add rules).

WiFi (for OnCue Remote):
- Use a dedicated access point (not the venue's WiFi).
- 5 GHz band for lower latency.
- Position the AP with line-of-sight to operators.

Test the entire network before every show — OnCue's health dashboard shows network status.

For critical shows, redundancy is essential.

Show file backup:
- OnCue auto-saves every 60 seconds.
- Keep copies on USB drive and cloud storage.
- Version your show files (show_v1.ocue, show_v2.ocue).

Machine redundancy:
- Set up a slave machine with the same show file.
- The slave follows the master and can take over if the master fails.
- Practice the switchover procedure before the show.

Network redundancy:
- Use managed switches with link aggregation.
- Carry a spare switch and cables.
- Have a backup WiFi AP for Remote.

Optimise your Windows PC for reliable show control:

1. Power plan: Set to 'High Performance' (not Balanced).
2. Disable sleep, hibernate, and screen timeout.
3. Disable automatic Windows Updates during shows.
4. Close unnecessary background apps (Outlook, Teams, browsers).
5. Set your audio interface to exclusive mode in Windows Sound settings.
6. Disable USB selective suspend in Power Options.
7. For ASIO: set buffer to 128-256 samples.
8. Disable Wi-Fi on the show control NIC (use Ethernet only).
9. Run OnCue as Administrator for best performance.
10. Keep 20%+ free disk space on the system drive.

OnCue monitors CPU and memory in the health dashboard — aim for < 50% CPU during shows.

The WebSocket API lets you build custom interfaces.

Connect to: ws://{oncue-ip}:{port}
Authentication: Send {"auth": "your-api-key"} after connecting.

Events you receive:
- timecode: {"type": "tc", "tc": "01:23:45:12", "fps": 25}
- cue_fired: {"type": "cue", "id": 5, "name": "Pyro Zone 1", "tc": "..."}
- transport: {"type": "transport", "state": "playing"}
- estop: {"type": "estop", "active": true}

Commands you can send:
- {"action": "go"}
- {"action": "stop"}
- {"action": "fire", "cue": 5}
- {"action": "arm", "zone": 1}

Build with HTML/CSS/JS, React, Python, Node.js, or any language with WebSocket support.

If OnCue shows no incoming timecode:

1. Check physical connections — is the LTC cable plugged in correctly?
2. Check audio interface levels — is there signal on the input? Use your audio interface's meter.
3. Verify the correct input is selected in Settings → Timecode.
4. Check the frame rate setting — it must match the source.
5. Try a different audio input channel (left/right).
6. Restart the audio interface and OnCue.
7. Test with a different LTC source or cable.
8. Check Windows Sound settings — ensure the interface is not muted or disabled.

If using MIDI MTC: verify the MIDI port is selected and not in use by another application.

If your Art-Net or sACN devices aren't responding:

1. Verify network connection — can you ping the device?
2. Check IP addresses — both devices must be on the same subnet.
Art-Net default range: 2.x.x.x or 10.x.x.x
sACN: any subnet (multicast handles routing).
3. Check that Windows Firewall allows OnCue on the network.
4. Verify the universe number matches on both ends.
5. Check the output is enabled and active in OnCue's output list.
6. Try broadcast/multicast instead of unicast (or vice versa).
7. Use Wireshark to verify packets are being sent.

Common issue: Windows assigns a 169.254.x.x address when DHCP fails — set a static IP instead.

If OnCue can't connect to the TX2-70K:

1. Check the USB/RS232 cable connection.
2. Verify the COM port in Windows Device Manager.
3. Make sure no other software is using the COM port.
4. Try a different USB port (avoid hubs).
5. Reinstall the USB-to-serial driver.
6. Power-cycle the TX2-70K.
7. In OnCue: Settings → Pyro → Refresh COM ports.

If connected but communication fails:
- Check baud rate (default: 9600).
- Verify the TX2-70K firmware is compatible.
- Try lowering the poll rate in advanced settings.

If OnCue feels sluggish or the timecode display stutters:

1. Check CPU usage in the health dashboard — should be < 50%.
2. Close other applications (especially browsers with video).
3. Set Windows power plan to High Performance.
4. Reduce the number of active outputs if CPU is high.
5. For large shows (200+ cues): ensure you have 16 GB RAM.
6. Disable the timeline visualisation during playback (reduces GPU load).
7. Check for disk activity — SSD strongly recommended.
8. Disable Windows Defender real-time scanning for the OnCue directory.
9. Update your graphics drivers.
10. As a last resort: restart Windows fresh before the show.

If licence activation fails:

1. Check your internet connection — activation requires a one-time online check.
2. Verify the licence code is entered correctly (copy/paste to avoid typos).
3. Check that the licence hasn't been activated on another machine (deactivate first).
4. Ensure the date/time on your PC is correct.
5. If behind a corporate firewall, whitelist api.oncuetimecode.nl.
6. Try running OnCue as Administrator.

Still not working? Contact support with your licence code and the error message. We can check the activation status on our end.