Cyanview’s camera remote control system offers several interface and license tiers depending on your workflow. Here we explain the differences between “CIO”, “RIO+LAN” and “RIO+WAN”, and the specific situations each one is designed for.
What is CIO?
CIO is an interface that connects serial-controlled cameras (compact cameras, most Sony camcorders, etc.) to an IP network. Beyond camera control, it also supports ENG/PL lenses, motor drives, and gimbals.
However, CIO is essentially a low-level converter for signal translation, and it does not communicate on its own. The actual control commands are sent from the RCP (Remote Control Panel).
What is RIO?
RIO is an interface with higher-level control protocols built in, allowing it to drive cameras directly. It runs the same software as the RCP and has a built-in CIO for serial ports, while also supporting camera control over USB, wired LAN, and WLAN.
Using RIO allows communication with the RCP over higher-latency networks such as cellular data or the public internet, making it well suited for remote production (REMI) and wireless setups.
Why RIO+LAN and RIO+WAN?
Equipment such as Sony camcorders and broadcast lenses can change settings or have the lens close if digital control is interrupted mid-operation. In a setup that pairs the RCP directly with a CIO, this kind of problem can occur the moment the switch connecting the two loses its connection.
By placing a RIO right next to the camera, the RIO can maintain the connection with the camera even if the connection to the RCP is briefly dropped. Even on a well-managed LAN, some devices are sensitive enough to require this kind of RIO-specific robustness.
To make this technology accessible to customers who don’t need remote production (REMI), RIO is offered in two license tiers depending on the use case.
RIO+LAN (formerly RIO-Live) vs RIO+WAN
| Item | RIO+LAN (formerly RIO-Live) | RIO+WAN |
|---|---|---|
| REMI (remote production) | Not supported | Supported |
| Camera count | Up to 2 | Unlimited |
| Typical use case | One-camera-plus-lens companion setup | REMI for a single camera, or REMI relay for a whole remote LAN of cameras |
| Price | Lower cost | Higher, reflecting REMI capability |
The “max 2 cameras” limit exists because RIO+LAN is designed to be the companion of “one camera plus one lens” — for example, an FX9 paired with a cine-servo lens.
RIO+WAN, on the other hand, allows a single RIO+WAN unit to remotely control a large number of IP cameras on the same LAN, as well as a large number of serial cameras connected through CIOs on that same LAN. The “unlimited cameras” characteristic is therefore designed around two main use cases:
- REMI for a single camera: mobile cameras, backpack units, drones, cable cameras, etc.
- REMI relay for a remote LAN: remotely controlling an entire group of cameras on a distant LAN through a single RIO+WAN unit
Configuration overview
Summary
| Interface / license | REMI (remote production) | Camera count | Typical use case |
|---|---|---|---|
| CIO | None (control data sent by RCP) | — | IP conversion for serial-controlled cameras and lenses |
| RIO+LAN (formerly RIO-Live) | Not supported | Up to 2 | Live production with one camera plus one lens |
| RIO+WAN | Supported | Unlimited | REMI for a single camera, or REMI relay for an entire remote LAN |