OTP and E1.59
ANSI E1.59, the Object Transform Protocol: a standards-track way to transmit object position, rotation and related transform data over IP.
What it is
The Object Transform Protocol, standardized as ANSI E1.59, transmits transform information about objects across an entertainment network: where something is, how it is rotated, and how those values are changing. Points are addressed hierarchically by system, group and point, so a consumer can subscribe to a defined slice rather than filtering an undifferentiated stream. The data is modular. A producer may transmit position, the derivatives of position, rotation and its derivatives, scale, and reference information relating one point to another, and a consumer must cope with modules that are simply absent. OTP also defines advertisement messages, so components can discover which systems, names and module types are present on the network rather than being told out of band.
Why it matters
OTP matters because it is an ESTA standard produced by the same process as E1.31, which means multi-vendor interoperability is a design goal rather than a byproduct of one company's ecosystem. Its discovery mechanism and named points also reduce the amount of undocumented convention a system depends on, which is exactly the material that decays across a long run and a changing crew. The honest caveat is adoption: what a standard permits and what is shipping in the firmware in your rack are different questions, and support varies by manufacturer and version. Design around the implementations you can verify in the room, and treat the standard as the thing that makes those implementations agree.
Addressing by system, group and point lets a consumer take a slice instead of the whole stream
Modules are optional; a producer may send position and no rotation, and consumers must handle absence gracefully
Advertisement messages give real discovery, including human-readable names for points
Being an ESTA standard makes multi-vendor interoperability a stated goal rather than a happy accident
Does OTP replace PSN or RTTrPM?
Not in itself. A standard replaces nothing until the products in the rack implement it, and support varies by manufacturer and firmware version. The practical position is to check what each producer and consumer in a specific system actually ships, and to design around the protocol that reaches every endpoint with the fewest translations. Where OTP is supported end to end, its addressing and discovery are genuine advantages.
Can OTP and sACN share a network?
Yes, and they are designed by the same body for the same environment. They still need the same discipline as any other multicast on the fabric: snooping with a working querier, deliberate decisions about which VLAN carries which traffic class, and verification of group membership under load. Sharing a fabric is a design decision with a bandwidth and fault-isolation cost, not a default.
What is the reference information for?
It lets a point be expressed relative to something else rather than only in absolute world terms, which is useful when an object moves within a structure that is itself moving. That is exactly the case that goes wrong in translation, because a consumer receiving only the resolved value has no way to know what it was relative to. Confirm what each consumer expects before relying on it.