Filter Explanations
1. Product Role / Device Type
What kind of AVoIP endpoint is it? This chapter answers the first and most fundamental question: what does this device do in the signal chain?
Typical sub‑items
- Encoder – Converts HDMI / SDI / DisplayPort / audio signals into IP streams for transport over the network
- Decoder – Converts an IP stream back into a display- or audio-ready signal
- Transceiver – Can operate as either encoder or decoder, often configured by software
- Gateway / Bridge – Connects AVoIP systems to other environments (USB, Dante, NDI, legacy AV, etc.)
- Controller / Manager – Management, orchestration, or monitoring devices for AVoIP systems
Why this matters: Filtering by device role prevents mixing fundamentally different products (e.g. decoders vs controllers) when comparing specs.
2. Video Capabilities
What video performance does the device support? This chapter zooms in on image quality, bandwidth, and latency, which are core differentiators between AVoIP platforms.
Typical sub‑items
- Maximum resolution (e.g. 1080p, 4K, 8K)
- Frame rate (30, 60 fps, etc.)
- Color depth / chroma (4:2:0, 4:2:2, 4:4:4)
- Compression type
- Visually lossless
- Light compression
- High compression
- Latency class
- Sub‑frame / near‑zero
- Low latency
- Standard / streaming latency
Why this matters: Video requirements vary enormously between control rooms, signage, classrooms, live events, and broadcast. This chapter lets users filter products that meet both quality and latency expectations.
3. Audio Capabilities
What audio formats and workflows are supported? AVoIP is no longer just about video; audio interoperability is often equally important.
Typical sub‑items
- Embedded audio support
- Audio‑over‑IP standards
- Dante
- AES67
- Dante AV
- Audio breakout
- Analog audio
- Digital audio
- Multichannel support
Why this matters: Many AVoIP systems must integrate into existing audio networks or coexist with DSP‑centric designs. This filter chapter helps avoid incompatibility issues early. [linkedin.com]
4. AVoIP Technology & Standards
Which ecosystem does the product belong to? This is one of the most strategically important chapters on the site.
Typical sub‑items
- SDVoE
- IPMX
- Dante AV
- Proprietary AVoIP platforms
- Open standards vs closed ecosystems
Why this matters: Standards determine interoperability, vendor lock‑in, switch requirements, and long‑term viability. Integrators often start their search here when projects mandate a specific ecosystem.
5. Network & Infrastructure Requirements
What does the network need to support this device? This chapter connects AV and IT concerns.
Typical sub‑items
- 1 GbE / 2.5 GbE / 10 GbE
- Multicast support
- IGMP requirements
- Layer‑2 vs Layer‑3 operation
- Switch compatibility (AV‑optimised vs generic IT)
Why this matters: Network capability is often the real limiting factor in AVoIP design. These filters help align endpoints with the available or planned infrastructure.
6. Control, Management & Security
How is the device configured and protected? This chapter focuses on operational lifecycle, not just signal transport.
Typical sub‑items
- Web UI
- Central management platform
- API support
- Third‑party control integration
- Enterprise security features
- Authentication
- Encryption
- Network isolation support
Why this matters: Large deployments live or die by manageability. This chapter helps distinguish install‑and‑forget devices from enterprise‑grade systems.
7. Power & Form Factor
How is the device physically deployed?
Typical sub‑items
- PoE / PoE+ / PoE++
- External power supply
- Rack‑mount
- Wall‑mount / behind‑display
- Fanless vs active cooling
Why this matters: Real‑world installation constraints (power budgets, heat, space) often rule out products that look perfect on paper.
8. Manufacturer & Commercial Filters
Who makes it, and how is it positioned?
Typical sub‑items
- Brand / manufacturer
- Product family
- Market focus
- Enterprise
- Education
- Broadcast
- Digital signage
Why this matters: This chapter supports brand standardisation, vendor preference, and commercial alignment within integrators and distributors.
Summary: How the Filter “Chapters” Work Together
Each chapter narrows the field from a different professional perspective:
- Signal role (what does it do?)
- Performance (is it good enough?)
- Standards (does it fit my ecosystem?)
- Network impact (can my infrastructure handle it?)
- Operations (can I deploy and manage it at scale?)
Used together, the chapters turn the directory into a decision-support tool rather than a product list, which is exactly the mission of the AVoIP Solutions Directory.