Discord audio routing stopped working correctly with FxSound after a recent update

Hi,

I have a specific audio-routing problem with FxSound and Discord that started approximately 10 days ago.

The important part is that this setup was working correctly before. I have been using FxSound with this configuration for quite some time. There were occasional minor endpoint-switching issues, partly related to my HyperX headset, but I was still able to use different audio devices normally. For example, I could have general PC/game audio playing through my monitor/speakers while Discord voice chat was playing through my HyperX headset.

The problem appeared recently, and I cannot get the previous behavior back.

My setup:

  • HyperX Cloud III S Wireless headset
  • Creative Pebble speakers
  • HyperX NGENUITY
  • Windows 11
  • Discord
  • FxSound

Here is my current configuration.

FxSound:

  • Playback Device → Creative Pebble speakers

Discord → Voice & Video:

  • Input → Windows Default (my HyperX/NGENUITY microphone)
  • Output/Speaker → HyperX Cloud III S Wireless

With FxSound turned on, my normal PC audio plays correctly through the speakers.

However, if someone calls me on Discord:

  • My microphone works normally.
  • The other person can hear me.
  • I cannot hear the other person through my HyperX headset.

There are two ways I can make the incoming Discord voice audible:

  1. Change Discord’s output from the HyperX headset to my speakers.
    → Then I can hear the other person through the speakers.
  2. Change FxSound’s Playback Device from the speakers to the HyperX headset.
    → Then I can hear the other person through the HyperX headset.

However, changing FxSound’s Playback Device to the HyperX headset also moves the entire audio output processed by FxSound to the headset. This means my game/general PC audio also goes to the headset instead of the speakers.

There is another very important detail:

If I turn FxSound OFF (using the FxSound ON/OFF function, without exiting/closing the application), the problem goes away and I can use the audio devices normally.

So, with FxSound turned OFF, I can have:

Game/general PC audio → Speakers
Discord voice → HyperX headset

which is exactly what I want.

This is why I believe something has changed recently in how FxSound handles its playback endpoint or Discord audio routing.

For the first period after setting everything up, this worked correctly. I did have some occasional endpoint-switching issues, partly related to the HyperX headset, but the actual audio routing between applications worked. I could, for example, have audio from my monitor/other PC sources playing normally while Discord voice was coming through the HyperX headset.

The current behavior only started approximately 10 days ago.

Could a recent FxSound update have changed the way the FxSound virtual playback device handles application-specific audio routing or Discord?

Is there a known issue with Discord + FxSound in recent versions?

I would really appreciate it if someone from the FxSound team could take a look at this, because the exact same setup was working before the recent change, and simply turning FxSound OFF restores the expected behavior.

Thanks!

p.s: I ve checked a bit the forum for similar problems,the one suggesting about Experimental/legacy seems to not be the case for me cause Discord doesnt have that Subsystem anymore,therefore i couldnt be able to change that and cause the problem or change it and fix it.

In System > Sound > Volume mixer, please check the Output device set for Discord. If it is set to Default, then Discord could be trying to use FxSound. So change it to HyerX headset.