Documentation
Setup guides, system requirements, and production workflows for every CueForge tool.
System Requirements
| Requirement |
Details |
| Operating System |
macOS 13 (Ventura) or later |
| Processor |
Apple Silicon (M1+) or Intel — Universal Binary |
| RAM |
4 GB minimum (8 GB recommended for CuePatch multi-surface) |
| Audio Interface |
Any CoreAudio-compatible interface with line input (for CueRoll/CueMaker LTC) |
| Network |
None required — all tools work fully offline |
⚠️ First Launch: On first launch, right-click the app → Open → click "Open" in the dialog. After that it runs normally. This is a one-time step.
Installation
All CueForge tools are standalone .app bundles. No installer needed.
Steps
- Download your .dmg file from the link in your purchase email
- Open the .dmg and drag the app to your Applications folder
- First launch: right-click → Open → Open (Gatekeeper bypass, one-time only)
- Grant audio input permission when prompted (CueRoll/CueMaker only)
💡 Tip: Keep the .dmg in a safe place. Your purchase includes free updates — re-download links are sent via email when new versions ship.
📝 CueRoll Coming Soon
LTC timecode note-taking for live production. CueRoll listens to LTC timecode from your audio interface and lets you drop timestamped notes with a single keypress.
When to Use It
- Tech rehearsals — log fix notes as they happen
- Show calls — mark cue timing for review
- Post-show notes — capture feedback timestamped to the running show
- Multi-department handoffs — export notes for lighting, video, audio teams
Typical Workflow
Feed LTC to audio input
→
Open CueRoll
→
Select audio source
→
Press key → note drops
→
Export list
LTC Input Setup
CueRoll reads LTC (Linear Timecode) from any CoreAudio input. You'll need:
- An audio interface with a line-level input
- LTC fed from your timecode source (console, media server, playback rig)
- Input level: aim for -12 to -6 dBFS (standard LTC level)
grandMA3 → LTC Output → Audio Interface Line In
disguise → LTC Output → Audio Interface Line In
QLab → LTC Output → Audio Interface Line In
Playback Pro → LTC Output → Audio Interface Line In
Sessions
CueRoll organizes notes into sessions. Create a new session for each tech, dress, or show call. Sessions are saved locally and persist between launches.
Export Formats
- CSV — Open in Excel/Google Sheets, sort and filter
- JSON — Integrate with other tools or scripts
- Plain text — Copy/paste into emails or chat
💡 Pro move: Run CueRoll on a laptop next to the console during tech. At the end of the day, export the notes list and email it to the whole production team. Everyone gets a clean, timestamped log of every note called — no more "what timecode was that fix at?"
🎬 CueMaker Coming Soon
LTC timecode reader with marker creation and grandMA3 XML export. Program timecoded shows without a console in front of you.
When to Use It
- Pre-programming — build marker lists before load-in
- On-site — create markers in real-time during playback
- Remote prep — build gMA3 timecode tracks from a hotel room
- MTC bridging — sync other software via MTC output
Typical Workflow
Feed LTC to audio input
→
Open CueMaker
→
Watch waveform + TC
→
Press M → marker drops
→
Export gMA3 XML
Key Features
- Live waveform — Visual confirmation that LTC is decoding
- Marker creation — Press M to drop a marker at current timecode
- 6-channel mixer — Monitor audio alongside LTC
- MTC output — Feed MIDI timecode to disguise, QLab, or other software
- grandMA3 XML export — Drop the file into your show and markers appear
grandMA3 Import
1. Copy the .xml file to your gMA3 show folder
2. In grandMA3: Menu → Import → XML → select your file
3. Markers appear in the timecode pool
4. Assign markers to your timecode track
💡 Pro move: Record LTC from rehearsal audio, then build your marker list at your desk with headphones. Export to gMA3 XML and load it at the next session. You show up with a pre-built timecode track.
⬚ CuePatch Coming Soon
Pixel map builder for LED walls. Built-in tile databases, calibration patterns, and instant PNG export.
When to Use It
- LED wall checkout — generate pixel maps in 30 seconds, not 30 minutes
- Pre-vis — verify wall dimensions and tile layout before load-in
- Calibration — output test patterns matched to your exact tile config
- Documentation — export maps for the production binder
Typical Workflow
Select tile type
→
Set wall dimensions
→
Choose pattern
→
Export PNG
Built-in Tile Database
| Manufacturer |
Example Tiles |
Availability |
| ROE Visual |
Black Pearl, Carbon, Diamond |
Free + Pro |
| Absen |
PL Series, KL Series |
Pro |
| Unilumin |
UpadIII, Ustorm |
Pro |
| INFiLED |
DB, ER Series |
Pro |
Free vs. Pro
- Free: Single surface, basic tile labels, PNG export, ROE tiles
- Base: Multi-surface, full tile database, calibration patterns, batch export, NotchLC support
💡 Pro move: Export pixel maps the night before checkout. Load them on a thumb drive. When you arrive on site, the maps are ready to throw up on the wall immediately while processors are still being patched.
✓ CueCheck Available
Content validation for production deliverables. Verify media files meet spec before they hit the wall.
What It Will Do
- Validate resolution, codec, frame rate, and color space of video files
- Check files against show spec sheets
- Batch validation of entire content drops
- Export validation reports for producers and content creators
Why It Matters
Every video engineer knows the pain: content arrives on-site, you load it into the media server, and it's the wrong resolution, wrong codec, or wrong frame rate. CueCheck catches those problems before load-in, not during it.
⏳ Status: Core validation engine is working. GUI and daemon mode are in development. Join the mailing list for launch notification.
Support
CueForge tools are built by a touring production professional. When you email, you're talking to the person who built it — not a support queue.
Get Help
- Email: steve@cueforgelabs.com
- Response time: Usually within 24 hours (unless I'm on a show)
- Include: macOS version, audio interface model, what happened vs. what you expected
Feature Requests
I build what the community needs. Email your workflow and what's missing — if it makes sense, it goes on the roadmap. Many features in the current versions came from user requests.