Dev note: We've been reading the feedback and this beta is a direct response to it. Think of Wave Link 3.3 as our Snow Leopard update (kudos if you catch the reference): fewer big headlines, a lot fixed underneath. The biggest thing people reported was Wave Link resetting its configuration out of nowhere. We've made significant progress on this and it should be much less common now, though some edge cases are still being worked through. After a Wave Link update, OBS Studio can also automatically restore its audio routing. On top of those two, a stack of smaller fixes went in (sliders no longer jitter, among others) and the app runs more smoothly day to day.

Dev note: This backup and restore feature followed additional work investigating why Wave Link would reset to defaults, seemingly out of nowhere. The team identified three main causes. All three have been worked on in this update, though some improvements are still ongoing.

• If Wave Link was stopped halfway through saving (by a crash, a forced shutdown, or a power outage), the settings file was left unfinished and couldn't be read on the next launch, so it started fresh. That's why so many reports started with "after a restart." Saves are now protected against interruptions.
• A single malformed or duplicate entry anywhere in the settings file used to get the whole thing rejected, leaving you back at a clean setup. Wave Link now recovers from the most common of these, skipping problem entries and loading everything else. This is an area we'll keep improving.
• Windows sometimes reassigns internal IDs to audio devices after a Windows Update or driver change. When that happened, your audio inputs looked brand new to Wave Link (empty inputs, no mixes, no effects), while the original entries sat unavailable. Wave Link now identifies the same audio inputs across that kind of change and keeps its routing and effects intact, though edge cases remain and we're still working through them.

These changes, in addition to the backup, mean Wave Link is much more reliable at loading your configuration. Should the worst happen, a recent backup is available to load with just a few clicks. Each backup is a full copy of Wave Link's settings file, so every restore point captures your entire configuration at that moment. One more automatic backup is saved right before an app update installs, so you can always revert if something goes wrong.

Dev note: On the surface, this behavior of losing audio input in OBS Studio looks like an OBS bug or a Wave Link bug. It's neither, and rather a quirk of how Windows identifies devices under the hood.

Windows doesn't identify an audio device by its name. Every input and output gets an internal ID, for example: \\?\SWD#MMDEVAPI#{0.0.0.00000000}.{2E4FC8C4-E875-11E8-B851-806E6F6E6963}, and apps that remember your device choice, OBS included, save that ID. When a driver is changed or Windows re-enumerates your hardware, those IDs can change. The microphone on your desk hasn't changed, but as far as Windows is concerned, it's a different device. OBS looks for the ID it saved, doesn't find it, and falls back to default.

Some Wave Link updates include a new audio driver, and installing one can trigger this reshuffle. We can't stop shipping driver updates, so the next best thing is making sure your OBS setup isn't the price of taking one. That's why the backup happens before the update installs, and why Wave Link holds an update back if it can't save a backup first.

If a device's ID has changed since the backup, Wave Link matches it by name instead. Any sources that no longer exist in OBS are recreated in whichever scene is active when you restore.

Dev note: The ear icon used to sit on each mix header but only appeared on hover, and only stayed visible on whichever mix was already being monitored. Most users never found it. This control is now permanently visible, so what you're monitoring and how to change it are always in the same place.