Disguise vx 2
Disguise vx 2: VFC outputs, SDI inputs and latency
Ask GLMedia about rental options for content playback and presentations. We review availability, configuration, and alternatives for your event.
Model and role
With the date, location, and intended use, we can review which equipment and combination can be offered. You can inquire before measurements, drawings, or the final schedule are ready.
The Disguise vx 2 is a legacy media server for show playback, mapped outputs and live SDI capture. Use it with an identified project, source plan and destination map. It is a different model from VX 2+; their specifications and software requirements must be kept separate.
Record the backplane version, fitted VFC types and capture-card model without opening the chassis. The guide distinguishes GUI connections by backplane version, and software compatibility explicitly distinguishes servers fitted with Matrox capture.
Connections and limits
- GUI and show outputs
- Separate GUI: DisplayPort 1.4 with backplane version 2, or DisplayPort 1.2 with version 1. Show: 2 outputs up to 4K through fitted VFC cards; connector and supported timing depend on those cards.
- Live capture
- Documented limit: 2 × 2160p60 or 8 × 1080p60, not both maxima added together. The input guide lists 12G-SDI and 3G-SDI on HD-BNC, with 10-bit YCbCr 4:2:2 formats. Check the installed capture configuration and input-group diagram.
- Network and sync
- 1 × 1GbE, 2 × 10GbE, 2 × 25GbE SFP28 ports, a separate management Ethernet port and BNC Genlock. Assign each role explicitly; an SFP28 port alone does not establish a video-over-IP workflow.
- Power and rack
- The current specification states AC 115–240 V, 50–60 Hz and 374 W peak, with powerCON TRUE1. 4U, 19-inch rack; operation at 5–35°C. Check the actual unit label before planning the supply.
What the system needs
Identified VFC and capture configuration, GUI display and peripherals, compatible signal cables/conversion, a saved project and real show media. For a live camera path, agree on the complete acceptable delay and how it will be measured.
Match source raster, frame rate, SDI link format and sync to the actual processor/display path. Keep a separately rehearsed fallback and independent media/project backup.
Prepare the system
- Record the server, backplane, VFC, capture card, Designer build and OS image. The reviewed compatibility table lists VX 2 as End of Support, with support up to r32.4.x; initial support is r17.4 or r20.1 when Matrox capture is installed. Do not apply a VX 2+ OS image by similarity.
- Connect the GUI and each show destination to their assigned ports. Check VFC type, output assignment and the receiving device’s format before building the complete cue.
- Verify one supported SDI source before adding the remaining inputs. With quad-link capture, match square division or 2SI and the complete link grouping; with single-link 12G, use only the ports identified for that capture configuration.
- Rehearse actual media, effects, live sources and outputs. Measure camera-to-screen delay separately from media playback; keep the tested settings and verify the fallback.
Operating questions
The GUI is visible, but a show screen is black. Which output should I check?
The GUI is a separate interface connection. Verify the physical VFC slot, destination input, cable/conversion and project output assignment. The GUI DisplayPort version depends on the backplane and does not identify the fitted show VFC.
In rehearsal, preserve the starting settings and test a simple labeled image at a format supported by both the VFC and destination. Substitute one known compatible lead if necessary before changing hardware or firmware.
Can a 12G-SDI source be connected to any HD-BNC input?
No. HD-BNC describes the connector, not the bandwidth of every input. The published 12G-capable input diagram marks A and E as 12G; compare it with the installed capture card before using that mapping. Do not infer 12G capability on the other connectors.
Confirm the source raster/frame rate, link mode and cable/conversion capability. Test one source on an applicable input first. Respect the simultaneous limit of 2 × 2160p60 or 8 × 1080p60; preserve the project before changing capture assignments.
Does the published low-latency figure guarantee the camera-to-screen delay?
No. The VX 2 page reports capture-to-output results for Normal, Low Latency and Ultra-Low Latency modes. It does not measure the camera, external converters, LED processor and display in your route. The playback benchmark also uses an Actor with GUI disabled and a dedicated Director.
Define the intended signal format and supported mode, then measure the complete route in rehearsal. Compare a simple path with the real show load and record the result. Do not promise a layer count or end-to-end delay from a benchmark alone.
Symptom and next check
| Symptom | Check | Next step |
|---|---|---|
| GUI works, show is black | VFC slot, format and assignment | Test the actual show route. |
| 12G source absent | Capture version, applicable input and source mode | Test one supported source and link. |
| Camera image is late | Complete camera/conversion/processing/display path | Measure the actual route in rehearsal. |
Power, environment and installation
Keep cooling clear, prevent condensation and use appropriate rack support and grounded power. Have the responsible technician check the exact unit and distribution ratings.
The official overview requires instruction from a certified engineer before opening or removing the case. Do not swap internal cards, restore the OS or update drivers as generic troubleshooting.
This guide does not establish measured performance, installed firmware, inventory or availability.
Manufacturer documentation
- VX 2 overview and service restriction
- VX 2 specifications
- VX 2 capture formats and input diagram
- Product/software compatibility
- VX 2 performance and test conditions
- VX 2 official diagrams
- VFC output documentation
Reviewed October 22, 2026. Official online VX 2 guide, compatibility matrix and model-specific performance page. Installed backplane, VFC and capture versions must match the proposed connection.