RoomScene 3D
Download

TSL UMD 3.1 vs 5.0: how the tally protocol works

TSL UMD is how most vision mixers, routers and tally controllers tell multiviewers and under-monitor displays what to show and which source is live. Two versions are in common use, and they are different enough that a receiver has to handle both.

Published

What TSL UMD carries

A UMD is the label under a monitor: “CAM 3”, “VT 2”, “GFX”. A tally is the red or green lamp next to it, or around the tile on a multiviewer. TSL UMD is the protocol that sets both. The sender is the device that knows what is on air: the vision mixer, a router, or a tally controller that combines several of them. The receivers are multiviewers, UMD displays, tally interfaces in the camera chain and, increasingly, software that wants to know what is live.

The protocol is one-way in practice. The sender pushes the state of each display; the receiver applies it. There is no handshake about what a tally means. Tally 1 is program because everyone in the building agreed it is.

TSL UMD 3.1

Version 3.1 started on serial lines, RS-422 or RS-485, with displays daisy-chained on one bus. It is now carried over UDP far more often than over serial, but the message has not changed. Every message is exactly 18 bytes:

Byte    Field     Content
0       HEADER    0x80 + display address (address 0–126)
1       CONTROL   bit 0     tally 1
                  bit 1     tally 2
                  bit 2     tally 3
                  bit 3     tally 4
                  bits 4–5  brightness
                  bit 6     cleared
                  bit 7     0
2–17    TEXT      16 bytes of ASCII display text

Each tally is a single bit: on or off. There is no colour in the message. What tally 1 and tally 2 mean is set by convention and by the configuration at each end. The common arrangement is tally 1 for program (red) and tally 2 for preview (green), with tallies 3 and 4 left to whatever the site decides.

As an example, camera 3 on address 3, on program, with both brightness bits set:

83          header: 0x80 + 3
31          control: brightness bits 4–5 set, tally 1 on
43 41 4D 20 33 20 20 20 20 20 20 20 20 20 20 20
            text: "CAM 3" padded with spaces to 16 bytes

The limits are visible in the layout. Addresses stop at 126. Text is 16 ASCII characters, so non-Latin labels are out. And because the header byte has its top bit set and the others do not, a receiver can find the start of a message in a serial stream, which is why the format looks the way it does.

TSL UMD 4.0, briefly

Version 4.0 extends 3.1 with a checksum and colour tally information. It is less common in the field. Most equipment offers 3.1 and 5.0, and most receivers are built around those two.

TSL UMD 5.0

Version 5.0 was designed for IP from the start, over UDP or TCP. It drops the fixed message in favour of a packet that can carry several displays, more than one screen, longer text and Unicode. All multi-byte values are little-endian.

Offset  Size  Field    Content
0       2     PBC      packet byte count
2       1     VER      minor version
3       1     FLAGS    bit 0: text is UTF-16LE
                       bit 1: screen control data
4       2     SCREEN   screen index
6       ...   one or more display messages:

  +0    2     INDEX    display index
  +2    2     CONTROL  bits 0–1   right-hand tally
                       bits 2–3   text tally
                       bits 4–5   left-hand tally
                       bits 6–7   brightness
                       bit 15     control data, not display data
  +4    2     LENGTH   length of the text
  +6    n     TEXT     display text

There are three tallies per display, named by where they appear on a UMD or multiviewer tile: left, right and the text itself. Each is two bits, so it carries a colour, not just on or off:

ValueBitsTally
000Off
101Red
210Green
311Amber

As an example, a CONTROL value with the text tally red and both brightness bits set is 0x00C4, which goes on the wire as C4 00.

Over UDP one datagram is one packet. Over TCP there are no datagram boundaries, so each packet is wrapped: it starts with DLE/STX, the bytes 0xFE 0x02, and any 0xFE inside the packet is sent twice. A receiver that sees FE 02 knows a packet starts; one that sees FE FE takes it as a single FE byte. A packet is at most 2048 bytes.

3.1 and 5.0 side by side

TSL UMD 3.1TSL UMD 5.0
OriginSerial RS-422/RS-485, now mostly UDPDesigned for IP, UDP or TCP
MessageFixed 18 bytes, one displayVariable packet, one or more displays, up to 2048 bytes
Addresses0–12616-bit display index, plus a screen index
Tallies4, on/off3 per display, each off/red/green/amber
Meaning of a tallyBy convention: commonly 1 = program, 2 = previewColour carried in the message
Text16 ASCII charactersVariable length, ASCII or UTF-16LE
Message startHeader byte with the top bit set (0x80 + address)PBC at the start of each packet; DLE/STX (0xFE 0x02) on TCP

Setting it up in a facility

There is no single official port for TSL. Each sender and receiver has its own setting, and the defaults differ between manufacturers. Write down the port with the destination and do not rely on anyone remembering it.

Most broadcast vision mixers, routers and tally controllers can send TSL to several destinations at once, and on many of them the version is set per destination. The multiviewer may want 5.0 while an older UMD controller still wants 3.1. That is normal; configure each destination for what its receiver understands.

  • UDP or TCP. UDP is simple, has no connection to maintain and is what most installations use. Its weakness is loss: if a sender only transmits on change, a dropped datagram leaves a lamp wrong until the next cut. TCP delivers every packet but needs a connection, so check which side opens it and what happens when it drops.
  • VLANs and firewalls. Mixers often live on a production VLAN, receivers elsewhere. The firewall between them has to pass the TSL port, for UDP, and for TCP if you use it. A firewall that silently drops UDP is the most common reason a new tally destination “does nothing”.
  • Addresses and cameras. The address on the wire is not the camera number. Address 1 might be CAM 1 in studio A and also the first input on a second mixer that drives studio B. Map each address to a physical camera, per sender.
  • Labels. The UMD text is a useful cross-check, but it is set by whoever configured the mixer and can change between shows. Map by address, verify by label.

Keep an address map as a living document, next to the camera list:

SenderVersionAddressLabel on wireCamera
Mixer A5.01CAM 1Studio A, pedestal 1
Mixer A5.02CAM 2Studio A, pedestal 2
Mixer A5.05JIBStudio A, jib
Tally router3.117B-CAM1Studio B, pedestal 1

Reading TSL in RoomScene 3D

RoomScene 3D uses TSL to show tally on the cameras in a 3D model of the studio, so the engineer in MCR or the person about to reboot a CCU can see which camera is live. It listens for 3.1 and 5.0 on the same port, over UDP and TCP, 8900 by default, and detects the version from each packet. The DLE/STX framing of 5.0 over TCP is handled. For 3.1, tally 1 is program and tally 2 is preview. For 5.0, red or amber is program and green is preview.

Incoming sources are listed live in Settings › Tally with their address and label, which makes building the address map above a matter of watching the list while the director cuts. Map each address to a camera there or on the camera's card. It is listen-only: nothing is sent back to the mixer, and it does not replace your tally system. Add the RoomScene 3D server as one more TSL destination on the mixer or tally router. The same camera keeps showing its monitoring status from Zabbix or the built-in check, so a CCU fault and an on-air tally appear in one place.

The tally page has the setup steps. For the cabling side of a studio, see patch panel and cable documentation. The 30-day trial includes tally; point a spare mixer output at it and watch the sources appear.

Try it on your own rooms

RoomScene 3D is a 30-day trial with every feature on. Install it on a test server and import one room.

Download the 30-day trial Ask for a quote

contact@roomscene3d.com · tahirfeyzioglu@gmail.com