- DOLBY ADVANCED AUDIO V2 WINDOWS INSTALL
- DOLBY ADVANCED AUDIO V2 WINDOWS DRIVERS
- DOLBY ADVANCED AUDIO V2 WINDOWS DRIVER
- DOLBY ADVANCED AUDIO V2 WINDOWS REGISTRATION
DOLBY ADVANCED AUDIO V2 WINDOWS DRIVERS
Anyway CMedia and Cirrus HD audio chips are far fewer than HD audio chips from ADI/Conexant/IDT/Realtek/VIA and making the Dolby PCEE drivers work on Cmedia & Cirrus audio chips is not worth the effort. Fortunately on the Dell e1405 laptop, the Sigmatel/IDT audio chip is using HDAUDIO\FUNC_01&VEN_8384.Īlso the Dolby PCEE drivers won't work on C-Media HD and Cirrus HD audio chips because their hardware IDs are not listed there.
DOLBY ADVANCED AUDIO V2 WINDOWS INSTALL
Therefore the Dolby PCEE drivers won't install on IDT audio chips with VEN_111D because the INF files listed it as 11D1 when it should be 111D. This is incorrect! The correct Hardware Device ID for IDT Audio is " HDAUDIO\FUNC_01&VEN_111D". They mention IDT audio as " HDAUDIO\FUNC_01&VEN_11D1 IDT" I discovered a few flaws with the Dolby PCEE drivers with the INF files. The good thing about the Dolby PCEE drivers is that they do work through analog, HDMI and SPDIF audio connections. Both computers use Windows 7 x86 editions because these computers can't handle an 圆4/64bit Windows OS.
DOLBY ADVANCED AUDIO V2 WINDOWS DRIVER
Also, this occurred both on my desktop HTPC with an nVidia GTX 760 and on my Surface Pro 2 with an Intel HD4600, so I'm 99% certain it's a problem inherent to the driver itself, not my particular hardware config.Ĭlick to but I still do use 32bit/x86 Windows on two computers - on a custom built PC with an old Intel board with Realtek ALC861 audio and on my mom's Dell Inspiron e1405 laptop with Sigmatel/IDT STAC9220 audio. Not complaining or anything, but this hadn't been mentioned yet in this thread, and figuring out this issue and then troubleshooting it was a bit of a nightmare for me. You have to either rollback with a restore point or reinstall Windows.
Worse, simply uninstalling this driver will not restore HDCP validation. I presume the fact that it's an unsigned driver is what is actually preventing it from qualifying as a protected HDCP signal chain.
DOLBY ADVANCED AUDIO V2 WINDOWS REGISTRATION
For some reason this driver is seen as an 'audio repeater' by Windows, and this seems to disrupt HDCP registration (a sort of hardware DRM that's built into the HDMI specification and is required to playback most paid video content). I imagine it also breaks PowerDVD playback of Blu-rays, but I didn't test that. This completely breaks your HDCP validation chain, so if you install this driver, you will no longer be able to playback Netflix, Hulu, Amazon, Vudu, iTunes, etc.
0 kommentar(er)
