Reports & DocumentationReports & Documentation

Reports & Documentation

Thirty-six reports built from the show you already have. Shape the columns, put your logo on it, print or export a PDF.

Reports & Documentation

Overview

Everything you put into Prismatik — the patch, the tracks, the media, the cables, the lineup — is paperwork waiting to happen. This is where it comes out: channel hookups, DMX patch sheets, pull sheets, power schedules, setlists, run of show, and a Comprehensive report that binds the lot into one document with a cover and contents.

Reports read the show that is open. There is nothing to assemble and nothing to keep in step — change the patch, print again.

When to Use

  • Handing a patch to a house crew who need it on paper
  • A pull sheet for the shop the day before a load-out
  • A setlist for the desk, with timecode so it can be followed
  • Sending a production book to a client as a single PDF

Step-by-Step

  1. Pick a category — Lighting, Video, Media, Show, Production, Manifest or Lineup — or leave it on All.
  2. Choose a report. The preview is the document; it is not an approximation of it.
  3. Set it up. Options for paper size, orientation and font size; Columns for what the table shows.
  4. Print, or Export PDF.

Shaping a report

Columns

Reports that draw a table let you choose the columns and their order.

  • Click a column to turn it off; click again to bring it back where it was.
  • The arrows move a column left or right.
  • Some columns are optional — off until you ask for them, because most people do not want them on a printed page. Notes and Mood are the obvious ones.
  • Reset returns the report to its declared columns.

Your choices are kept per machine rather than per show, because a column layout is how you like a report to read — not something to set again for every production.

Columns → Letterhead → Add logo puts a logo at the top of every report, aligned left, centre or right. It is embedded in the document rather than linked, so it survives into a PDF handed to someone else. Keep it under 2MB.

Paper and pagination

Reports print at 0.75in margins on US Letter or A4, set in Options and carried into the printed page and the PDF alike.

Some pagination is decided for you, because it is what makes a document usable at a desk:

  • Each setlist starts a new page. A set that began halfway down a page under the tail of the previous one was no use to anyone.
  • Each section of the Comprehensive report starts a new page, after the cover and contents.
  • Tables repeat their header when they run onto another page.
  • Rows are never split across a page break, and a heading is not left stranded at the foot of one.

The preview shows the same pages the printer will produce, breaks included.

Common Workflows

One show, several audiences

Build the report once, then use Columns to cut it down for each reader — the shop wants quantities and weights, the LD wants channels and addresses, the client wants neither. Nothing is duplicated; you are printing the same report two ways.

The whole book

Comprehensive Show puts a cover, a contents page and every major report into one document. It is the thing to hand over at the end of prep.

Troubleshooting

A report is empty

It is reading the show that is open. A patch report needs a Manifest, a setlist report needs setlists, and Run of Show needs a lineup belonging to this show — lineups are per show, so one built under another production will not appear here.

The PDF and the preview disagree

They should not; tell us if they do. The preview reads the same break positions the printer uses.

A column I want is not offered

Not every report has been moved onto the column model yet — Setlist and Track Library are, and the rest follow. Reports still on their original tables show fixed columns.

  • Manifest — the register most patch reports are built from
  • Timeliner — where a track’s timecode offset is set
  • Tag It! — labels rather than paperwork

Source

Component: ReportsAndDocumentation