User`s guide

Chapter 7: Configuration 51
Viz Video Hub
This section contains information on limitations of the Viz Video Hub and is still
valid for those that use Viz Video Hub. Viz One replaces the Viz Video Hub and
does not have the following limitations.
If you to transfer video clips from Viz Video Hub you can use the default vizroom1
profile, unless you configure a profile manually in Viz Video Hub. If you configure
a profile manually, the profile must be identical in the Viz Content Pilot client and
Viz Video Hub.
When configured to use video clips from Viz Video Hub it is required to use IP
addresses for both the Viz and video devices in order to visualize the transfer
progress correctly; hence, a hostname on the Viz device will work, but not when
configured to be used alongside a video device. Also, they must match the video
configuration for both program and preview.
See Also
• Forked Execution
7.2.3 Forked Execution
Forked execution can be used with standalone and transition logic scenes. It also
replaces the execution of visible containers.
This section contains information on the following topics:
• Standalone scenes
• Transition logic scenes
• Visible containers
Standalone scenes
Forked execution supports standalone scenes by executing the same graphics
with different concepts on two or more render engines. Concepts are defined per
channel in when
Working with the Profile Configuration tool.
As an option you can also use this setup to handle fail situations by having the
same graphics concept rendered on both engines.
Transition logic scenes
As with Standalone scenes, forked execution supports setting concepts for
Transition Logic scenes. In addition Transition Logic scenes, by defining channels
with different render engine setups, can show different states of the same scene
on a per engine basis. All states are synchronized for all engines (at all times) in
order to achieve an artifact-free and smooth morphing of the graphics from one
state to the other.