Avolites Titan

Write Timeliner’s markers straight onto a Titan timeline over the network. No CSV, no USB stick, no import dialog on the desk — and sending again updates the markers instead of duplicating them.

Overview

Timeliner has always exported a file for Titan. That file has to be saved, carried to the console, found in a file browser and imported — and most failed imports are a step in that chain rather than anything wrong with the file.

Titan’s WebAPI takes markers directly. Prismatik finds the console, asks it what timelines it has, pairs them to your tracks, and writes.

The property that matters: each marker carries its Prismatik id, so sending the same set twice updates what moved instead of laying a second set beside the first. Re-ingest a re-delivered track, send again, and only the markers that actually changed change.

That is the thing file-based routes cannot do. Cuepoints’ own grandMA3 documentation notes you cannot merge into a sequence you already exported.

Before you start

• Titan v10 or later, with the WebAPI reachable. Confirmed working on Titan 19.1 (DiamondXL).
• The console and your machine on the same network.
• Prismatik uses port 4430, the non-interactive one. It does not touch the panel the operator is looking at. (4431 does, which is why it is not used.)

The Titan WebAPI has no authentication

None. Anything that can reach a console can drive it, including calls that fire cues.

Prismatik therefore never searches for a console on its own and never connects unasked — you enter an address and press a button, every time. It also means a wrong timeline writes markers into someone’s show with no undo, so the first thing to do on an unfamiliar desk is make an empty timeline and send to that.

Naming the console

Protocol Manager → Console Protocols → Avolites Titan.

Enter the console’s address and press Check connection. It reads the console’s own name back — if it says Connected to D92-00009, everything below will work.

That panel does one job. Which timeline each track writes to is decided in the send wizard, per track, from a list read off the desk.

Sending a set

Timeliner → Timecode & output → Send to Titan…

Four steps, because there are four questions.

1. Find the console

Find consoles asks every address on your own network who it is — a read, which is the only reason sweeping is acceptable at all. Or type the address if you know it.

2. Its timelines

Prismatik reads the console’s handle list and shows the timelines on it, each with where it physically sits:

WWT - TC                    RollerA p1.0 · #3
CAN'T LET YOU LEAVE - TC    RollerA p14.0 · #206
GOODBYE - TC                RollerB p1.0 · #4

The position is there because user numbers are arbitrary. On a real show the timelines on pages 1 to 12 carried 3, 2, 9, 12, 75, 76, 390, 77, 489, 1, 21, 70 — nothing you could guess or remember. RollerA p1.0 is where your hand goes.

Cue lists and chases are filtered out. If a console words things differently and nothing is recognised, tick Show every playback and pick by legend.

3. Link them up

Tracks are paired to timelines by name, using the same matching that recognises a re-delivered audio file — so a track called Mi Corazón finds a timeline legended MI CORAZON - TC, and a leading “The” is ignored.

On a real 39-track show against 41 console timelines it pairs 21 on its own, with none wrong. What it cannot pair is worth knowing, because it is not a fault to fix: console legends get abbreviated (WWT - TC for When We Touch) or truncated (HOW LOW - TC for How Low Can You Go). That is what the dropdown is for.

Your choices are remembered with the show, so the second send is one button. A link you set by hand always beats the name match — you chose it.

Anything left at — not sent — is skipped.

4. Send

One track at a time. A failure is reported against its track and the rest still go: a half-sent set with a named casualty is recoverable, one that stopped at track four silently is not.

What lands on the desk

Absolute timecode. A marker sent as 18:50:30:00 reads 18:50:30:00 on the timeline. Nothing is offset and nothing needs reconciling — what you sent is what the clock shows, so checking a cue is “we sent 18:50:00:00, it reads 18:50:00:00, there is a trigger on it”.

A Titan timeline can carry its own offset, but that does not move anything — it shows as a +1:00:00:03 reading when you open the timeline. Prismatik ignores it deliberately.

Every marker gets a legend. Auto-marked beats often have no label, so the layer name and position stand in (Strobe 12). A blank legend on a desk is a marker you cannot find again.

What it does not do

• Markers land on the timeline, not on tracks within it. The call takes no track, so layers arrive flat.
• It only adds and updates. Delete a marker in Prismatik, send again, and the console keeps the old one. The push is not a mirror, and says so.
• It does not create timelines. Make them on the desk first.
• It does not bind markers to cues. Markers are markers; triggers are a later job.

If a timeline was renamed

A timeline’s legend and its user number are both things you change while programming. Prismatik stores links against the console’s own internal id, which you cannot change, so a renumber does not silently redirect your markers.

If a linked timeline has been renamed or removed since you last sent, the wizard says so before sending rather than writing into whatever now answers to that number. It never guesses which timeline a renamed one meant to be — that guess is how a song’s markers end up on the wrong one.

Troubleshooting

“No answer — check the address, and that the WebAPI is enabled.” The console is not reachable on 4430. Check the address, the network, and that the WebAPI is switched on in Titan.

Nothing is listed as a timeline. Tick Show every playback. Every row shows Titan’s own type name, so you can still pick the right one.

Markers went to the wrong timeline. Re-link that track and send again — the ids mean the correct timeline updates in place. The wrong one keeps what it was given; remove those on the desk.

Some markers failed. The count and the first reason are reported. The push is idempotent, so re-sending is safe and only fixes what is missing.