- Oct 14, 2012
- 2,401
- 1
- 91
I've recently noticed that for some reason Windows 10 doesn't support HD audio like Dolby TrueHD or DTS-HD at least with my setup.
It worked fine over HDMI from my graphics card in windows 7 but they simply aren't there in Supported Formats,
After seeing that my 5 month old receiver wasn't coming up as HDCP compatible in Nvidia Control Panel, which I'm sure it did in windows 7 (and taking a look right now it says it is), I found that by getting certain cheap HDMI splitters you could forgo the HDCP handshake and play content on hardware that didn't support HDCP.
The splitter arrived this morning but the HD audio formats didn't appear. I also heard crackling very time audio played so I've ordered 2x HDMI 2.0 leads that should be here by Wednesday.
The splitter itself supports HDMI version 1.3b, I don't think this should be a problem as it is only connected to my receiver. My monitor is connected via DVI.
Like I mentioned before, it now says both my monitor and receiver are HDCP compatible, and the logo shows they are locked in. I had initially thought that because my receiver didn't have HDCP 2.2 support, that would be the issue but it seems not anymore.
Has anyone else had these kinds of issues with Windows 10 or 8?
It worked fine over HDMI from my graphics card in windows 7 but they simply aren't there in Supported Formats,
After seeing that my 5 month old receiver wasn't coming up as HDCP compatible in Nvidia Control Panel, which I'm sure it did in windows 7 (and taking a look right now it says it is), I found that by getting certain cheap HDMI splitters you could forgo the HDCP handshake and play content on hardware that didn't support HDCP.
The splitter arrived this morning but the HD audio formats didn't appear. I also heard crackling very time audio played so I've ordered 2x HDMI 2.0 leads that should be here by Wednesday.
The splitter itself supports HDMI version 1.3b, I don't think this should be a problem as it is only connected to my receiver. My monitor is connected via DVI.
Like I mentioned before, it now says both my monitor and receiver are HDCP compatible, and the logo shows they are locked in. I had initially thought that because my receiver didn't have HDCP 2.2 support, that would be the issue but it seems not anymore.
Has anyone else had these kinds of issues with Windows 10 or 8?