Transition Logic is first and foremost a method of designing a graphics package that allows the designer to maintain the look and feel of the graphics while also allowing anyone else, such as journalists or producers, to add graphics items to a rundown without the need for any kind of technical knowledge of how the system works.
Transition Logic allows the independent control of any number of graphics layers, providing a code-free and design-based method for building graphics that gracefully animates in and out, and transitions from one to another automatically. This is accomplished by using a Master Scene which coordinates the animation of independently controlled objects which make up the whole. The master scene commonly contains the background items of the graphics package. Such items can be looping backgrounds or the design items of the lower third, over the shoulders, and full-screen graphics. The variable or changing content, such as the text in a lower third, is stored separately in Object Scenes.
A Transition Logic package consists of:
Part | What it is |
|---|---|
Master scene | The background scene that holds the logic. It stays loaded for the whole show. |
Layer | An independent slot of the master, for example Fullscreen, Lower or Bug. Technically a top-level container with a Toggle plugin and its own transition director. |
State | A named position of a layer. Every layer has the state O (Out: nothing on screen) and at least one on state, called IN by default. You can add more, for example TWO_LINES. |
Transition | The animation between two states. It is the stretch of the layer's director timeline between the stop markers of the two states. Logicmaker creates the transitions; designers animate them in the Stage. |
Object scene or Leaf scene (page) | A small scene holding the content of one layer in one state. This is what a control application takes. |
Out page | A leaf scene that takes a layer to O. Operators use it to clear the layer. |
When a lower third is played On Air, the object scene for the lower third is triggered. This tells Viz Engine to load the master scene, place the object scene inside the master, and animate the appropriate timeline(s). Thankfully, all of that is handled automatically, which is what makes Transition Logic so valuable.
How a take works.
When a control application (for example Viz Trio, Viz Pilot or Viz Mosart) takes a leaf scene, the scene's content is loaded into its layer and the layer animates to the leaf's state. Whatever was on that layer before animates out through its own transition. Layers that are not addressed stay untouched - that is the point of Transition Logic.
Under the hood: the Toggle plugin gives every layer two placeholder subcontainers named <Layer>,A and <Layer>,B. Takes alternate between them so the outgoing and incoming content can cross-fade, and four small helper directors (<Layer>,AX, ,AO, ,BX, ,BO) animate the placeholders during those cross-fades. Logicmaker creates and maintains all of this; you normally only meet it in the Stage tree and in the health check
Transition Logic scenes are designed with a built in logic that allows for morphing background graphics, handles multiple layers of graphics, and manages the transition from the graphic to graphic of each layer. The built in logic also minimizes the operator’s need to know how scenes affect each other, as the considerations of these various options are handled in the design phase. This ultimately results in a simplified work-flow and a look that is consistent and glitch-free.
To understand what Transition Logic is, one needs to understand a few basic concepts:
A Transition Logic scene is not a single scene, but a set of Viz graphics scenes that consist of a master scene that may have multiple layers of graphics that can be On Air at the same time and independently controlled.
Each layer in the master scene may have multiple referring object scenes. However, only one object scene per layer can be active at any given time.
Transition Logic layers are conceptual, not spatial.
Note: With Transition Logic scene design, take in and take out commands are still used as with standalone scene design. Where standalone scene design demands that only a single scene can be On Air at a time, however, Transition Logic allows for more than one scene to be On Air simultaneously. This means using Transition Logic allows a graphic covering the lower third of the screen, and another covering the left and/or the right side of the screen for over the shoulder graphics, to be On Air at the same time.
Transition Logic can be played out by most of Vizrt’s control applications such as Viz Trio, Viz Pilot and Viz Multichannel.
Architecture Overview
RENDERER└── MAIN_LAYER (master scene — always on-air) │ ├── Container "Banner" ← design elements (backplate) │ ├── Container "BannerLyr" ← Toggle plugin here │ │ ├── $current ← visible object scene │ │ │ └── $object │ │ └── $other ← next object (loading buffer) │ │ └── $object │ └── Container "BannerBackplate" ← animated rectangle │ ├── Container "OTS" │ ├── Container "OTSLyr" ← Toggle plugin here │ │ ├── $current │ │ └── $other │ └── Container "OTSBackplate" │ └── Container "Ticker" └── Container "TickerLyr" ← Toggle plugin here ├── $current └── $otherSTAGE (Directors)├── Director "BannerLyr" stops: $O ─── $LOWERTHIRD ─── $O│ ├── BannerLyr,AX (A-side cross-fade — 1s alpha dissolve)│ ├── BannerLyr,BX (B-side cross-fade — must mirror AX)│ ├── BannerLyr,AO (A-side object animation — auto-managed)│ └── BannerLyr,BO (B-side object animation — auto-managed)│├── Director "OTSLyr" stops: $O ─── $OTS_LEFT ─── $OTS_RIGHT ─── $O│ ├── OTSLyr,AX│ ├── OTSLyr,BX│ ├── OTSLyr,AO│ └── OTSLyr,BO│└── Director "TickerLyr" stops: $O ─── $TICKER ─── $O └── ...Each layer operates independently, taking Banner Off Air does not affect OTS or Viz Ticker.
$current and $other: Content is always loaded onto $other (invisible). Data is pushed via ControlObject. Then switch triggers the cross-fade: $current fades out, $other becomes $current and fades in. The viewer never sees a loading state.
The Take Lifecycle (TCP)
This is the complete sequence that newsroom applications (Viz Trio, Viz Pilot, Media Sequencer Engine) execute when an operator presses Take. Understanding this sequence is essential for automation integrators.
First Take: Layer Goes from $O to $IN
# 1. Ensure renderer is readyIS_RENDERER_READY# 2. Load master scene (only needed once per session)RENDERER*MAIN_LAYER SET_OBJECT SCENE*default# 3. Reset the layer's current placeholderRENDERER*MAIN_LAYER*TREE*$BannerLyr*FUNCTION*Toggle*reset_current INVOKE# 4. Load object scene into the invisible buffer ($other)RENDERER*MAIN_LAYER*TREE*$BannerLyr*FUNCTION*Toggle*object SET GEOM*News/LowerThird_Breaking# 5. Push data to the not-yet-visible sceneRENDERER*MAIN_LAYER*TREE*$BannerLyr$other$object*FUNCTION*ControlObject*in SET "ON 01 SET BREAKING NEWS"RENDERER*MAIN_LAYER*TREE*$BannerLyr$other$object*FUNCTION*ControlObject*in SET "ON 02 SET Details to follow"# 6. Animate in — GOTO_TRIO triggers the state transition + Toggle cross-fadeRENDERER*MAIN_LAYER*STAGE*DIRECTOR*BannerLyr GOTO_TRIO $O $LOWERTHIRDUpdate On Air (No Animation)
# Push new data to the currently visible sceneRENDERER*MAIN_LAYER*TREE*$BannerLyr$other$object*FUNCTION*ControlObject*in SET "ON 01 SET UPDATED HEADLINE"Swap: A/B Switch to a Different Template
# 1. Load a different object scene onto $otherRENDERER*MAIN_LAYER*TREE*$BannerLyr*FUNCTION*Toggle*object SET GEOM*News/LowerThird_TwoLine# 2. Push dataRENDERER*MAIN_LAYER*TREE*$BannerLyr$other$object*FUNCTION*ControlObject*in SET "ON 01 SET New Story"RENDERER*MAIN_LAYER*TREE*$BannerLyr$other$object*FUNCTION*ControlObject*in SET "ON 02 SET More details here"# 3. Cross-fade switch (old fades out, new fades in — same state)RENDERER*MAIN_LAYER*TREE*$BannerLyr*FUNCTION*Toggle*switch INVOKETake Out: Layer Goes from $IN to $O
# Animate out — backplate reverses, Toggle cross-fades object outRENDERER*MAIN_LAYER*STAGE*DIRECTOR*BannerLyr GOTO_TRIO $LOWERTHIRD $OMulti-Layer Concurrent Operation
All layers operate independently. You can take Banner in, then take OTS in, then take Banner out while OTS remains unaffected:
# Take Banner inRENDERER*MAIN_LAYER*TREE*$BannerLyr*FUNCTION*Toggle*reset_current INVOKERENDERER*MAIN_LAYER*TREE*$BannerLyr*FUNCTION*Toggle*object SET GEOM*News/BreakingRENDERER*MAIN_LAYER*TREE*$BannerLyr$other$object*FUNCTION*ControlObject*in SET "ON 01 SET Headline"RENDERER*MAIN_LAYER*STAGE*DIRECTOR*BannerLyr GOTO_TRIO $O $LOWERTHIRD# Take OTS in (while Banner is on-air)RENDERER*MAIN_LAYER*TREE*$OTSLyr*FUNCTION*Toggle*reset_current INVOKERENDERER*MAIN_LAYER*TREE*$OTSLyr*FUNCTION*Toggle*object SET GEOM*News/OTS_GraphicRENDERER*MAIN_LAYER*TREE*$OTSLyr$other$object*FUNCTION*ControlObject*in SET "ON 01 SET Expert Name"RENDERER*MAIN_LAYER*STAGE*DIRECTOR*OTSLyr GOTO_TRIO $O $OTS_LEFT# Take Banner out (OTS stays on-air)RENDERER*MAIN_LAYER*STAGE*DIRECTOR*BannerLyr GOTO_TRIO $LOWERTHIRD $OSession Cleanup
# Full cleanup sequence — frees all cached resourcesSCENE CLEANUPGEOM CLEANUPIMAGE CLEANUPFONT CLEANUPMATERIAL CLEANUPMAPS CACHE CLEANUPREND SET_OBJECTPOOLS CLEANUPThis section contains information on the following topics: