The architecture problem
Most professional AV-over-IP systems are not single products. They are stacks of products. An integrator building a 16-node hospital AV installation typically specifies:
- An encoder for each source (16 units)
- A decoder for each display (16 units)
- A separate control processor (1 unit)
- A separate recording server (1-2 units)
- A separate video wall processor (1-2 units, if a video wall is in scope)
- A separate audio DSP (1 unit)
- A network switch with multicast support (1 unit)
- A management server for the control platform (1 unit)
That is a lot of boxes. Each one is a separate vendor SKU, a separate firmware update cycle, a separate warranty, a separate point of failure. The integrator spends days integrating them and writing glue logic. The end customer pays for all of it.
The 5-in-1 approach
ADHOOPU takes a different architectural approach. The flagship QG-1169 is a single 1U chassis that runs five media cores on one Linux platform:
Core 1: Encoding
Hardware-accelerated H.264 and H.265 encoding for live signal capture from HDMI 2.0, 12G-SDI and DisplayPort 1.4 inputs. The encoded streams are published to the network as standard RTSP, RTMP, SRT or WebRTC endpoints.
Core 2: Decoding
Hardware-accelerated H.264 and H.265 decoding for display-side signal reception. Up to 4K at 60Hz with 4:4:4 chroma. Streams can be pulled from any standard encoder on the network or from another ADHOOPU chassis.
Core 3: Recording
Multi-channel simultaneous recording to internal storage (2× SATA 3.0 hot-swap bays) or attached NAS. Configurable codec, resolution, frame rate and retention policy. Recordings are accessible via Web GUI, NFS or S3-compatible API.
Core 4: Transcoding
Real-time transcode between H.264 and H.265, between resolution ladders, and between transport protocols. Useful for feeding low-bandwidth clients (mobile, remote viewers) while maintaining a high-quality internal stream.
Core 5: Control
Native RS-232 (4 ports), RS-485 (2 ports), IR (4 ports), GPIO (8 channels), Relay (4 channels), HTTP, TCP and UDP. No separate control processor required. The chassis speaks every common AV control protocol directly.
Project economics
For a 16-node hospital installation — the kind that ADHOOPU integrators regularly deploy — the bill-of-materials comparison looks like this:
| Functional block | Multi-box architecture | ADHOOPU 5-in-1 |
|---|---|---|
| Encoding (16 channels) | 16 encoder units | Built into 16 QG-1169 chassis |
| Decoding (16 channels) | 16 decoder units | Built into 16 QG-1169 chassis |
| Control processor | 1 separate unit | Built into each chassis |
| Recording server | 1-2 rack units | Internal storage in each chassis |
| Video wall processor | 1 separate unit | Built into each chassis |
| Audio DSP | 1 separate unit | Built into each chassis |
| Management server | 1 separate unit | Web GUI + SSH on each chassis |
The reduction in hardware count is what drives the project cost difference. With ADHOOPU, the integrator specifies one chassis per node instead of six to eight separate devices. Cabling is simpler. Power and cooling requirements drop. Rack space drops. The control surface is one Web GUI instead of six vendor management portals.
What integrators say about it
The most common integrator feedback after a first deployment is about commissioning time. A multi-box AV-over-IP deployment that would take two engineers five days to integrate takes one engineer two days with ADHOOPU. The second-most-common comment is about reliability: fewer boxes means fewer firmware versions to track, fewer vendors to coordinate with when a security patch lands, fewer points of failure during the first six months of operation.
For a detailed bill-of-materials comparison for your specific project, contact our engineering team with a one-page scope document. We return a complete quotation within 24 hours.