Recording

Create a clip with just video. Viz program output resolution is set to 576i25.

• We start with flushing the channel, CONTROL FLUSH, to have a clean state.

• Then we tell the clip channel to create the video file, VIDEO_SET 1.

• The clip resolution should match the output resolution, RESOLUTION VIDEO_SET 0 0.

• Container is .avi, CONTAINER VIDEO_SET AVI.

• And codec is dvcpro411, CODEC VIDEO_SET DvCPro_411 the codec requires no further options .

• Open the clip with NAME SET v:/clips/sample.

• And record 100 frames, CONTROL RECORD 100 wait until all frames have been recorded.

• Close the clip, CONTROL FLUSH.

• The resulting is a clip v:\clips\sample.avi.

Advanced Recording

Create a downscaled clip with video, separate key, audio, VBI and proxy. Viz Engine program output resolution is set to 1080i25.

• Start with flushing the channel, CONTROL FLUSH, to have a clean state.

• Tell the clip channel to create the video, key, audio, VBI and proxy files:

  • VIDEO_SET 1

  • KEY_SET 1

  • AUDIO_SET 1

  • VBI_SET 1

  • PROXY_SET 1

• The resolution should be SD 16:9, RESOLUTION VIDEO_SET 2 0.

• The video and key files should be D10 files.

  • CONTAINER VIDEO_SET XDCAM_MXF

  • CODEC VIDEO_SET 27

• Since we want separate audio we need to specify the audio container, CONTAINER AUDIO_SET W64.

• Same applies for VBI:

  • CONTAINER VBI_SET AVI

  • CODEC VBI_SET YUYV422

• Set the D10 Iframe options, OPTION VIDEO_SET IFRAME bitrate=30 forceDCTFrame=0.

• Audio configuration, OPTION VIDEO_SET AUDIO ch=8 bits=24/32.

• And VBI configuration, OPTION VIDEO_SET VBI ON.

• The MXF file allows to carry time code information, OPTION VIDEO_SETTCstartTC=11:00:00:00.

This finishes setup of the hires part, next is the proxy configuration.

• The proxy should be scaled to 50%, RESOLUTION PROXY_SET 0 50.

• Container is QT mov, CONTAINER PROXY_SET QT_MOV.

• Codec needs to be set to uncompressed, CODEC PROXY_SET YUYV422.

• Audio should be included in the proxy, too, OPTION PROXY_SET AUDIO ON.

Before we can setup the proxy QT options we need to open the clips:

• Open the clip, NAME SET v:/clips/advanced.

• Then set the proxy QT codec, OPTION PROXY_SET QTCODEC SVQ3.

• And the proxy QT options, OPTION PROXY_SET QTVIDEO average_data_rate=0 quality=512.

• Record some frames, CONTROL RECORD 1000 and wait until they are recorded.

• Close the clip, CONTROL FLUSH.

  The resulting clips are:

  • v:\clips\advanced.d10.mxf (SD 576i with fill)

  • v:\clips\advanced_key.d10.mxf (SD 576i with key)

  • v:\clips\advanced_vbi.avi (HD1080i with VBI)

  • v:\clips\advanced_proxy.mov (proxy with video and audio)

Create Clips with Stage Events Example

This example creates a reference clip and uses stage events to start the recording. It contains various counters and a timecode. It has the capability for audio and video as well. Let’s take a look at each step involved first.

Enable Feedback

At first we enable the feedback channel to send UDP packets to localhost. Now we are ready to initialize the clip channels and the renderer:

Cleanup Clip Out and Clip In Channels

Flush any clips in the clip in and clip out channel. Since the flush command needs to travel through the ringbuffer we need to wait a few frames until they have been executed.

Cleanup Renderer

Unload scenes from the renderer and cleanup all pools. We want to start with a fresh environment here.

Set Up Stage Start Event

Enable the Stage Start event to trigger the record command on the clip out channel.

Load Scenes And Set Audio And Video Clips

This loads the background scene, and sets the audio clip and the video clip. The scene for the main layer is also loaded here.

Cue Scenes

Both scenes are cued. This is required for frame accurate clip playback.

Load Scenes Into Renderer

The scenes are loaded into the back layer and main layer.

Reset Animation Timelines

The timelines for back and main layers are reset to zero. Now we are ready to configure the clip out channel.

Configure Clip Out Channel

The first line sets a text container in the main layer with some descriptive information. The following lines configure the clip out channel and on the last line open the clip.

Start The Animation

This starts the animation on both layers. The stage start event trigger fires and the recording starts.

Close Clip

After the recording of the predetermined number of frames has been finished (can be observed on the feedback channel) we close the clip:

We have now recorded a clip with 5000 frames in XDCAMHD422 format in an MXF container.

Render a Playlist

Recent additions to Viz Artist ease rendering a complete playlist into separate clips. This example guides through those new features. First we need to prepare some steps in the configuration file.

Default Profile

First, we create default profile that we can load with a single command. In This profile we make use of the placeholders for the name of the clip. This is under the section CHANNELS_CONFIG in the configuration file.

Scene Load Interceptor

The profile that we created in the previous section should always be applied when we change the scene. To be more specific we want it to be applied right before when a scene gets loaded into the render editor but before it is actually loaded. We make use of the command injector on the scene load interceptor on the MAIN_LAYER.

Stage Interceptors

The Stage events have been already introduced above. Here we make use of them again but this time bound only onto the MAIN_LAYER. When the animation starts then an infinite record command is set to the clip out channel. When the animation stops the clip is flushed and hence properly closed.

Startup Commands

The Interceptors are not part of a scene or the configuration file. They need to be applied once. So we just bundle them together in the startup commands section together with the activation of the feedback channel. The feedback channel commands make only sense if the controlling application resides on the localhost. Otherwise, replace localhost with the name of the host where the UDP feedback should be directed at or leave them out of the startup commands.

Ready to Render The Playlist

Load the scenes into Viz Engine and cue them.

After that the scenes are ready to be put into the render editor. Now let’s set the placeholder for the clipname and render the first clip.

This triggers the scene load command injector that executes the RENDERER*VIDEO*CLIPOUT*1*PROFILE APPLY which in turn loads the profile and applies it to the clip out channel.

assuming that is set v:/clips/out/, then the clip name is expanded to v:/clips/out/playlist/n1/heidi_1.xdcamHD422.mxf. The next step is to start the animation. This triggers the stage start command injector.

Which, in turn, triggers the stage start command injector.

Now the controlling application watches the feedback channel it subscribed to before:

as we can see in the feedback messages there are also STOP and FLUSH commands. Once the animation stops the stage stop command injector kicks in.

This command stops and flushes the clip. Now we can repeat with rendering the next clip until the playlist is completed.