Fantago

Monitoring, Multiviewers & Master Control

Evertz QMC Master Control Software BETA

Evertz / Quartz QMC-MCS and QMC-2 master control switchers over the RCP-T37 automation protocol, directly over Ethernet or through a serial-to-Ethernet bridge. Transitions, crosspoints, keyers, DVE squeeze, logos, voice-overs, macros, and…

Handlers run inside Fantacore — the file is a plugin, not a standalone program. Start with the free 30-day trial.

How to connect Evertz QMC Master Control to Fantacore

  1. Open the Fantacore Dashboard and click Add Device.
  2. Pick the Evertz QMC Master Control handler from the device type list (internal id evertz_qmc).
  3. Enter the IP address of your Evertz QMC Master Control, then set protocol TCP and port 8003.
  4. Save and connect. Fantacore starts polling the device and publishes its feedback variables, ready to use in panels, sequences and logic flows.
  5. Drag the actions below onto a panel button, a Stream Deck key, a schedule or a logic flow node.
Evertz QMC Master Control handler specifications
ProtocolTCP
Default port8003
Handler version1.1.1
AuthorFantacore Bridge
Internal IDevertz_qmc

Description & Instruction

Evertz / Quartz QMC-MCS and QMC-2 master control switchers over the RCP-T37 automation protocol, directly over Ethernet or through a serial-to-Ethernet bridge. Transitions, crosspoints, keyers, DVE squeeze, logos, voice-overs, macros, and status read back as variables.
Setup: the QMC address and TCP port 8003 (or the bridge address and its own port). The automation port serves one client at a time: by default the connection is opened only for an action.

Command Integration Guide

The Evertz (Quartz) QMC-MCS and QMC-2 master control switchers are automated with the binary RCP-T37 protocol, derived from the GVG M-2100 automation interface. The handler talks to the QMC over TCP, either directly on its Ethernet port or through a serial-to-Ethernet bridge.

Connection

  • Direct Ethernet: enter the QMC address and TCP port 8003.
  • Through a serial bridge: connect it to the QMC automation port (RS-422, 38400 baud, 8 data bits, no parity, 1 stop bit; some QMC processor modules can be strapped for RS-232), set it to raw TCP server mode with no protocol added to the data, and enter the bridge address and its own TCP port.
  • The automation port serves one client at a time. While another program is connected (the station automation, a test tool), the QMC accepts Fantacore's TCP connection but answers nothing; while Fantacore is connected, the others get no answer. The Connection setting chooses:
    • On demand (default): connect for an action, disconnect 3 seconds after the last message. Variables are read once after each action.
    • Always connected: the handler keeps the port, reconnects every 5 seconds and reads the status continuously. Only when nothing else drives the QMC.
  • "Connected but no reply" (link = no_reply) almost always means another client holds the port.
  • Leave Connection is Persistent unchecked: the handler manages its own connection.
  • Automation must be enabled on the QMC. When it is disabled the QMC acknowledges commands without executing them: the handler reads this state and shows it in <prefix>automation.

How commands are sent

  • One sub-command per message, one message at a time: the next leaves only after the QMC answered the previous one. A NAK (refused command) is shown as an error with the QMC's reason (ERROR_STAT). ACK means received, not executed: with automation disabled the QMC acknowledges and does nothing.
  • A command that gets no reply is never sent again by the handler: it may have run.
  • A transition sends type, rate and levels one by one, then — once all were accepted and two frames have passed — TX_START. If any set-up step is refused, nothing starts.
  • The QMC clears the keyer presets (KEY_ENABLE) and the levels (TX_NEXT) after every transition. The default levels, "Background + preset keyers", add the keyers only when one was preset since the last transition, so a CUT never takes an on-air keyer (the logo) off by accident.
  • While a transition runs the QMC refuses set-up commands (preset source, levels): those return NAK.
  • All Stop stops the running transition only, unless a stronger option is chosen. The "Full reset" option puts crosspoint 1 — normally black — on air.

DVE squeeze

  • DVE: Squeeze runs a move (1-63, the moves stored on the QMC) on Program, only from full screen.
  • DVE: Return to Full Screen runs the same move again (a DVE move started twice reverses), waits for it to end, then takes the DVE level off air with a key-only transition, leaving the other keyers as they are.
  • The QMC's replies cannot tell "squeezed" from "full screen with the DVE level still on air". Using the two actions above keeps a known state: dve_move different from 0 means squeezed. DVE: Start Move (raw) sends a single DVE_START and loses that guarantee.

Variables

Read every second when always connected (Status read interval, 0 turns it off), after each action on demand; written only when they change:

  • pgm_source, pst_source: upstream router source on Program and Preset.
  • key1_onair…key4_onair, dve_onair, dve2_onair: true/false. key1_next… : the state after the next transition. key1_prv… : the keyer's preset as the QMC holds it (KEY_ENABLE), the PRV bank of the key bank actions.
  • in_transition (true/false), transition_video, transition_keyer, transition_audio: quiescent, preroll, transitional, fading_to_black, fading_from_black, in_black.
  • transition_type, transition_rate, transition_frames, next_background, next_key.
  • over_pgm, over_pst (off, over_1, over_2, both), over_ratio_pgm, over_ratio_pst (0-100).
  • dve_state (quiescent, moving), dve_move (move on Program, 0 = none), dve_squeezed (true/false).
  • logo, next_logo, automation (enabled/disabled), link (connected, idle, no_reply, disconnected), protocol_version, firmware_version.

All names start with the device prefix (e.g. qmc_pgm_source for a device named "QMC").

Notes from the protocol manual

  • Crosspoint commands act only when the QMC controls an upstream router. Sources are router numbers 1-240.
  • A crosspoint take clears the voice-overs: select them after the take.
  • A take on PGM is a hot cut, on air at once. Voice-over and ratio on PGM are on air at once too.
  • A logo not yet in the QMC's active memory is loaded only while its keyer is off air, and loading can take up to 30 seconds.

Evertz QMC Master Control control — frequently asked questions

Does Fantacore support Evertz QMC Master Control?

Yes. Fantacore includes a ready-made Evertz QMC Master Control handler (version 1.1.1) that talks to the device over TCP, default port 8003. It is bundled with every licence and with the 30-day free trial — there is no per-device fee.

What protocol does the Evertz QMC Master Control handler use?

TCP, default port 8003. Fantacore connects straight to the device over your production network, so no gateway, middleware or vendor software is needed in between.

Can I control Evertz QMC Master Control from a Stream Deck?

Yes. Every Evertz QMC Master Control action can be mapped to an Elgato Stream Deck key, to a button on a custom Fantacore touch panel, to a timed schedule, or to a logic flow triggered by another device — including devices from a different manufacturer.

Can I modify the Evertz QMC Master Control handler?

Yes. The handler is a plain JavaScript file (evertz_qmc.js) that you can download from this page, edit and drop back into Fantacore. You can also write your own handler from scratch — see the Developer Guide.

Control Evertz QMC Master Control from a single interface

Fantacore drives Evertz QMC Master Control alongside 50+ other broadcast, lighting, audio and smart home devices — from custom touch panels, an Elgato Stream Deck, a schedule or a logic flow. Runs offline.

Try free for 30 days Pricing

← All 56 device handlers