HVS Camera System Architecture
Once a USB camera is connected, the data has several typical paths: "local processing / network streaming / multi-device sync / remote control". This page helps with selection; each capability's details are on its own page.
Data-path overview
Path 1: local processing
The camera connects directly to the host via USB3.0 and is processed in real time on the host:
- GUI preview and recording: MultiVision Studio
- C++ capture and secondary development: Hybrid Vision Toolkit + Hybrid Vision Algo
Path 2: network streaming
The camera itself acts as a sender, pushing the event stream in real time over TCP to receivers on the network (PC / server):
- EVS Network Server (TCP, default port 8888)
- The APS image stream can be pushed via RTSP (see the APS sender in Web Window)
Path 3: multi-device synchronization
When multiple cameras work together, a unified time baseline is needed:
- EVS Time Sync (UDP, default port 9999, microsecond-level): the first device to connect is the reference, and the others calibrate their timestamps by offset.
Path 4: remote control
Configure and control the camera remotely via a browser (PC / mobile):
- Web Window: HTTP access; can change network configuration, start/stop EVS/APS senders, and configure time sync.
Which capability to use
| Scenario | Recommended capability |
|---|---|
| Single-machine debugging, real-time view | MultiVision Studio (local) |
| Writing your own algorithm, product integration | Toolkit + Algo (local) |
| Streaming events to a server over a distance | EVS Network Server (TCP streaming) |
| Multi-camera time alignment | EVS Time Sync (UDP sync) |
| Phone / remote web control of the camera | Web Window (HTTP) |
Tips
For first use, start with USB Camera Quick Start.