If SoundID Reference standalone app has a lower volume than set and the "Adjust output device gain" feature is not working, this guide provides more details on the issue and workarounds.
In this article:
Known issue
Resolution version: TBD, Expected release: TBD
Article updated: Dec 08, 2023
"Adjust output device gain" not working
With the "Adjust output device gain" setting enabled in the SoundID Reference standalone app, adjusting the gain level does not adjust the volume of the built-in output itself. The volume remains lowered, in some cases nearly inaudible. This issue has been present for some since SoundID Reference version 5.7.3. Our developers are looking into it.
Known workarounds
There are two known workarounds for this:
1. Manually adjust the volume:
- In SoundID Reference Preferences, disable "Adjust output device gain"
- Open Audio/MIDI
-
Drag the volume slider for the output manually to the desired level
NOTE! There may be a volume jump upon switching output device in this case, so be cautious.
2. Revert to a previous version: Current software issues - how to revert back to a previous version
4 comments
This is a BIG issue and it's 6 months old already, please fix.
Hi harri,
I hope you are doing well!
Yes, this particular issue is still being worked on. Due to some other major issues and product releases this has been slightly postponed. Updates on the issue should be implemented in the upcoming updates.
Once an update will come, you will be notified instantly.
Best regards,
Martin from Sonarworks
It is end of the '24 and still nothings changed:( recent updated just get it worse:(
I'm having the same issue with Sound Reference on Mac where the output volume in the app is capped at -6.9dB and won't go any higher. I'm using Sound Reference version 5.12.1.8 on MacOS Ventura 13.7.1 with an Apollo Twin.
I've tried the workarounds listed on this page and none will help. I essentially can't use the program to help calibrate my speakers with this low of an output volume. For a speaker calibration solution of such high quality (and high cost) I'm surprised a bug so egregious is not getting fixed at the highest priority and expediency.
Please expedite an fix!