disguise GX 3 troubleshooting

Common GX 3 errors & problems

What techs run into most, and what's usually behind it. The step-by-step fix for your exact unit is in Ask Roadie.

• GX 3 connector reference for audio, MIDI, USB and networking when prepping a rack

  Likely cause: Most GX 3 prep failures are connector-family mismatches rather than faults, because the chassis uses circular multipin XLR, HD-BNC and Toslink instead of the full-size connectors crews expect.

  Step-by-step fixGet the fix →

• GX 3 does not appear in the d3Net session, or a machine shows red fps in the session list

  Likely cause: d3Net discovery depends on the launcher advertising the machine, so a machine with no launcher is invisible no matter how good the network is.

  Step-by-step fixGet the fix →

• GX 3 is dropping frames or playback stutters and you need to know whether the CPU or the GPU is the bottleneck

  Likely cause: A genlocked server has a hard per-frame deadline.

  Step-by-step fixGet the fix →

• GX 3 media output is black or the display is not detected on a VFC output

  Likely cause: EDID is the metadata handshake between the display and the GPU.

  Step-by-step fixGet the fix →

• GX 3 operating system is corrupted or the server needs a factory restore (Redisguise)

  Likely cause: The OS image is a clean factory build, so restoring it clears driver, Windows and Designer-install corruption in one pass.

  Step-by-step fixGet the fix →

• GX 3 outputs will not genlock, or genlock is unavailable across the three media outputs

  Likely cause: The GPU can only lock a set of outputs onto one timing domain if they all report the same display timings.

  Step-by-step fixGet the fix →

• How powerful is a GX 3 relative to other servers, and what is it the right tool for

  Likely cause: Notchmark score is the practical yardstick for real-time generative load, and the three 4K VFC media outputs are the hard ceiling on how much canvas one box can feed regardless of GPU headroom.

  Step-by-step fixGet the fix →

• Lighting console DMX over Art-Net or sACN is not reaching or not leaving the GX 3

  Likely cause: Art-Net and sACN are addressed by universe and interface, so a wrong start universe, a wrong bound interface, or two devices claiming the same addresses all present as no data or erratic data.

  Step-by-step fixGet the fix →

• Need to know how many layers a GX 3 can actually play back before designing a show file

  Likely cause: Designing to the published per-codec ceiling avoids building a file the server cannot sustain at frame rate.

  Step-by-step fixGet the fix →

• Racking, transporting or lifting a GX 3 safely

  Likely cause: A deep 4U server cantilevers on front ears alone and can shear them or sag; supporting the rear transfers the load into the rack frame.

  Step-by-step fixGet the fix →

• What video inputs and capture does a GX 3 have, and what do you need for clean IMAG capture

  Likely cause: HD-BNC is a smaller connector family than BNC, and 12G paths are far less tolerant of marginal cable, so connector and cable quality decide whether 4K locks.

  Step-by-step fixGet the fix →

• Which Designer software release should a GX 3 be running, and how do you update it

  Likely cause: Designer is the functional firmware of a disguise server, so the release number is what determines features, codec support and bug fixes.

  Step-by-step fixGet the fix →

Not on the list? Describe it your way, or paste the error code off the display. Ask Roadie works the problem with you until it's fixed or you have a clear next move.

More disguise gear

Other playback & media servers gear