Se rendre au contenu

Use case · House of worship

No dedicated shader. No mismatched stream.

Worship productions run on volunteers. PTZ cameras cover the room, a mirrorless adds the cinematic angle, and nobody sits on shading. The cameras still have to match every Sunday.

PTZ over IP + mirrorless, with a colour corrector / LUT Topology: Local Surface: Set-and-forget

The problem

What makes house of worship hard

Volunteers, not engineers

The crew changes weekly. Anything that needs a trained shader on duty will eventually go wrong.

PTZ and mirrorless disagree

Two camera generations, two colour sciences, one screen. The difference shows on every cut.

Stage lighting evolves

Worship lighting moves between songs and seasons. A one-time white balance does not hold.


Set once, let it run

Configure every camera once, store the look, and let the system hold it. The Multi-Cam Dashboard gives a browser grid of every camera for monitoring; touch up occasionally from the panel or leave it alone.

Set once, let it run

The colour layer does the matching

A colour corrector or 3D LUT box on the same control channel aligns the mirrorless to the PTZ fleet: real black, matrix and detail where the camera itself only offers exposure.

The colour layer does the matching

Map it onto your production

Cyanview and its integrators design the topology with you: cameras, interfaces, transport and the right control surface.

Talk to Cyanview Read the docs