Harkius Sep 26, 2019 @ 4:03am
DTS Sound Unbound
Has anyone downloaded DTS Sound Unbound from the Microsoft store?
I managed to enable DTS for headphones (DTS Headphone:X) but there is no setting to enable it for the home theater (DTS:X).

Something went wrong while displaying this content. Refresh

Error Reference: Community_9745725_
Loading CSS chunk 7561 failed.
(error: https://community.fastly.steamstatic.com/public/css/applications/community/communityawardsapp.css?contenthash=789dd1fbdb6c6b5c773d)
< 1 2 >
Showing 1-15 of 28 comments
Cotivity Sep 26, 2019 @ 11:13am 
I've installed the trial but uninstalled it since I already use Atmos for theater and headphones. You're right though... I've attempted to have X kick in but it continued to read as 2 channel audio matrixed. Since I really don't need it due to Atmos, I didn't try to figure out why it continued to output stereo when fed an X test signal. Let us know what you find, if you go beyond the trial.
Bad 💀 Motha Sep 26, 2019 @ 12:53pm 
Just use the Windows Sonic option when you right click the Speaker icon. No need for useless crap from the windows store.
Harkius Sep 27, 2019 @ 12:45am 
Windows sonic is for headphones.
Like I said there is a setting to enable DTS Headphone:X (same menu as Windows Sonic) but there is no setting to enable DTS:X.
Bad 💀 Motha Sep 27, 2019 @ 11:24am 
Cause you don't have a DTS capable sound card. Realtek doesn't support that. Need something like Creative, Asus, EVGA
Harkius Sep 27, 2019 @ 12:44pm 
My Realtek supports DTS and my sound card supports Dolby and DTS but that's not the point.
There should be a setting near Windows Sonic to enable DTS:X, atleast this is what happened with Dolby Access IIRC.
Bad 💀 Motha Sep 28, 2019 @ 8:36am 
If it supports features like DTS then just enable it in the software or via Windows playback / recording
Harkius Sep 28, 2019 @ 8:43am 
The thing is: the setting for Dolby Atmos is near Windows Sonic, for DTS:X is not there.
Let's wait Cotivity
Last edited by Harkius; Sep 28, 2019 @ 8:43am
Cotivity Dec 26, 2019 @ 10:01pm 
Originally posted by Harkiter:
The thing is: the setting for Dolby Atmos is near Windows Sonic, for DTS:X is not there.
Let's wait Cotivity

UPDATE:

I went ahead and reinstalled after, ascertaining what I believe is happening with DTS:X vs Atmos currently...

"Atmos for headphones" doesn't seem to actually simulate channels unless it's being fed an Atmos signal...I may be wrong but I just can't seem to recognize any channel separation during use on non-Atmos soundtracks.

DTS:X, however, based on it's design is supposed to add channel separation and simulate height meta on even NON spacial audio...so I have been, after extensive testing been able to verify that while using headphones, it's working as designed. The issue is that there doesn't seem to be ANY streaming services that are using it so it's impossible to test the "X" part on my Atmos/X receiver.

So by buying it you are in essence future proofing on the home theater side but are able to use the headphone codec now for gaming, etc.
_I_ Dec 26, 2019 @ 11:58pm 
atmos does not use channels
it uss sound and locations, its up to the decoding device to figure out what channels are used for each sound
Revelene Dec 27, 2019 @ 1:21am 
The easiest way to get Dolby Atmos to your receiver would be to use HDMI or optical. When you use a sound card, most of those only have support for that decoding for headphones or optical, but not for analog. I'd say that is exactly why it isn't working, because you have something in the chain that doesn't support it.
Cotivity Dec 27, 2019 @ 1:47am 
Your thoughts are welcome but the OP and I aren't having Atmos issues...It's about the unique situation with DTS:X . Thanks anyway though...
Harkius Dec 27, 2019 @ 2:42am 
My problem was that there was no option to enable DTS:X (speakers) in the Windows menus.
Anyway, I found out that Atmos and X are useless unless you have speakers in the ceiling, also movies should be able to reproduce these signals without buying them.
Last edited by Harkius; Dec 27, 2019 @ 2:49am
Revelene Dec 27, 2019 @ 10:27am 
Originally posted by Cotivity:
Your thoughts are welcome but the OP and I aren't having Atmos issues...It's about the unique situation with DTS:X . Thanks anyway though...

Same concept. I'm willing to bet your sound card only supports DTS:X over headphones (software implementation, that anyone can use yay advertising) or optical, not analog.
Cotivity Dec 27, 2019 @ 7:35pm 
Originally posted by Revelene:
Originally posted by Cotivity:
Your thoughts are welcome but the OP and I aren't having Atmos issues...It's about the unique situation with DTS:X . Thanks anyway though...

Same concept. I'm willing to bet your sound card only supports DTS:X over headphones (software implementation, that anyone can use yay advertising) or optical, not analog.

In the case of DTS:X, no... What happens is it DOES in fact matrix a 2 channel (headphone X) codec into a spatial audio output via HDMI to my DTS :X receiver.

The issue which confused the OP (and myself until I figured it out) , is that since there essentially isnt a DTS:X encoded soundtrack in games/movies currently it simply wont output DTS:X ...only the headphone X matrix.

Atmos does the EXACT same thing in certain circumstances...it isn't a hardware issue, at least not for me since I have a full Atmos setup it is a chicken before the egg situation unique to DTS:X
Harkius Dec 28, 2019 @ 2:41am 
I'm not sure if you understood my problem.
Please check http://i.imgur.com/GSfm2Gn.png in that menù you can enable Sonic for headphones, Dolby Atmos for headphones, Dolby Atmos for home theater and DTS:X for headphones. The setting for "DTS:X for home theater" is MISSING.

Anyway they are useless for HDMI, like I said movies can reproduce Dolby and DTS without buying them, in games you can use PCM. Dolby and DTS are useful only for S/PDIF.
< 1 2 >
Showing 1-15 of 28 comments
Per page: 1530 50

Date Posted: Sep 26, 2019 @ 4:03am
Posts: 28