Tech Note: Christie Spyder x20 VI Vertical Pixel Threshold Still Functionality

There is a known issue with x20 hardware which limits how Still Layers can be used in certain High Rez setups.

When configuring a frame with a VI Vertical Pixel count above 1850 pixels in Height, the system becomes limited with how it can utilize Still Stored images.

Only layers 3,6,11, and 14 can be used as still layers.  Using other layers will induce strange behavior, including cropping, random noise, and other various errors when adjusting Keyframe parameters.  

This is a hardware limitation with all x20s and all versions of Vista Advanced.

TL;DR-Exact wording via Vista Systems:  "If the vertical height is higher than 1850 only layers 3,6,11,14 can load stills. This is a hardware limitation for any version software."

I have also heard people suggest this limit was at 1856 pixels.  YMMV.

Spyder Console Crashing with Gefen Pro DVI Matrix Router over IP

I ran across a frustrating bug when using a GefenPro as an external DVI Matrix Router with an x20 and an M2C-50 console.  

When going idle for an unknown period of time(more than 1 minute, less than 10), a bug occurs. Recalling Command keys works fine, but function keys cause the console to hang and then loses connectivity to the spyder. It then re-establishes a connection and fires all the buffered function keys sequentially.

When the console crashes it registers a Remote error in the Alert Viewer: "Telnet Socket Timed Out Waiting for Response".

Using the Gefen IV serial protocol in Spyder, I was able to get a stable connection.

To solve this issue use a serial connection from the Spyder frame to the Gefen Pro Router.  

IP control can 'time out' under certain circumstances intermittently.  

Vista(Christie) Matrix Router Compatibility Repository


Join me over at Github and lets solve the occasional headaches of Matrix Router Configurations with the Spyder.

The goal is to build a List of Video Matrix Routers compatible with the Vista(Christie) Spyder Switching Platform

Compatible Matrix Routers will be listed By Directory with Connection Settings config.txt and working, tested .vap configuration file

Router Test Process:

1. Factory reset the router to is default IP Address and/or Serial Port Configurations

2. Plug a reliable monitor into Output 1 of the router and 2 reliable sources as inputs 1 and 2

3. Switch the Output 1 between Inputs 1 and 2 on the router(either via front panel or other vendor specific operations) to ensure the router is in working order.

4. Open the Template .vap in Vista Advanced (Currently supporting 4.0.4)

5. Adjust the connection settings with the Appropriate Protocol and Add the router to the config.

6. Try a Query Router

5. Now perform a route using the RouterXY Patch Panel


Default Vista Advanced Configuration:

Version 4.0.4


4 Discreet 720@59.94 with Preview Mon on Output 8


Submissions should be forked in the Approved Directory and must include(see template):

Within a Directory labelled by Product-MaxtrixSize-Type   (ex.  Lightware-32x32-DVI, MatrixPro-8x8-SDI)

1. Working, configured Vista Advanced 4.0.4 .vap

2. Completed config.txt file template


If you are interested in working on this, let me know!




Request working Router configs by completing the template and commiting the submission to the Request Directory:

Within a Directory labelled by Product-MaxtrixSize-Type   (ex.  Lightware-32x32-DVI, MatrixPro-8x8-SDI)

1. The current router configuration Vista Advanced 4.0.4 .vap

2. Completed config.txt file template


Those with Request submissions can fork their solution, and when verified, I will merge the branch and move to Approved folder