The Virtual Extension provides visual feedback and touch-screen operation. It can be integrated into the frame or delivered as a stand-alone unit. If the Virtual Extension is integrated, then the VX module slots directly into the frame at a fixed viewing angle.
The functionality of the GUI is defined by the configuration. This chapter describe the standard configuration (included with every console). The operation may vary if the configuration is customized.
Prerequisites
The VX software runs on a Windows 64-bit PC that must be supplied by the customer. A license to run the standard configuration is included with every console.
It is expected that the customer has prepared and connected the host PC. How to do this is described in crystal - Configuring the Virtual Extension.
If the surface has more than one VX module, then all of the displays should be connected to the host PC and powered.
Starting the Software
The VX runtime app is started by double-clicking on the start script icon. This starts the Main and Fader sessions (according to the initial settings defined in VX Admin).
In each case, the session loads and connects to the hardware. Providing there are no error messages, the VX display is ready for operation.
If the display does not look operational, then try the troubleshooting tips in crystal - Powering On.
Session Mapping
Once the sessions are running and connected to the hardware, check the configuration of the 'Channel Strip' page.
The number of channel strips and master slots should match the controls on the surface modules. For crystal, there are two possible layouts: a Fader session (with 8 channel strips) or a Main session (with 6 channel strips plus 2 master slots).
If there is a mismatch, then correct the mapping of the sessions to the displays (using the "Screens" area in VX Admin).