Se rendre au contenu

Use case · College sports

Control every campus venue from one room.

Athletics departments stream dozens of events a week with student crews and tight budgets, and driving a truck to every gym does not scale. With REMI (remote camera control over IP), one room shades every venue on campus.

Mixed affordable bodies + PTZ, central hub Topology: REMI, combined Surface: Panel or software

The problem

What makes college sports hard

Many venues, small crew

Basketball, volleyball, soccer and softball overlap. Staffing a shader per venue is impossible.

Affordable cameras, mixed brands

The fleet grows camera by camera: PTZ here, mirrorless there. None of it matches out of the box.

Students rotate constantly

Every semester brings new operators. The system must be simpler than the org chart.


The REMI hub pattern

Put a RIO at each venue and give every device the same REMI tag. A single control room imports every camera as an ordinary numbered channel, wherever it sits on campus.

A Cyanview RIO at a campus venue sending camera control to a central control room over 4G

Size the surface to the show

Big matchups get a shader on an RCP. Routine streams run set-and-forget: configure once in the Multi-Cam Dashboard, monitor, and touch up only when needed.

A Cyanview RCP panel in the gallery shading multiple campus venues as numbered channels

The multi-venue rig

Venue A: RIO WAN + 4G routerVenue B: RIO WAN on venue LANTransport: REMI cloud, one shared tagSurface: RCP in the galleryBackup: RIO holds control if the link drops

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