Home › AV over IP › Distributed AV System Manufacturer

Distributed AV System Manufacturer — Hardware, Firmware and Management From One Factory

"Distributed" describes where the intelligence sits, not how the boxes look. In a distributed AV system every source and every display has its own endpoint, routing happens on the network, and the management layer is a service rather than a chassis. That changes what a manufacturer has to own — and it changes what happens in year four of the installation.

What Distribution Actually Moves

In a centralised matrix, video is switched in one place and every cable converges on that place. In a distributed system the switching function is spread across the network and the endpoints, so the cabinet disappears and the topology becomes an IT document rather than an AV one.

Capture

Encoders at each source convert HDMI to streams. One encoder serves every screen that needs the source, including screens in other buildings.

Transport

Managed Ethernet with IGMP snooping, a media VLAN and QoS. Fibre uplinks between floors or buildings carry AV alongside data.

Render

Decoders at each display or panel group apply windowing, crop and rotation locally, which is what makes video walls and multi-view possible without a separate processor.

Orchestrate

Management holds routing tables, presets, schedules, firmware versions and health status. This is the layer that decides whether the system is maintainable.

The Five Functions in One Platform

Distributed AV projects usually assemble four or five separate products: an encoder line, a decoder line, a recording server, a transcoder for streaming, and a control processor. Our QG-1169 platform folds those into one system so a site does not end up with five vendors and five support contracts.

Encoding

Up to hundreds of sources, H.264 or H.265, with per-source bitrate profiles so a document camera and a signage player do not have to share the same settings.

Decoding

Single display, multi-window, panel groups and full video walls. Decoders render locally, so adding a screen does not add load to a central processor.

Storage

Recording of selected streams inside the platform — hearings, lectures, procedures — with retention policy per channel instead of a separate NVR appliance.

Transcoding

Restream to a conferencing platform, an LMS or a CDN at a lower bitrate while the local wall keeps the full-quality stream. One source, several outputs, no extra hardware.

Control

Routing, presets, schedules and device health, driven from a browser, a touch panel or a third-party control system through documented APIs.

Firmware

Staged rollout with per-unit version reporting and exportable configuration. A distributed estate with no firmware discipline becomes unmaintainable by year three.

Centralised vs Distributed: An Honest Comparison

CriterionCentralised matrixDistributed AV system
Initial cost, small siteUsually lower. One chassis covers eight inputs and eight outputs with fixed cabling.Higher per room below roughly six endpoints, because each endpoint carries its own cost and each needs a switch port.
Cost at scaleRises sharply — bigger frame, more cards, longer dedicated cable runs, more labour.Falls per endpoint. The marginal cost of the twentieth room is an encoder, a decoder and switch ports.
Adding a roomNew cable home-run to the equipment room; the frame may need a card.Two endpoints on the nearest switch. No new home-run.
Failure impactChassis failure affects every room it serves.Endpoint failure affects one screen. The rest of the system is unaffected.
Skill requiredAV technician with matrix experience.AV plus network literacy: VLANs, multicast, QoS. This is the real cost of distribution.
Long-term supportTied to the chassis generation and its card availability.Tied to firmware and endpoint supply. Ask who controls both.
Best fitOne or two rooms, fixed signal set, no IT ownership of AV.Multi-room, multi-building, phased rollouts, KVM and wall requirements, sites where IT already runs the LAN.

What a Manufacturer Has to Own

In a distributed design the endpoints are commodity-shaped hardware with firmware inside. The value sits in what the manufacturer controls. Four questions reveal whether that control is real.

Does the manufacturer write the firmware?

If the board is a rebadged OEM unit, behaviour changes require the OEM's cooperation. Ask who can fix a multicast bug in the next release, and how long that took last time.

Is the management layer in the same house?

Endpoints from one supplier and management from another is where most distributed projects stall at commissioning: two support queues and nobody owning the integration.

Can the configuration be exported?

A routing table that lives only inside a running appliance is a single point of failure. Export and re-import of presets and endpoint configuration should be a documented operation, not a support ticket.

Is there a spare-parts commitment?

Distributed estates fail one endpoint at a time, which is manageable — but only if a spare arrives in days. Confirm lead time for a replacement unit in year four, not at tender.

Design Checklist Before You Buy

Network first

Media VLAN, IGMP snooping, QoS marking, uplink sizing. Get the switch configuration signed off by whoever owns the LAN before the first endpoint is ordered.

Count sources and destinations separately

Twelve sources on forty screens is twelve encoders and forty decoders. Quotes built on screen count alone are the most common cause of a mid-project budget conversation.

Decide recording at design stage

Retro-fitting recording into a distributed system means storage planning, retention policy and an extra network path. It is cheap at design and expensive after handover.

Fix the naming convention early

