Critical issue – AMC unusable with multiple Apollo interfaces (X and non-X)

0

Hello Sonarworks team,

 

I’m reaching out to report a blocking issue with the Apollo Monitor Correction (AMC) integration in SoundID Reference.

When I use my Apollo Twin X Gen 2 alone, everything works perfectly:

  • The calibration profile loads via AMC

  • Audio is routed correctly

  • The Monitor Control in the UAD Console functions as expected

 

However, as soon as I turn on my Apollo 8 (non-X, rack unit), audio is completely cut off.

The Twin becomes the secondary interface, and SoundID appears to apply the AMC calibration to the Apollo 8 — which is not connected to my monitors.

 

As a result, the Twin X — my actual monitoring interface — receives no audio at all.

To get audio back, I have to:

  • Power down both Apollo units

  • Turn on only the Twin X

  • Relaunch SoundID Reference and manually reapply the calibration profile

 

This behavior makes AMC unusable in setups involving multiple Apollo interfaces (X and non-X).

 

What’s clearly missing is the ability to:

➡️ Manually select which Apollo device the AMC profile is applied to.

In my setup (and I imagine many other professional studios):

 

  • I use an Apollo 8 for I/O

  • And an Apollo Twin X for monitoring and Monitor Control

  • I expect AMC to work exclusively on the Twin X, without interference from the other unit

 

Could you please let me know:

 

  • Is this behavior known?

  • Do you plan to implement a device selection option?

  • Is there an official workaround for this kind of multi-Apollo configuration?

 

Thank you in advance for your help — I truly value your tool, but this limitation currently makes the integration unusable in my studio.

1 comment

0

Even when I configure the Apollo Twin X as the master device and the Apollo 8 as the secondary (slave) in the UAD Console, the problem persists.

Please sign in to leave a comment.