A desktop computer setup displays audio settings, with two speakers, keyboard, mouse, and tower on a desk.
FxSound 1.2.18.0 Beta targets an everyday Windows audio annoyance: waking a PC only to find sound coming from the wrong speakers. The project’s GitHub release notes document a three-second wait for HDMI audio to reconnect after sleep, alongside a device-volume fix, preset Undo control, automatic crash recovery, a GPU-rendering setting, and a separate Windows 7 build. This is a pre-release, not a stable release.

A desktop computer setup displays audio settings, with two speakers, keyboard, mouse, and tower on a desk. HDMI audio gets time to reconnect​

The HDMI change addresses reports of FxSound abandoning the selected output after sleep. Its approach is straightforward: wait three seconds for the connection to return before proceeding. That is a targeted reconnection adjustment, not a promise to repair every Windows audio problem.

The project’s issue tracker supplies useful context beyond the changelog. In issue #646, a user running FxSound 1.2.13.0 described a laptop connected to a Samsung TV through Nvidia HDMI audio. After the display slept and woke, FxSound selected the laptop speakers instead of returning to the television. Another commenter using 1.2.15.0 reported the reverse sort of surprise: monitor speakers took over from the intended speaker output after standby. Both reports described Windows 11 systems.

The practical distinction matters. These reports concern which device plays the sound, rather than whether an equalizer makes it sound better. For affected users, keeping playback on the intended speakers is the more useful enhancement.

Volume settings should stop reverting​

The volume correction also has a specific reported scenario. Issue #655 describes FxSound 1.2.17.0 Beta remembering an older device-volume setting after the user changed it in Windows. In the reporter’s example, monitor speakers were lowered from 50 to 30, but switching to another output and back restored 50. The reporter said completely closing FxSound, adjusting the volume, and reopening the application worked around the problem.

That report helps distinguish this bug from arbitrary loudness changes: the trigger was switching outputs after adjusting a device’s system volume. Version 1.2.18.0 explicitly lists the associated fix.

Smaller controls, plus a Windows 7 distinction​

The remaining changes are concise but useful:

  • Preset Undo: Revert unsaved edits to the selected preset from its dropdown.
  • Crash recovery: FxSound automatically relaunches after an application crash.
  • GPU rendering: Enable it through settings, with confirmation before application.
  • Windows 7: Compatibility returns through a separate build using JUCE 6.1.6. The preceding beta moved to JUCE 9 and explicitly excluded Windows 7.

What beta testers should check​

For anyone testing the fixes, a focused before-and-after check is more revealing than simply confirming that music plays:

  1. Note the selected output, let the display or PC sleep, then wake it and check whether that selection survives.
  2. At a comfortable listening level, change one output’s Windows volume, switch away, and switch back.
  3. Record the FxSound version, audio-device names, and whether the trigger was display standby or full system sleep if a problem remains.

These checks follow the scenarios documented in the project’s reports; they are testing suggestions, not claims of independent validation. For users whose current setup behaves properly, there is no need to treat this beta as a mandatory upgrade. Its clearest value is giving affected users a targeted fix to evaluate—less unexpected speaker roulette, more predictable playback.

 

References

  1. (Bug) Switch the output device when the monitor wakes from sleep · Issue #595 · fxsound2/fxsound-app · GitHub github.com
  2. FxSound 1.2.18.0 Beta - Neowin Neowin 2026-11-17T09:59:18+00:00