VirtualVTR Pro - GPI Event Sequence

This page is a comprehensive description of what each specific preference in VirtualVTR and VirtualVTR Pro will do. It does not offer overall guidance on particular setups.

These parameters and functions are ONLY available in the VirtualVTR 'PRO' version of the software. Owners of the standard VirtualVTR software can order an upgrade to these facilities from Gallery.

GPI Event Sequence Introduction
VirtualVTR Pro offers synchronised streamers, beeps and also GPI event control for professional ADR and Foley. These are triggered by the VirtualVTR Pro sync point, which is described in the chapter about the Video streamers, in the section 'Marking a Sync Point'. The GPI events will send pre-defined midi messages out of a port in VirtualVTR and these messages are typically used to control relay closures for external hardware, using a device such as an R8 from Midi Solutions .The Beep parameters in this dialog are the same as those shown in the Overlay setup dialog.

GPI Events
VirtualVTR Pro features a highly flexible approach to GPI events. It offers user-scripted XML format files as programmable events to be triggered at certain points in the lead up and lead out of the synchronised event. Several example GPI XML scripts are provided, to show the syntax. Contact Gallery for more information on the syntax used. Effectively each XML script can trigger a whole sequence of timed midi messages. This allows you to do things like schedule a midi on and off message from a single GPI event point, with a preset time between the messages to allow the device to respond. This could be used, for example to trigger a beep from a sampler or other musical synthesizer, or to flash a light for short period
For example the following script sends a string of Midi Sysex Data 'F00000502600F7'

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Event Elements</key>
<array>
<dict>
<key>Element Delay</key>
<string>0</string>
<key>Element Data</key>
<string>F00000502600F7</string>
<key>Element Type</key>
<string>STATICMIDIEVENT</string>
</dict>
</array>
<key>Event Sequence Name</key>
<string>R8ClearSettings</string>
<key>Event Target</key>
<string>DEFAULT</string>
</dict>
</plist>

Most of the events are linked to a specific point in the synchronised event, for example to correspond with the beeps, or the sync point, or the record in our out time (when performing a manual punch in or out using a Shuttle Pro or MCS3). However there is also an event which is positioned specifically advanced from the sync point, by a user specified period. This is used to fire an external Video streamer box, which has a particular duration and which you want to END at the sync point.

Contact Gallery for more information on setting up GPI event sequences, writing XML scripts etc.

©2004 Gallery