• Registered: 2016-01-16
  • Posts: 14

Topic: Fireface UCX - 5.1 Speaker Configuration in Windows incorrect

The standard 5.1 speaker configuration is for the two surround speakers to be positioned +/-110 degrees from the listener. I've just installed a RME Fireface UCX, and have the surround working just great... but in Windows 10, the 'configure speakers' option of the sound control panel has the speakers positioned more as surround REARS, as if they were rears from a 7.1 setup.

This is causing positional inaccuracies in video games, which is a problem for us as this card is for a game audio development. The most common audio system in games (Wwise) will use the Windows speaker configuration to position sounds to the speakers appropriately.

Interestingly, one of our other sound rooms has the same card and didn't have this problem, actually, 5.1 was listed twice in the speaker configuration: one with the surrounds at the correct 110 degrees (listed as 'surround side') another behind (listed as 'surround rear'). We just updated the driver in that room and the 110 degree speaker position was REMOVED, leaving just the incorrect 'surround rear' configuration. So it appears that RME have removed the surround side 5.1 configuration in the latest driver.

PunBB bbcode test


Can someone from RME comment on this please. We would REALLY like to get the correct 5.1 speaker configuration back,with the surround speakers positioned at 110 degrees.

Thanks!

  • Registered: 2016-01-16
  • Posts: 14

Re: Fireface UCX - 5.1 Speaker Configuration in Windows incorrect

Reverting to 1099 fixed it.

Looking back at the release notes and the forum, it looks like RME spent some time messing with the WDM surround configuration a while ago by adding loads of speaker configurations, some bugs where introduced and then all of it got ripped out and replaced with the 5.1 being set to surround rears:

V 1.164 (06/26/2018)
- WDM: 5.1 format changed to rear speakers


Can someone explain the decision to use the non-Dolby spec speaker position? We're not going to update our drivers beyond 1099 until this is resolved unfortunately.

Thanks