How do I setup audio return paths in MXNet 1G V2

How do I setup audio return paths in MXNet 1G V2

A decoder can only be routed to one encoder at a time. You can't have one decoder sending an Audio Return Signal to multiple encoders, for example. 

A lot of sites utilize CEC for volume adjustment/control of source and sink devices, this unfortunately can only be done when the encoder and decoder are in a unicast (or point-to-point) connection mode. You cannot get CEC passthrough to work reliably in a multicast AVoIP network. 

For the encoder, the encoder will output the returned audio via TOSLINK or HDMI strictly depending on how the decoder is "receiving" the ARC/eARC audio. If the decoder is intaking via TOSLINK, then the routed encoder will output via TOSLINK, if the decoder is intaking via HDMI, the encoder will output via HDMI.

Note - in the API commands below, remove the [] around the encoder/decoder ID/MAC

Establishing an Audio Return path is quite simple, here's the direct API commands:-

config set device arp enable [EncoderID/MAC] [DecoderID/MAC]
eg config set device arp enable 188A6A02118B 188A6A0213C9
This command will activate the Audio Return Path (ARP) feature, and establish a connection to the specified encoder & decoder.

config set device arp disable [EncoderID/MAC] [DecoderID/MAC]
eg config set device arp disable 188A6A02118B 188A6A0213C9
This command will simply kill the previously established ARP route on the specified encoder and decoder, and disable Audio Return (device will reboot).

config set device arp input [hdmiout, spdif] [DecoderID/DecoderMAC]
eg config set device arp input spdif 188A6A0213C9
This command will change how the Decoder ill intake audio from the sink device, either via TOS (spdif) or HDMI output. As mentioned above, this affects how the routed encoder will output the audio.

config set device forcearc {on,off} [DecoderID/DecoderMAC]
eg config set device forcearc on 188A6A0213C9
This command will give you the ability to force the decoder to only accept ARC audio, and not eARC. This is quite useful for systems that have an eARC compatible display, but only an ARC compatible AVR.


    • Related Articles

    • How To: Using the MXNet USB Control Tool

      Powerpoint and software for the USB Control Tool used when configuring Point To Point, Multicast Settings, and Control Routing. Extra information. To manually set the channel to 0000 via command line astparam s ch_select 0000;astparam save;sleep ...

    • New FPGA MXNET EV/DV2 System Issue.

      MXNET Firmware Update: Troubleshooting Guide Issue Overview: AVPro Edge’s latest FPGA firmware update (version 9.18.9) introduces valuable enhancements, but some users with older firmware (version 9.13.1) may experience compatibility issues, ...

    • How to set up an Araknis 310 Switch to use with AVProEdge MXNet

      We always recommend using the AVProEdge switch range when installing an MXNet system. These switches are very high end and come with a 10 year warranty and are pre configured out of the box to work with MXNet. However, if budget is a concern and you ...

    • USB KVM Not Working with MXNet 1G V2

      If you are finding the USB KVM feature is not working with MXNet 1G V2 it may be because the USB mode on the encoders is different to the USB Mode on the decoders so they are not compatible. This can be fixed by doing the following. You will need to ...

    • Poor Audio Quality on 2N Verso

      The 2N units are 3 high units. When you go 3 high you need to move the microphone down to the bottom.