Callaba

Matrox Maevex 7100 SRT setup with Callaba Gateway

May 14, 2026

Corrected exact-family setup guide

This guide covers the current Maevex 7100 contribution path. Maevex model numbers matter: 7112A is the AVC/H.264 encoder, 7112H adds HEVC/H.265, and 6152 is a decoder family with a different role. Confirm the exact chassis before applying any stream settings.

Choose the correct Matrox Maevex 7100 SRT setup with Callaba Gateway

PathOperational roleWhen to choose it
Maevex 7112A Single-channel 4K60 AVC/H.264 encoding, SRT transport and simultaneous recording. Choose for broad H.264 interoperability across existing players and distribution paths.
Maevex 7112H Single-channel 4K60 H.264 or HEVC/H.265 encoding with SRT over UDP. Choose H.265 only after every decoder, recorder and final destination has passed a compatibility test.
Maevex 6152 decoder A receiving/decoding device rather than the source encoder described by this setup. Use the Matrox family hub to choose a decoder or legacy workflow instead of following encoder steps blindly.

Keep the source, handoff and Callaba roles explicit

Source-side responsibility

Maevex captures HDMI video and audio, performs H.264 or H.265 hardware encoding, creates the SRT transport and can record locally or to supported storage.

Transport handoff

The handoff contract is exact model, firmware, source raster, codec, bitrate, audio, SRT role, UDP port, latency, Stream ID and encryption. Store credentials outside screenshots.

Callaba responsibility

Callaba provides the matching reachable endpoint, browser monitoring, transport statistics, cloud recording, playback, protocol routes and API-controlled operations.

Configure a Maevex 7100 contribution path

  1. 1. Read the model label and firmware version. Confirm 7112A or 7112H and avoid treating a 6152 decoder or an older 5100/6100 model as the same source device.
  2. 2. Connect the production HDMI source and confirm local pass-through, resolution, frame rate, color and audio before introducing the network.
  3. 3. Use the Maevex web UI or PowerStream Plus to create the stream. Select H.264 for maximum compatibility or H.265 only for a validated end-to-end HEVC path.
  4. 4. Create the corresponding Callaba endpoint. Match the documented SRT connection role, UDP port, Stream ID, encryption and recovery settings without publishing the generated URL.
  5. 5. Start the stream and inspect Maevex plus Callaba telemetry. Make a short Callaba recording, play it back and exercise the real downstream route before production sign-off.

Official references reviewed

Frequently asked questions

Which Maevex models does this setup cover?

The source workflow focuses on Maevex 7112A and 7112H encoders. A 6152 decoder or an older 5100/6100 device has a different role or transport matrix, so verify its exact product documentation before configuring Callaba.

Should I choose Maevex 7112A or 7112H?

Choose 7112A for AVC/H.264. Choose 7112H when HEVC/H.265 is required; it also supports H.264. Base the decision on the complete downstream codec chain rather than bandwidth alone.

Can Maevex send SRT to Callaba?

Current Maevex 7100 documentation lists SRT over UDP. Configure the connection role supported by the installed firmware and create the opposite peer in Callaba, then test through the actual firewall and NAT path.

Can Maevex and Callaba record simultaneously?

Maevex 7100 documentation includes simultaneous stream and record capabilities, while Callaba can record the received feed. Use both only when the operational requirement justifies two independent copies, and verify each artifact.

Does this setup apply to every Maevex 5100 or 6100 device?

No. Legacy encoders and decoders have model-specific codecs, transports and roles. Check the exact Matrox product page and use the family hub when the device is not a 7112A or 7112H.

Move from device choice to a tested receiving path

Launch Callaba on AWS · Run Callaba on your infrastructure