Match=PTZ Try
The virtual CCU for PTZ
Match=PTZ

Match your cameras.

One look · every camera · one click

The color and framing control broadcast had with a CCU — now in software, for a whole studio of Sony PTZ cameras. No hardware rack.

PROGRAM · STUDIO 1 UNMATCHED
CAM 1
.11 · R+6 B−4
CAM 2
.12 · R−5 B+7
CAM 3
.20 · R+2 B+9
CAM 4
.21 · R+8 B−3
4 cameras, 4 different colors. Hit Match.
verified against hardware never invents VISCA commands zero runtime dependencies server-side permissions works offline
The problem

You moved to PTZ and lost the CCU.

Modern PTZ cameras (Sony BRC-H800 / X1000 and the like) brought flexibility and cut costs — but broke the CCU workflow that traditional broadcast took for granted.

Matching color went manual.

Camera by camera, digging through the OSD menu with a joystick. Slow, not repeatable, and overnight the look drifts.

A hardware CCU/RCP is expensive and per-camera.

It doesn't scale to a whole PTZ studio. You pay a panel per head.

Controllers remember position, not image.

Companion, vMix, NDI recall bring back the framing — but color is left to chance.

No real permissions.

Anyone on the network can touch any camera. Security lives in the UI, not the server.

No software CCU treats the whole look — color and framing — as a versionable, recallable memory with permissions, for an entire PTZ studio. That's MatchPTZ.

How it works

Save the look. Recall it by room.

MatchPTZ injects color (paint) and position over VISCA-over-IP. You build a "memory" that stores the exact state, group it into macros, and an operator recalls it with one click — verified against the camera, with real permissions.

01

Adjust

Fine paint and framing from the web console. With read-back: you see what each camera applied and what its firmware doesn't support.

02

Save

The exact color and position become an image memory — versionable, not a volatile preset.

03

Group

Memories combine into macros per control room. One button = the whole studio matched.

04

Recall

The operator recalls with one click, from their room, only over what they're allowed to. Audited.

CAM .20SET WB 6500K R_GAIN 0x8A→ ACK → COMPLETION ✓
CAM .20READ-BACK 051A.021052/52 params OK
CAM .11PAINT recall memory «Studio 1»→ COMPLETION ✓ · dedup
Why MatchPTZ

Four things, always true.

Everything below is demonstrable in the code or against real hardware. In a market tired of hype, that's the strongest card.

Repeatable look

The exact color and framing, saved as a memory, recalled with one click. No more matching cameras by hand.

Reliable on air

Verified against hardware, never invents commands, re-reads to confirm. Works offline. Doesn't drop the air.

Built for teams

Real permissions by room and role, server-side. An audit of who did what. The operator only touches what's theirs.

Light and unbound

Zero runtime dependencies, runs on your LAN, no mandatory cloud. Install in minutes.

Under the hood

Built like an instrument, not an app.

No magic, no cloud lock-in. A precise tool that talks to your cameras and proves what it did.

ProtocolVISCA-over-IP (UDP). Sony BRC-H800 / X1000, and growing.
VerificationRead-back per parameter. The console shows what each camera applied and what its firmware doesn't support.
RuntimeStandard Node, zero runtime dependencies. Runs on your LAN — bare metal or a VM.
AuthorityServer-side permissions by room and role. An audit log of every change.
MemoriesColor and framing saved as versionable memories, grouped into per-room macros, recalled in one click.
LicensingSigned offline license with Device-ID. Revalidates periodically — never blocks live operation.
IntegrationSits alongside Companion / Stream Deck. It owns color; they own triggering.
Competitive landscape

The only one that treats the whole look as a memory.

You don't compete with the hardware or with Companion: you replace them where needed and integrate where they add value. The defensible position is the workflow, not the control.

AlternativeWhat it doesWhere MatchPTZ wins
Sony hardware CCU / RCPReal paint controlPer-camera cost, doesn't scale to PTZ. Software for the whole studio.
OSD menu + joystickEverything, by handNot repeatable, slow, no permissions. You save and recall the exact look.
Companion / Stream DeckPreset / position recallDoesn't handle color as a memory or per-room permissions. You complement, not compete.
vMix / NDI PTZ controlFraming recallNo deep paint, no verification against hardware.
Manufacturer apps (PTZOptics…)Basic per-brand controlMulti-firmware, verified, with a permissions and audit model.
Who it's for

Same product, two doors.

Broadcast cares about on-air reliability and fine control; corporate/AV, about consistency and operational simplicity.

Broadcast · live TV

The right look, repeatable, with no menu time.

Daily shows where color has to be matched now. Multi-room, operator rotation, and nothing can drop the air. Fine paint control, verified against the camera.

The right look, one click — and if the internet drops, the air stays up.
Corporate · AV · events

Set it once, anyone recalls it right.

Hybrid rooms with several PTZ cameras that have to look consistent, run by techs with no camera training. Presets that "one day stop being right", solved as a memory.

Set it once. Without touching the camera menu.
The project

We didn't plan it as a business. We needed it.

MatchPTZ started in a control room full of PTZ cameras that wouldn't match — with the paint workflow that used to live in a CCU simply gone. The options on the market were a hardware panel per camera, or a joystick and patience. Neither scaled to a whole studio. So we built the tool we wished existed: one that stores the exact look — color and framing — and recalls it on command, verified against the camera.

What we ran into

PTZ cameras don't tell the truth about themselves. The same VISCA command lands differently across firmwares, some parameters are silently ignored, and a pan/tilt query can even come back a different length than the manual promises. The only honest way through was to measure every camera against real hardware, byte by byte, and read back what it actually applied. That slow, empirical work became the core of the product — and the reason it never bluffs on air.

Why we believe in it

Because no one else treats the whole look — color and framing — as a memory you can trust, for a full PTZ studio, without a hardware rack. Because it's honest: it shows what each camera did and admits what a firmware can't do. And because it stays out of the way when it counts — it never blocks live operation, and it works when the internet doesn't.

What's next

More cameras, more brands

Expanding multi-firmware support — more Sony models and other brands, each verified against real hardware, never assumed.

Control from tablet & phone

Operator recall from a tablet or phone — a match one tap away from the floor.

Plans

Start free. Scale when you go on air.

Offline licensing with Device-ID: authenticate once and it works without internet, revalidating every few days with prior notice. No manual keys.

Free
$0

To evaluate against your own hardware, no strings attached.

  • 1 device
  • Up to 2 cameras
  • Image memories and recall
  • Verifiable read-back
Download
Professional POPULAR
$10 USD / mo

For real production: multi-camera, per-room macros and teams.

  • 2 devices
  • Unlimited cameras
  • Macros and control rooms
  • Roles · audit trail
  • Offline operation
Try
Enterprise
Custom

For large, multi-studio operations with their own requirements.

  • Configurable devices
  • Multi-studio and multi-room
  • Advanced audit and roles
  • Onboarding and dedicated support
Talk to sales
Support

A person answers.

Small team, direct line. No ticket maze — you reach the people who built it and know your cameras.

Email
soporte@matchptz.com

We read every message. Expect a reply within one business day.

Match=PTZ

The CCU that PTZ never had.

Match the studio. Save the match. Recall it by room.