Hi all
We have had an abundance of issues with setting up a pair of A77H Adam Audio monitors.
First of. The volume required to set up the speakers is WAY to loud. If we turn it down to normal speack level sonarworks want's us to turn it up. We did not have these volume issues with the other Adam Audio speakers we have in the main studio. (The A77H are in Post prod) Once we managed to get past the deafening volume needed we then got stuck in a input signal loop. After 4 hours of trying we got passed the green circle thing only to be told that our left and right speakers are the wrong way round.(they are not) So we are now stuck and have nooooo idea what to do next. We have checked and double checked everything we can but to no avail.
Any help will be extreamly greatful.
Thanks in advance.
KayJay. ( i did post this earlier but i think i lost it. Story of my life)
2 comments
Hi alowendgrowl, thanks for reaching out! It looks like you also made a post regarding some issues with the measurement process in the Reference 4 Community.
I would recommend here as well to go through our Measure troubleshooting guide to make sure everything is set up properly: Stereo speaker measurement troubleshooting guide
The speaker volume should be set at a conversational volume. You can also try increasing the mic input gain and turning down the speaker volume to reach the optimal level for the app to proceed further.
If some issues still persist, can you provide more details on your signal chain (computer, interface, any other components involved)? Thanks!
Hi.
We have done all the measurement trouble shooting guides and they were no help. Adjusting the input gain has no effect, the green circle just sits there and just twitches. We do not have access to our computers. They are locked in a temprature controlled room. P.c is running Intel 100000x series 20 core CPU. 256 Gb DDR4 Ram. Motu 112D into a Behringer ADA8200, then into Adam A77H. If you need any more info, i will do my best to pin down one of the Technicians.
Sadly, this has caused us 6 hours of Downtime. If we cant get a resolution to this problem, we will have to go to another product.
Thanks Zane for the reply.