Skip to content
Helm Docs

Helm Clock

Idea Summary

Section titled “Idea Summary”

Helm Clock is a compact hardware device inspired by the Rosendahl MIF4 MIDI Timecode Interface, designed to serve as a central timecode generator, distributor, and monitor within the Helm platform. It integrates seamlessly with Helm software (e.g., Helm Cues and Helm DJ) to handle timecode synchronization, audio playback routing, and protocol conversion for live production environments. The device ensures precise timing across systems like DJ hardware (via Pro DJ-Link), lighting consoles (e.g., GrandMA), video servers (e.g., Resolume Arena), and DAWs (e.g., Reaper). It acts as a bridge for timecode formats such as LTC (Linear Timecode), MTC (MIDI Timecode), and SMPTE, while providing audio outputs and network capabilities for distributed control.

The core purpose is to eliminate fragmented workflows in live events by offering a reliable, all-in-one timecode management tool. It displays timecode on an 8-digit 7-segment LED for quick visibility, uses a small 1x1” OLED screen for menu navigation, and an encoder for user control. Built initially on a Raspberry Pi for MVP prototyping, it aims for scalability to custom microcontrollers for cost efficiency in production.

How It Should Work

Section titled “How It Should Work”
  1. Timecode Handling:
    • Input: Accepts LTC via XLR input or MTC via MIDI/USB/Network.
    • Processing: Re-clocks incoming timecode to reduce jitter (using algorithms similar to MIF4’s suppression of drop-outs). Supports forward/reverse/stationary timecode at variable speeds (e.g., 5-500% nominal, inspired by MIF4 specs).
    • Output:
      • Duplicate LTC on two XLR outputs.
      • MTC over MIDI out and network (via RTP or custom protocol).
      • Timecode display on 8-digit 7-segment LED (HH:MM:SS:FF format, supporting 24/25/30 FPS).
    • Sync Protocol: Implements a custom fast-transfer protocol for data/timecode sync across devices/software, ensuring low-latency alignment (full spec in separate tech doc).
  2. Audio Routing:
    • Acts as a USB/Network soundcard for Helm software.
    • Playback Audio: Routes timeline audio from software (e.g., tracks in Helm Cues) to Minijack and Phono (RCA) outputs—never outputs timecode here.
    • Timecode Audio: LTC exclusively via XLR outputs.
  3. User Interface:
    • Display: 8-digit 7-segment for primary timecode readout; 1x1” OLED screen for menus (e.g., input source selection, output config, network settings).
    • Control: Rotary encoder with push-button for navigation—simple, intuitive menu structure to avoid complexity in live settings.
    • Boot Process: Custom disk image for Raspberry Pi (or equivalent) boots directly into the application, stripping unnecessary OS elements for efficiency and reduced CPU load.
  4. Connectivity:
    • Inputs: 1x XLR (LTC), MIDI In, USB-C (power/data), Ethernet (network sync).
    • Outputs: 2x XLR (LTC), MIDI Out, Phono (RCA stereo), Minijack (3.5mm stereo).
    • Network: Ethernet for RTP MIDI, custom sync protocol, and potential VOIP talkback in future iterations.
  5. Integration with Helm Ecosystem:
    • Connects to Helm software over USB/Network for cue triggering, track data, and automation.
    • Supports re-clocking for stable sync in multi-device setups (e.g., with CDJs via Pro DJ-Link).

Big Options to Think About

Section titled “Big Options to Think About”
  • Microcontroller Choice: Raspberry Pi for MVP (easy development, Linux-based for networking/audio). Alternatives: ESP32 or STM32 for production—lower power, cheaper, but requires custom firmware.
  • Power Options: USB-C for power (5V/3A min). Consider PoE (Power over Ethernet) for pro setups.
  • Enclosure: Compact, rugged design for live use (metal/aluminum for EMI shielding). Rack-mountable or portable.
  • Scalability: Modular design for adding features (e.g., more XLRs, wireless sync via Wi-Fi module).
  • Software/Firmware: Open-source base for protocol (leverage existing like rtpmidi). Custom boot image to minimize latency.
  • Cost vs. Features: Balance MVP simplicity (core timecode/audio) with future expansions (e.g., embedded VOIP, video mapping integration).

Considerations

Section titled “Considerations”
  • Reliability in Live Environments: Must handle jitter/drop-outs (target <1ms latency). Test against MIF4 benchmarks (e.g., -30 to +20dBu input tolerance).
  • Compatibility: Ensure broad support for SMPTE standards, Pioneer hardware, and common software (QLab, TimecodeMate).
  • Regulatory: FCC/CE compliance for audio/EMI; safety for XLR voltages.
  • Development Challenges: No official Pro DJ-Link docs—rely on open-source reverse-engineering. Network protocol must be efficient to avoid bandwidth issues.
  • User Experience: Keep UI minimal to prevent errors under pressure; dark-mode friendly for low-light stages.
  • Cost Scaling: MVP ~$100-200/unit; production target < $50 via custom PCBs and bulk manufacturing.
  • Security: Network features need encryption for sensitive show data.

This device positions Helm as a comprehensive ecosystem, starting from software and expanding to hardware for unified live production control.