Disguise vx 2
Disguise vx 2: VFC outputs, SDI inputs and latency
Plan content and signal paths with vx 2: variant, VFC, capture, project and destinations. Ask GLMedia about rental or purchase, preparation and operation.
Model and role
To evaluate a server, start with the images required at each destination and the intended live sources. GLMedia can help turn that layout into equipment and operation requirements, with rehearsal for the actual project.
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.
Show use and alternatives
For panoramic video or mapped destinations, we can review vx 2 against the project, sources and installed configuration. When material arrives from another production team, check versions and media before setup. We can evaluate compatible preparation, adapted content delivery or another server if the project requires a different platform; the equipment name does not settle that decision.
If the project is not available yet, describe the screens and how content will arrive. Once available, we review a copy, the exact version, media, and installed modules to scope adaptation, testing, and operation. There is no need to select an upgrade before identifying the show requirements.
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.
Separate file playback, live capture and distribution to each destination in the inquiry. Identify who supplies the project, media and compatible license, and the available rehearsal time. If a variant or module remains unidentified, retain that uncertainty when comparing alternatives; the proposal should specify the configuration offered.
Prepare the system
- Record the server, backplane, VFC, capture card, Designer build and OS image. The official compatibility matrix 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.
Use and troubleshooting questions
- The control display works, but the show screens are black. What should I verify?
- Can a 12G-SDI source be connected to any HD-BNC input?
- Does the published low-latency figure guarantee the camera-to-screen delay?
- We received a project from a newer version. How do we choose a show playback solution?
- Does a project copy on another server already provide VX 2 backup?
The control display works, but the show screens are black. What should I verify?
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.
In rehearsal, separately test an image labeled by destination and the complete cue. This distinguishes connection, assignment and project load and helps define preparation or conversion in the proposal.
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.
We received a project from a newer version. How do we choose a show playback solution?
Record the exact build and preserve the original project. The official matrix does not enable the latest Designer on VX 2; possession of a file does not establish that the server can open and run it correctly.
We can evaluate a compatible project version with the content team, exported media for another workflow or a server suited to the required version. Confirm the selected option in a pre-show test and, if adaptation or a version change is needed, prepare it with the content team before setup.
Does a project copy on another server already provide VX 2 backup?
d3Net documentation requires distributing the project and required media and defining machine roles. A project copy alone does not establish available content, output assignment, or a prepared recovery path.
We can evaluate a compatible backup server or simplified playback path according to which destinations must continue. For a quote, identify critical signals and cues and the expected recovery; then verify version, files, modules, and connections on the actual system. Rehearsal should check destination picture and audio, not just whether the project opens.
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.
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
- Failover: Understudy availability, roles, feeds and matrix routing
- Legacy d3Net setup: Understudies, targets and file distribution
VX 2 documentation: model guide, compatibility matrix and conditions of the manufacturer’s published tests. Match the installed backplane, VFC and capture configuration to the proposed connection.
Project received from another production
Show scenario
A supplier delivers a project, but opening it and reaching the show screens are not yet confirmed.
A solution we can quote
We can review the software version, media, modules, output assignments and operation, and agree with the project author on the adaptations and corrections needed.
Another option to compare
If interactive functions are not required, compare two options: a project adapted by its author to compatible software, or rendered files for simpler playback.
Proposed acceptance check
Work on a preserved copy; open and run critical cues on the event unit, check missing media, and verify each output at its destination. Log the approved version.
To prepare a proposal
Share the originating version, file list, and screen description; a preliminary handoff helps identify open items.
Does updating to the latest Designer solve the handoff?
No. VX 2 has a published compatibility limit; check versions before planning an adaptation.
Does copying the project create a ready second system?
No: media, configuration, and routes must also be available; review backup as another system.
Manufacturer documentation
Help us improve this guide
Is an explanation missing, did you find an error, or did you solve something differently? Tell us on WhatsApp.
WhatsApp opens with an editable draft. Review it and send it if you choose. Do not include passwords, keys or client information. Contributions are reviewed before being added to guides; they are not published automatically.