NRG2CUE Generator: Setup, Tips, and TroubleshootingThe NRG2CUE generator is a specialized tool used in live production and event workflows to convert, organize, and trigger energy (NRG) cues — timed control signals for lighting rigs, audio playback, pyrotechnics, and show automation systems. Whether you’re integrating NRG2CUE into a touring rig, a theatre production, or a broadcast environment, this guide walks through step-by-step setup, practical tips to streamline your workflow, and troubleshooting techniques for common problems.
What the NRG2CUE Generator Does (Overview)
The NRG2CUE generator translates energy-event data into cue-ready actions. It usually ingests input from systems like timecode, MIDI, OSC, sensor feeds, or proprietary NRG files and outputs discrete cue events to lighting desks, show controllers, audio playback systems, or safety interlocks. Typical capabilities include:
- Mapping input channels to cue IDs and device outputs
- Scheduling and time-based triggering (timecode, internal clocks)
- Cue chaining, conditional triggers, and rollback/abort logic
- Redundancy and failover handling for critical shows
- Logging and diagnostic tracing for post-show analysis
Setup
1) Pre-setup checklist
Before starting, gather:
- NRG2CUE hardware or software license and latest firmware/software build
- Show files (NRG or compatible formats), cue lists, and device maps
- Connection plan: network diagram, DMX/Art-Net/USB/MIDI cables, and power sources
- Timecode source (LTC/MTC) or synchronization plan (PTP/NTP)
- Backup strategy: secondary timecode source and redundant power if needed
2) Physical and network connections
- Connect the NRG2CUE unit to your network via a dedicated VLAN if possible to isolate show traffic.
- Link lighting and control outputs (Art-Net/sACN, DMX over USB, MIDI) per the device map. Label every cable and port.
- Power: use an Uninterruptible Power Supply (UPS) for both the NRG2CUE unit and primary show-critical devices.
3) Install and update software/firmware
- Upgrade to the latest firmware/software first; read release notes for breaking changes.
- Back up current configuration before applying updates.
- After updating, verify that device drivers and OS-level dependencies (if any) are compatible.
4) Basic configuration
- Assign a static IP or reserve a DHCP lease for the NRG2CUE device to avoid address changes mid-show.
- Set timecode preferences (LTC/MTC, frame rate) matching your master clock.
- Import or create cue lists and map input channels to target devices. Use clear, descriptive names for cues and devices.
5) Testing and verification
- Run an isolated test with a subset of cues and devices. Observe timing accuracy and end-to-end latency from trigger to action.
- Validate cue chaining and conditional triggers (e.g., pause on fault, resume on clear).
- Log a dry run with time stamps for later analysis.
Practical Tips and Best Practices
Redundancy & Safety
- Use dual timecode sources (primary/backup) and configure automatic failover.
- Program safe default states for outputs in case of a crash (e.g., lights to blackout, audio muted).
- Keep a manual override plan and labeled physical controls for emergency stops.
Performance & Latency
- Keep network traffic on a separate VLAN and avoid broadcast storms; use IGMP snooping for sACN.
- Prefer wired connections for reliability; use high-quality cables and maintain connectors.
- Pre-cache large audio or media files on local drives rather than streaming over the network.
File Management
- Version-control cue lists and configuration files; include a changelog for every edit.
- Use human-readable cue names and group related cues into folders/scenes.
- Export a compact, printable cue sheet for the stage manager and operator.
Collaboration & Handoffs
- Standardize cue naming and numbering conventions across departments (audio, lighting, show control).
- Prepare a “show brief” with key timings, backup plans, and contact list for crew.
- Train at least two operators on the NRG2CUE workflow and emergency procedures.
Troubleshooting
Problem: Device not responding to cues
- Check physical connections and power to the target device.
- Verify IP addresses, network masks, and that the NRG2CUE’s outputs are mapped to the correct target.
- Confirm that the target accepts the protocol being used (Art-Net vs sACN vs DMX vs MIDI).
Problem: Timing drift or mismatched timecode
- Confirm frame rates match between the NRG2CUE and the master timecode source.
- Inspect cabling for noise or intermittent connections on LTC lines.
- If using network time protocols (PTP/NTP), ensure the NTP server is reachable and stable; consider hardware timecode sync for mission-critical shows.
Problem: Intermittent cue firing
- Look for network congestion or broadcast storms; check switches for errors and enable QoS for show traffic.
- Review logs for dropped packets or device faults.
- Simplify: temporarily disable non-essential devices and re-test to isolate the faulty subsystem.
Problem: Cue list corruption or missing cues
- Restore from the latest backup or previous stable version.
- If using external storage (USB drive, NAS), check for file system errors and perform a disk integrity check.
- After restoring, run a full test of all cues before the live event.
Problem: Firmware/software incompatibilities after update
- Keep a rollback firmware image available before upgrading.
- If incompatibility appears, revert to the previous known-good version and contact vendor support with diagnostic logs.
- Test updates in a staging environment where possible.
Advanced Features & Integration
Conditional logic and scripting
Many setups support scripting or conditional cues (if X and Y, then trigger Z). Use these sparingly and document logic clearly. Test edge cases like simultaneous triggers and race conditions.
Analytics and logging
Enable verbose logging during rehearsals, then analyze timestamps to tune latency and ordering. Maintain logs for post-show troubleshooting and to build a performance baseline.
Integration with DAWs and media servers
When syncing to audio playback, pre-roll media servers and confirm that playheads align with timecode. Use MIDI Machine Control (MMC) or Transport over OSC where supported for tighter control.
Example Quick Checklist (Pre-show)
- Firmware/software up to date and tested.
- Static IP assigned; network VLAN configured.
- Timecode source verified and frame rate matched.
- Cue list imported and validated; backups present.
- UPS for critical devices; manual overrides labeled.
- Two trained operators briefed.
When to Contact Vendor Support
- Hardware failures (power supply faults, unresponsive ports)
- Reproducible software crashes after rollback attempts
- Cryptic errors in logs that your team cannot diagnose within rehearsal time
When contacting support, supply: device serial, firmware/software versions, log exports, a concise description of steps that reproduce the issue, and network topology.
Troubleshooting and robust planning make the difference between a smooth show and a cascade of last-minute fixes. A disciplined setup, redundancy planning, consistent file/version control, and rehearsed emergency procedures will keep your NRG2CUE-driven productions reliable and repeatable.
Leave a Reply