Two I/O sizes
Choose 12×8 or 4×4 analog I/O around the room and system requirement.
Official Symetrix product image showing Radius NX 12×8 and 4×4 front and rear panels. Dante, AEC and expansion-card options depend on the selected configuration.
Symetrix · Networked Audio DSP
Symetrix Radius NX
Product / system referenceRadius NX
Flexible networked audio DSP for conferencing and installed AV, available in 12×8 and 4×4 analog-I/O versions with optional Dante and AEC expansion.
12×8 / 4×4Analog I/O
64×64Dante option
8 / 16AEC option
USBAudio
Selection guidance
Where Radius NX fits
Network audio option
Optional 64×64 redundant Dante supports larger networked-audio architectures.
Conferencing expansion
Optional 8- or 16-channel AEC coprocessor supports meeting and conference-room deployments.
Control ecosystem
Embedded web server, GPIO, RS-232 and Symetrix control options support integrated AV operation.
Technical reference
Radius NX reference
| System type | Networked audio DSP |
|---|---|
| Analog I/O models | Radius NX 12×8 or Radius NX 4×4 |
| Dante | Optional 64×64 redundant Dante module |
| AEC | Optional 8- or 16-channel AEC coprocessor |
| Expansion | 1 I/O expansion-card slot |
| USB | Built-in USB; supports computer conferencing / multitrack workflows depending on configuration |
| Control | 4×4 GPIO · RS-232 · embedded web server · Symetrix control ecosystem |
Official manufacturer source & Malaysia confirmation
Current manufacturer information is used as the technical reference. Product revision, software/firmware, accessories, approvals, country SKU, availability and final project configuration can change; The exact Malaysia requirement should be verified before quotation or tender submission. Official Symetrix reference ↗
Current manufacturer information is used as the technical reference. Product revision, software/firmware, accessories, approvals, country SKU, availability and final project configuration can change; The exact Malaysia requirement should be verified before quotation or tender submission. Official Symetrix reference ↗
Applications
Typical deployment environments
Meeting roomsTraining roomsAuditoriumsInstalled AVNetworked audio systems
Integration considerations: The final design should be based on the complete workflow—not the product alone—including interfaces, network/power, mounting or rack design, accessibility, monitoring, operational policy, commissioning and lifecycle support.
Continue exploring
Related Professional Audio references
System dependencies
Place DSP/control in the complete audio system
A product is only one part of the deployment. Confirm the supporting components and infrastructure before final model selection or installation.
Dependency links are planning paths, not automatic compatibility claims. Exact model/SKU, interfaces, loading, firmware/software and accessories must be verified for the final project.
Audio chain
Installed pro sound
Coordinate DSP with inputs, amplification, loudspeakers and room requirements.
Open related area →Meeting application
Conference audio
For meeting spaces, align DSP/control with conferencing microphones and room AV.
Open related area →System design
Professional audio design
Confirm I/O, network/control, redundancy and commissioning as one system.
Open related area →Product family navigation
Continue from this model
Return to DSP & Audio Control, continue to the relevant solution, or open a selection guide without losing product context.
New project / active selection
Select through the current family
Use the parent family and solution links to compare application fit. Current Malaysia availability, exact SKU, warranty terms and compatible accessories should be verified at quotation stage.
Existing installed product
Assess support before replacing it
Already installed? Identify the exact model and condition first, then verify lifecycle, parts/software support and the practical repair or migration path.
Open legacy & replacement support →Other items in this family
Need help selecting the right professional audio architecture?
The final equipment schedule should be based on the application, interfaces, system topology, site conditions and support requirements.
