Processing and Control for Professional AV Installations

Frequently Asked Questions

Radius NX

  • Is Radius NX Microsoft Teams Certified?

    Symetrix is a Microsoft Partner*. Symetrix products are Microsoft Teams compatible**.

    * Microsoft Partner website

    ** Microsoft Teams Compatible: Provides the same functionality as certified products. 

DSP General

  • How can I reduce the amount of DSP usage in my site file?

    If you're programming a site file and notice that your approximate DSP usage seems to be getting too high, possibly with fewer modules being used than expected, consider using dual-mono modules. These modules are capable of doing the same processing as mono modules, but essentially offering two for nearly the price of one. For exmple, a mono Loudspeaker Manager module uses 5.6% DSP while a dual-mono Loudspeaker Manager module uses 3.1% DSP each, totalling 6.2% DSP for both modules. This can drastically improve your DSP performance by not using as much processing resources. 

  • Where can I download archived versions of Composer software?

    Archived versions of all final public releases of Composer software are available here. The software runs on a Windows PC and is used to configure, design, and control Composer-based products. For new designs we highly recommend using the latest version of Composer, however archived major release versions can be found below for legacy compatibility and/or troubleshooting requirements. All firmware files are included as part of the downloaded Composer software package. The Composer firmware
    versions and Dante Kernels listed below are to help in cross-referencing the firmware running on the installed DSP(s) with the corresponding version of Composer that should be downloaded.

    To communicate with Symetrix hardware from a given version of Composer, it may be necessary to upgrade (or downgrade) firmware in each hardware device. This can be done directly from the Composer application and only takes a few minutes per device. Firmware upgrade is done from the Composer Hardware menu. 

  • What is DSP and how does to apply to Composer-based hardware?

    Advanced Digital Signal Processing is at the core of our Composer-based hardware. Our solutions simply design and deliver superb fidelity, adding value for designers, integrators, and end users.

  • What is the maximum number of networked devices allowed in system?

    Control Devices – Composer Limits

    The maximum number of control devices in a Site file is 128. This includes DSPs, Touchscreens, W series, Control Servers, and xControls. The limit is based on the maximum number of units Composer can communicate with at once. If this limit is exceeded, some will not locate correctly so Composer will not go online. This limit does not include Dante only devices that are located through a DSP. See the section below for limits on these devices.

    Dante Devices – Dante Audio Routing Limits

    The maximum number of Dante devices that can be routed to by one Brooklyn based DSP is 128. But in reality, this limit is rarely met as there are other soft limits that are reached first. First, the maximum number of Dante Channels (64) and/or Dante Flows (32) supported by one DSP will usually limit the number of devices that can be used. 

    Dante Devices – Intelligent Module Limits 

    The CPU/Memory resources used by Intelligent Modules will also limit the real world number of devices that can be used. The maximum number of 256 Intelligent Modules per DSP may theoretically come into play, but other practical limits will almost always be reached first. For xIO Devices, Intelligent Module requirements for CPU processing limit is different for Radius NX class DSPs and Edge/Prism class DSPs. Radius NX devices can support about 30 Intelligent Modules communicating with xIO Devices. Alternately, Edge/Prism Class DSPs, which have an older CPU and less Memory, can support about 20 Intelligent Modules communicating with xIO Devices. This is a rough estimate because the available processing is also affected by other things the Site might be doing (e.g. running Control Screens, recording/playback, etc.). In practice, this means that if you want to run more than 20 or 30 xIO devices in a single Site, you will need to divide them between multiple DSPs.

  • What is Phantom Power?

    Phantom power derives its name from its invisibility to audio signals, even though the microphone cable carries both phantom power (as direct current) and audio signals (as alternating current). Specifically, the term phantom power means a positive DC voltage sent to the microphone on both audio leads, through current-limiting resistors which also serve to isolate the audio leads from one another. The front panel phantom power button applies phantom power via pins 2 and 3 of the mic input XLR connectors.

  • Will phantom power damage my non-condenser microphones?

    Generally no, some older ribbon microphones are somewhat susceptible, but it’s always a safe bet to disable phantom power when not needed.

  • What kind of cable do I use to hook up the Analog Control Inputs?

    Standard two-conductor shielded twisted pair.

  • What is the RS-485 network?

    RS-485 is a standardized network for balanced digital multipoint communication. In Composer-based hardware, only ARCs can use the RS-485 network.

  • Should Symetrix hardware have an extra rack space above and below it in the equipment rack?

    Anecdotal evidence suggests a longer life-span of Symetrix hardware that is separated by at least one additional space in the equipment rack. This is in addition to following the guidelines for maximum recommended ambient operation temperature. See unit’s Quick Start Guide for information.

  • Will phantom power damage my non-condenser microphones?

    Generally no, some older ribbon microphones are somewhat susceptible, but it’s always a safe bet to disable phantom power when not needed.

  • What is required to configure a Symetrix DSP?

    Windows 7 or later.

    250 MB free storage space.

    1024×768 graphics capability.

    16-bit or higher colors.

    CD-ROM drive or Internet connection 512 MB or more RAM as required by your operating system.

    An available serial port capable of operating at 57600 or 115200 baud.

    A straight-through RS-232 cable and/or CAT5 cable.

  • Are Crestron modules available for Composer?

    The following archive contains Crestron modules for the most commonly controlled functions of Composer:

    Composer Crestron Modules v.3.0

    The v3.0 Crestron modules are compatible with Composer hardware including Edge, Radius 12×8 EX, Radius AEC, Prism, Solus NX, xControl, 2 Line
    Analog Telephone Interface Card, and the 2 Line VoIP Interface Card. The following control modules have been developed and will be available for use with the Crestron 2 and 3 series controllers:

    • Volume Up/Down Control Module with User Limits
    • Fader Set Control Module
    • Button Push Module
    • Preset Execution Module
    • Controller Receiver Module
    • Input / Output Selector Module
    • VoIP Dialer Module and ATI Dialer Module
    • Speed Dial Module / Speed Dial Store / Delete Phone Number / Name Module

    The updated Crestron modules utilize command processor architecture to maximize efficiency and responsiveness. The command processor is responsible for all the data parsing to and from the Symetrix DSP which makes it more efficient for the individual control modules to operate. When the control ID’s match a particular control module, then the controller information is used and updated.

    Note: Crestron v.3.0 modules were specifically designed to work with SymNet Composer hardware over RS-232 (baud rate 57600), TCP/IP or UDP/IP port 48631. These modules will not work with legacy SymNet hardware. If you have legacy SymNet hardware, please use the Crestron v.1.0 or 2.0 modules.

    Composer Crestron Modules v.2.0

    The v2.0 Crestron modules are compatible with SymNet Composer hardware including Edge, Radius 12×8, Radius AEC, Prism, Solus NX, xControl, SymNet 2 Line Telephone Interface Card.  Examples provided include Fader control, Button press, Increment and Decrement button, Preset Recall, Mute All, and Controller Receiver.

    Note: Creston v2.0 modules where specifically designed to work with SymNet Composer hardware over RS-232 (baud rate 57600) or UDP/IP port 48631.  These modules can also be used for UDP/IP control with legacy SymNet hardware, Integrator Series, Jupiter Series, and Solus by simply changing the RS-232 buad rate to 38400 or the UDP/IP port to 48630.

    2 Line Analog Telephony Interface Crestron Control Module v2

    This program was created to demonstrate the capabilities of the SymNet 2 Line Analog Telephone Interface (ATI) card in the context of Crestron
    external control. The user module and touch panel signals that comprise 95% of this program can be easily copied to other integration projects where the Symetrix ATI card will be used. A Composer file has been created that has the controller numbers corresponding to this external control program. This allows the correct information to flow in both directions between the device and control system processor.

    Composer Crestron Modules v1.0

    The v1.0 Creston modules are compatible with: Jupiter, Zone Mix 761, 780, 788, 722, Solus, 8x8DSP, CobraLink, and 4×4, 4×12, 8×8, 12×4 Express Cobra hardware), Examples provided include Volume, Fader, Button, Switch and Dialer control plus Preset recall. Additionally, the v1.0 modules will work with the legacy SymNet hardware across a multi-unit ring, as well as a multi-ring system. A matching example SymNet Designer Site File is also included. The modules are fully documented by the SymNet Control Protocol Crestron Module. 

    Addendum linked here: SymNet_Control Protocol_Crestron_Module_Addendum 

  • Can I change the temperature scale in Composer’s DSP diagnostic module?

    Our diagnostics module is set to Celsius by default and, currently, there is no feature to change this to Fahrenheit or any other temperature scale. 

  • How do I factory reset my DSP?
    • Remove power from the DSP.
    • Locate a pin hole on the back of the DSP. There is a reset button recessed under the surface.
    • Remove power from the unit, push and hold the reset button, re-apply power and continue to hold the reset button for 20-25 seconds.
    • You may hear relays clicking inside the DSP, this is normal. The front screen should display “Performing factory reset” at some point.

    IMPORTANT NOTE:
    Ensure there is a backup of the site programming saved prior to performing a factory reset. A factory reset will erase all memory from the DSP and return it to factory specification. This includes site programming, assigned IP address, and firmware updates since original factory firmware. If you would like assistance or have any questions about this process, please reach out to Tech Support at support@symetrix.co or call +1 (425) 778-7728, Ext. 5.

  • Why are my DSPs LED lights “running” back and forth?

    This can mean that the unit has no site file/programming loaded onto it or that the loaded programming has been invalidated. If the latter is the case, contact Tech Support at support@symetix.co or call +1 (425) 778-7728, Ext. 5.

  • How do I reset my DSP’s IP address and return it to DHCP mode?

    Some of our DSPs don’t have a front screen that will display the current IP address, which can cause some connection issues. You can reset the DSP’s IP configuration back to DHCP by locating and pushing the reset button on the back of the unit for about 1-2 seconds. The button should not need to be held – just a good, solid press.

    IMPORTANT NOTE:
    Do not hold this reset button for longer than 10 seconds to avoid the risk of a factory reset, which will erase all memory of the DSP including site programming and firmware upgrades since factory spec.

  • Can I downgrade a DSP below its factory spec?

    No. When a DSP leaves our factory, it is loaded with the current firmware at the time. Units cannot be downgraded below this factory spec in the field. If there are other units in the site that are below this, they will need to be upgraded to meet this firmware version.