All,
I'm running macOS Sonoma version 14.7.6 (23H626) on a Apple Mac Studio M2 Ultra.
I have four Universal Audio Apollo's; and X16, X8, X6 and X6. Those also connect to a UAD Satellite Octo and Quad.
I am running SoundID Reference Measure Version 5.12.2 (5.12.2.1)
I have the Sonarworks calibration Mic connected to the Apollo X8 mic input 3.Upon launching Measure I am able to detect the mic inout level fine and the Apollo X8 sees it on Mic Input 3 - all of that is great. However during the next step it does playback the test voice, Left Speaker - Right Speaker but after selecting Yes, my volume is set and then “Start Adjusting” the countdown and test tone can be heard but I get a message “No Signal Detected”. UGH
Please help
6 comments
I have the same problem with the X16 and a xTwin for my mic input. I sure hope they fix this.
Hi guys, thanks for posting and commenting!
We have already received several other reports of this behavior and managed to reproduce it in-house too. Further investigation, together with UA, revealed that the problem stems from the UAD Console. The issue comes from using a non-default I/O Matrix, such that the microphone inputs are not in the default input. During the Listening Spot stage, the microphone signal will be lost as a result. This is because the "integrated measurement mode" sets the I/O matrix to default, which blows away the microphone channel selection.
We have already addressed the issue in a new version, which is not available publicly yet. I have created individual support request threads for both of you, and shared the potential fix version. Let us know if this resolves the problem, thank you!
I also solved it with the procedure below:
I turned off the X16 and tried performing with the Twin only, making sure the UAD console was set to automatic I/O detection and removed the X16 from the device list in UAD console. It worked as it should.
I then turned everything off, started the X16, let console auto detect I/O then turned on the Twin, let console autodetect. This seemed to solve the issue. I'll update to the version you sent, I appreciate your prompt reply!
Scott Cooke makes sense - essentially, the issue can be avoided by using the default I/O matrix. If you test the build I sent, please make sure to do so with your custom I/O matrix, as that is the entire point (should work with the custom matrix too). Thank you!
Confirming it now works with my custom I/O matrix as well. Thank you!
Scott Cooke very glad to hear that, thanks for following up and letting us know!