The app now maintains your headset choice in Microphone and Speaker settings after a computer restart — previously it would maintain throughout the day but would reset upon startup

Added the option to prioritise inputs and outputs in the order you prefer. Go to the hamburger menu (3 lines) on the top right of the app ⇒ Click Manage inputs and outputs

UI improvement to make it easier to view the connected applications

Changed copy from “inactive” to “no app connected/paired” to avoid confusion when IRIS Clarity has not been set up in the meeting platform you’re using, or when you’re not actually on a call

Fixed bug where you could hear feedback on calls

Fixed bug where microphone was going silent without notice. Now, if it happens again (which it shouldn’t), user gets a notification to restart the app.

Added the option to turn Echo Cancellation on or off in Preferences. Echo cancellation is required when using the computer speaker in calls to avoid echo and feedback. However, if you are using headphones, you can turn this off to reduce CPU usage.

Updated terms in the Installer to be clearer and easier to understand

We now require a restart upon installation to ensure audio drivers are set up correctly and the app works optimally

IRIS Clarity now displays  apps connected to it, so if there is more than one, they will all be listed in the Microphone and Speaker sections

Bug fixes and improvements, including the issue where the app doesn’t open

Changed the app name to rather than just . It should make it easier to find. 😊

The background noise slider now needs to be toggled on before it appears in the application: Go to the hamburger menu (3 lines) on the top right of the app ⇒ Click Preferences ⇒ Check the box next to “Show background noise level slider”

Avaya users: we have added a new volume slider to address an issue inherent to Avaya that causes incoming audio to be a little too quiet. We are working on building this out for all other applications, too.

Fixed a bug where the app wasn't launching at system startup despite the “Launch at system startup” option being enabled