home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
HTPC Projects
Software
Operating System
Can't engage pro logic when windows is set to 5.1 via hdmi
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Toastemeister" data-source="post: 1236533" data-attributes="member: 162370"><p>I had to register as I've struggled with this and only recently fixed it and notice the answer was given earlier (and in the MP WIKI) but might be missed especially as I hit this thread multiple times when Googling this issue and I suspect others have too.</p><p></p><p>The issue is the windows Directsound API and the answer is to use WASAPI (or ASIO) wherever possible and leave the windows speaker configuration to 5.1. These settings are sometimes called exclusive mode audio and should be available in your media player sound output settings if supported (MP and KODI support it). Effectively when using WASAPI the player ignores the windows speaker configuration and sends what it has to the amp directly. This means all discrete 5.1 sources (DTS, Dolby) will work as discrete surround sound and any stereo material played by the player will be treated as such by the AV amplifier (applying prologic for example)..</p><p></p><p>All your other Windows applications will use Directsound unless specified and as such obey the Windows Speaker configuration. I address some situations below (Chrome, audio apps, games)</p><p></p><p>Chrome used to have a switch to enable WASAPI but is is currently broken ( google chrome enable-exclusive-audio). You could use an older version to fix this but newer versions have important security patches. Best to push Google to fix this. </p><p></p><p>Spotify hasn't WASAPI output ( a clone called Fidelify does ). If your media player has a Spotify plugin this can fix this issue too as it will use the output configured on the player. Other streamers vary. Tidal has WASAPI (called exclusive mode) buried in the output settings for example.</p><p></p><p>5.1 games will use Directsound and if you've the windows speakers set to 5.1 they will output 5.1 (see note below).</p><p></p><p>Stereo games (many titles) will also use Directsound output and if the speakers are set to 5.1 will fail to get the prologic treatment. Only switching to a 2 channel speaker configuration will fix this (forcing discrete 5.1 games to stereo prologic too until switched back). This at least limits the amount of times the speaker configuration needs to be changed to playing stereo games. </p><p></p><p>A final note... even if you've surround speakers at the side choose the speakers to the rear setup in windows. At least one game ( Wasteland 2 ) didn't recognise the surround speakers to the side setup as 5.1 and only allowed stereo in the output as a result. Potentially the opposite is true for other titles so try this if games don't give 5.1 output. If you've a 7.1 aware amp and have 5.1 speakers you can safely set windows to use 7.1 and the amp will downmix the rear channels to what you have so this can assist as well (though once again some games may not see the windows 7.1 output as a valid surround output). All of these issues surrounding games are just related to poor game programming or lack of implementation of discrete surround. Consoles mostly got around this by having surround sound as a requirement for games to be released on them.</p></blockquote><p></p>
[QUOTE="Toastemeister, post: 1236533, member: 162370"] I had to register as I've struggled with this and only recently fixed it and notice the answer was given earlier (and in the MP WIKI) but might be missed especially as I hit this thread multiple times when Googling this issue and I suspect others have too. The issue is the windows Directsound API and the answer is to use WASAPI (or ASIO) wherever possible and leave the windows speaker configuration to 5.1. These settings are sometimes called exclusive mode audio and should be available in your media player sound output settings if supported (MP and KODI support it). Effectively when using WASAPI the player ignores the windows speaker configuration and sends what it has to the amp directly. This means all discrete 5.1 sources (DTS, Dolby) will work as discrete surround sound and any stereo material played by the player will be treated as such by the AV amplifier (applying prologic for example).. All your other Windows applications will use Directsound unless specified and as such obey the Windows Speaker configuration. I address some situations below (Chrome, audio apps, games) Chrome used to have a switch to enable WASAPI but is is currently broken ( google chrome enable-exclusive-audio). You could use an older version to fix this but newer versions have important security patches. Best to push Google to fix this. Spotify hasn't WASAPI output ( a clone called Fidelify does ). If your media player has a Spotify plugin this can fix this issue too as it will use the output configured on the player. Other streamers vary. Tidal has WASAPI (called exclusive mode) buried in the output settings for example. 5.1 games will use Directsound and if you've the windows speakers set to 5.1 they will output 5.1 (see note below). Stereo games (many titles) will also use Directsound output and if the speakers are set to 5.1 will fail to get the prologic treatment. Only switching to a 2 channel speaker configuration will fix this (forcing discrete 5.1 games to stereo prologic too until switched back). This at least limits the amount of times the speaker configuration needs to be changed to playing stereo games. A final note... even if you've surround speakers at the side choose the speakers to the rear setup in windows. At least one game ( Wasteland 2 ) didn't recognise the surround speakers to the side setup as 5.1 and only allowed stereo in the output as a result. Potentially the opposite is true for other titles so try this if games don't give 5.1 output. If you've a 7.1 aware amp and have 5.1 speakers you can safely set windows to use 7.1 and the amp will downmix the rear channels to what you have so this can assist as well (though once again some games may not see the windows 7.1 output as a valid surround output). All of these issues surrounding games are just related to poor game programming or lack of implementation of discrete surround. Consoles mostly got around this by having surround sound as a requirement for games to be released on them. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
HTPC Projects
Software
Operating System
Can't engage pro logic when windows is set to 5.1 via hdmi
Contact us
RSS
Top
Bottom