I think I can answer part of your question:I have an issue getting ARC Genesis to work with the new MRX 540 and wonder if anyone can help with what is going on – while I wait for Anthem to respond…..
Arc is the latest version 1.3.25 and the MRX540 has the latest firmware I believe 00.54/00.03. I have exactly the same issue from a desktop and a laptop both running Win 10.
The MRX is connected to the local network via ethernet and the web UI works fine.
When I kick off ARC it sees the MRX on the network and continues. It shows the speaker configuration screens and if I then continue it shows me the microphone and allows me to select it.
After initializing it says ‘Measuring form position 1’ , I click Start and I hear may be 10 test tones from the first Front speaker. Then the message ‘Critical audio problem’ appears. I can click Resume and it may do one more and present the same error or may be a sequence again, but it always fails in the same way.
ARC appears to access the microphone as I can see in the Windows privacy settings that it lists ARC as currently using it when doing the above..
I’ve seen others saying that the microphone level in Windows needs to be set at 100, but whenever I run ARC it resets the level back to 35 (in the device properties). I’ve noticed that if I test the microphone at this level in windows, i.e. 35, it appears to hear nothing. If I increase to 60+ then the windows test does hear something and at 100 it seems to have good levels. Is this what the issue is or is this a red herring? If it is, how do I stop ARC from setting it back to 35 every time I run it??
Any assistance / advice would be gratefully received.
As a side issue, I’ve noticed that if I do any config changes manually via the web UI before running ARC then after selecting the microphone in ARC it just appears to get ‘stuck’ at initializing and never goes any further.. Once I’ve run the Factory reset on the MRX it will proceed past initializing to the main issue above!
It seems that ARC requires 'exclusive access' to the microphone, which sets the level to 35. You can attempt to set something different, but it will always revert to 35 shortly afterwards. If you disable 'exclusive access' you can set whatever level you like: however, you then get a 'critical error' message & cannot use the mic!
One way round this is to go to the calibration level setting in the web ui & set it to -10 or similar in order to get the test tones up to the required level.