User guide

Viz Engine Administrator’s Guide
Copyright © 2014 Vizrt Page 145
10 Frame Accurate Output
At the moment the frame accurate commands only work with DVE as clip target. Due
to different usage of the ring buffer (another place in the timeline) the texture target is
not working.
This section contains information on the following topics:
• Prerequisites
• Configuring Frame Accurate Output
• Commands
10.1 Prerequisites
To make sure clip handling is fast the system has to be configured to use a RAID-0 hard
disc configuration. Also it is best to use a Matrox X.mio2 or X.mio2 Plus rather than an
X.mio because of the increased memory usage and performance required.
If the system is fitted with an X.mio you could increase the performance by setting the
used RGB to YUV conversion to Shader (see Render Options). For further details, see
the Configuring Frame Accurate Output section.
As all of the clip players are initialized at first usage it is necessary to do so prior to
starting a frame accurate scene. Do this by loading a dummy scene that has all clip
channels set to either DVE or texture mode and a valid clip name given.
Note: It can take up to 4 seconds for the clip players to initialize. Do this a second
time to also initialize the pending clip players. Please keep in mind that this
procedure is only needed after a fresh restart of the Viz Engine/Artist.
See Also
• Configuring Frame Accurate Output
• Render Options
• Shader definition
10.2 Configuring Frame Accurate Output
To configure frame accurate output
1. Start Viz Config
2. Select the Communication section and enable Frame Accurate Viz
Communication
3. Set FAVC Bias as needed
• Delay fields (in addition to ring buffer size) for frame accurate commands via
TCP or GPI. This is the bias in frames for the commands if Frame Accurate Viz
Command is turned on. Could be negative as well.
4. Set FAVC Field Dominance to Odd Retrace Counter