CUEPRINT

Docs / 04

Troubleshooting

First reflex for anything odd: open a System Monitor window (Add Window → More → System Monitor). Every run prints [CUEPRINT] lines saying exactly what it did, which properties it read, and the full path of any file it wrote. Most “it didn’t work” cases are answered by one of those lines.

The plugin doesn’t appear in the Import list

The console only scans the exact library path. Check, character for character:

<usb>/grandMA3/gma3_library/datapools/plugins/

Common misses: grandMA3 folder missing at the root of the stick, plugin instead of plugins, or cueprint.lua / cueprint.xml split across folders. Both files must sit in the same directory. If the import dialog still refuses, your MA3 version may want a different DataVersion in cueprint.xml — open it in a text editor and match the version of any plugin exported from your own console.

I updated, but the popup shows the old version

Imported plugins keep their own copy of the code inside the show file. Replacing the files on disk is not enough — re-import cueprint.xml into the pool slot. The popup title is the check: it shows the running version.

The export ran but I can’t find the file

  • The log line CSV path: / Guion path: is the truth — it prints the full path of every file written.
  • On a physical console the default target is the internal drive, which has no file explorer. Aim exports at a USB stick instead: run Discovery once with the stick inserted, read the PATHS & DRIVES section in the log to find the stick’s path, and set it as output_dir_override at the top of cueprint.lua.
  • Empty sequences are skipped by design, with a clear error in the log — no empty files are written.

Columns look wrong in Excel

  • Everything lands in one column — your Excel locale expects ; separators. Re-export choosing Excel espanol (;) in the popup.
  • Fractional cues (6.1) align left / sort as text — same cause, same fix: the ; flavor writes decimal commas so Spanish Excel reads them as numbers.
  • ####### in a cell — the column is just too narrow; drag it wider.

Pro: “The exported XML was not found”

The one-step guion runs MA3’s own Export Sequence and then reads the file back. If the log shows this error, it also lists every directory it probed — send that list to support. Workarounds meanwhile: type the sequence number in the popup (the export command requires it), or export the XML yourself and drop it on cueprint_pro_viewer.html.

Viewer: “Formato no reconocido”

The viewer accepts sequence exports only — from MA3 (gma3_library/datapools/sequences/*.xml) or MA2 (gma2/importexport/). Fixture/preset/macro exports are different files and won’t parse.

MA2: a column comes out empty in the guion

MA2 parsing is validated against real v3.9 console exports — cue numbers, names, fades, channel/fixture values and preset references included. If a trigger-time column (or anything else) is blank on your export, email the XML to support: those fields vary between MA2 versions and the parser is extended against real files.

Still stuck?

Email the address on your receipt with:

  1. Console model and software version,
  2. Your license key,
  3. The [CUEPRINT] log lines (or a System Monitor photo).

Pro licenses get priority turnaround, but nobody waits long.