Endpoint names, room codes and preset names should follow one scheme from day one. Renaming two hundred endpoints later is a project in itself.

Plan control integration

If the customer has Crestron, Extron or Q-SYS on site, confirm the API commands and who writes the driver before commissioning week.

Agree the acceptance test

Latency figure, simultaneous-view test, failover test and firmware version. Written before installation, not negotiated after.

Deployments

Multi-building campus

Lecture theatres, overflow rooms and atrium signage on the campus backbone. Fibre between buildings replaces dedicated AV home-runs that would never have been pulled.

Hospital groups

OR and endoscope feeds to teaching rooms, PACS review in conference spaces, and procedure recording with per-department retention.

Courthouse clusters

Several courtrooms sharing evidence display, remote witness and recording, with a central control room monitoring endpoint health across the building.

Command centres

Any source on any screen, KVM at operator desks, and video walls that keep running when a single decoder fails.

Enterprise floors

Meeting rooms standardised on one endpoint pair, with central scheduling and a single firmware baseline across the estate.

Retail and franchise

Head-office content pushed to store displays, local sources still available in-store, all managed from one interface.

Frequently Asked Questions

What makes a system "distributed" rather than just networked?
Distribution means the switching and rendering intelligence sits at the edge. If a single chassis still performs all routing and every cable still converges on it, the system is networked but centralised. The practical test: can a room keep working if the head-end appliance is offline? In a genuinely distributed design, point-to-point and preset routing stored on endpoints continue; in a centralised one, the rooms go dark.
How many endpoints can one distributed AV system handle?
There is no hard chassis limit, which is the point. The practical ceiling is the network design and the management layer's scale. We have deployed estates in the hundreds of endpoints across multiple buildings; beyond that, the design question moves to zoning and routed multicast rather than to a bigger appliance.
Do we need a separate AV network?
A separate VLAN, not necessarily separate cabling. Media on a dedicated VLAN with IGMP snooping and QoS is the standard design. Physically separate switches are only justified in high-security environments or where the IT team will not permit multicast on the production LAN.
Can a distributed system replace an existing matrix without re-cabling?
Usually yes, and that is often the reason for the migration. Existing source and display cabling becomes encoder input and decoder output; the routing path moves onto the LAN. Phased migration is normal: one floor or one courtroom at a time, with the old matrix serving the rest until the last phase.
How is recording handled without a separate NVR?
Selected streams are recorded inside the QG-1169 platform, with retention set per channel. That suits hearings, lectures and procedures where the recording is tied to a specific source. For large-scale surveillance retention, a dedicated NVR remains the right tool, and the platform can pass streams to it.
What about security and access control?
Management access is role-based, and the media path stays inside the customer network — streams do not leave the site unless transcoding to an external service is configured deliberately. For government and court projects we document the data path so it can be reviewed by the customer's security team.
Is the system Linux-based?
Yes. Endpoints and the platform run on Linux, which is why they operate as appliances rather than PCs: no patch Tuesday, no antivirus overhead, and a stable behaviour profile for 7×24 operation.
Do you manufacture under partner brands?
Yes. The OEM/ODM programme covers hardware labelling, boot branding, packaging, default configuration and, where volume justifies it, firmware feature work. This is how several regional AV brands source their distributed line.

Start With the Room List

Send the rooms, sources per room, screens per room and whether recording or KVM is required. We reply within 24 hours with endpoint counts, a network plan and a phased migration proposal where an existing matrix is being replaced.

Request a System Design   See the AV over IP Platform

Related Pages

ADHOOPU

Professional AV manufacturer — Integrated AV Platforms, Distributed AV over IP, and AI Edge Computing & Video Analytics. OEM/ODM for system integrators, distributors and AV brands worldwide.

19 years of AV engineering · Shenzhen, China · 3-year warranty

Products

Integrated AV Platform QG-1169 AV over IP Encoders ST52K Encoder SR52K Decoder AI Video Analytics 615 AI Analytics Box

Solutions

Warehouse Safety Industrial Safety Oil & Gas Safety Hospital Safety Campus Security Parking Analytics Traffic Analytics Smart City Analytics Logistics Safety Retail Analytics Airport Analytics Smart Courtroom Surgical Teaching Command Center Education Meeting Room Smart Security Construction Site Factory & Industrial

Company

OEM / ODM About ADHOOPU FAQ Resources Contact
ADHOOPU · Room 1206, Block A, Dachanwan, Jingang Commercial Building, Xixiang Street, Bao'an District, Shenzhen, China
WhatsApp +86 138 2352 5531 · Email jimmy@adhoopu.com · Web https://www.adhoopu.com
© 2026 ADHOOPU. Integrated AV Platform · AV over IP Encoder / Decoder · AI Video Analytics · Professional AV OEM Manufacturer.