11-21-2017 05:20 AM - last edited on 03-05-2024 08:19 PM by ROGBot
07-08-2018 06:53 PM
a.l.timmons wrote:
Yea, I am trying to figure this out now too. This whole process is opaque as hell. Never really explained.
Summary: TL; DR, there seems to be 3 options-
The cracked OEM Driver here, where newest is at the top
A cracked version on tech power up that also includes other software- (Some sound blaster stuff)
https://www.techpowerup.com/forums/threads/unlocked-realtek-hd-audio-drivers-windows-7-8-with-dolby-...
- really confusing there too- 112 pages of banter to pick through. Its always hard. Start at the end and go backwards- nothing makes sense but you dont miss the critical update on page 49. Or at the beginning, and understand, but be 4 years behind.
Theres also a replace patch that seems to replace 2 files in the system directory. https://www.techpowerup.com/forums/threads/unlocked-realtek-hd-audio-drivers-windows-7-8-with-dolby-...
So, I haven't figured out differences yet, or even if it makes sense for me to do this. I don't use digital output. I don't have any headphones yet that are worthy.
Several of those guys link over here.
07-31-2018 02:05 AM
08-07-2018 08:44 AM
08-08-2018 06:06 AM
Calibos wrote:
Arrgh. Been pulling my hair out the last few days with all the hacked driver malarley and hoped that this thread was my salvation.
I've an Asus Z170-A mobo running windows 10 April update. I recently bought a new Receiver for the livingroom Home theater which freed up an old Sony DB930 Receiver for my PC/VR room. I bought myself a lovely KEF E305 (Eggs) 5.1 Speaker system. My intention was for the Realtek Integrated audio chipset on my mobo to do all the encoding/decoding work and feed the old Sony Receiver the 5.1 channel analogue signal, effeectively only using the Receivers Amplification and not using its old Dolby Digital or Pro Logic 1 decoder over optical/Toslink. The latest HD audio formats like Dolby TrueHD and ATMOS are only possible over the analogue outputs anyway. So I can play TrueHD etc movie soundtracks via Kodi and my Realtek 5.1 analogue outputs, through the 5.1 speaker inputs of my old receiver. Worked as expected. Great!! However I was frustrated to find that the Realtek drivers did not support Psuedo Multi-Channel like Dolby Pro Logic 2 for Stereo sources. Thats what sent me down the hacked drivers rabbit hole from which I only have just recovered. Nothin workedf needless to say.
I thought my salvation was here. Have deleted all evidence of the hacked drivers I installed the drivers here with Asussetup and then the latest MS catalogue drivers. My problem now is that while I have the Dolby Pro logic 2 tab when I tick the box the Apply button remains grey'd out and I cannot click it. Not only that but with these drivers I lost the Bass management tickbox on the Realtek app and while my subwoofer works when clicking the speaker icon test tones, when I play 2 channel audio content like a youtube vid, not only am I not getting Pro Logic 2 Psuedo Multichannel, I'm only getting Front left and Right Stereo 2.0 but my Subwoofer isn't outputting any sound either so I'm not even getting 2.1 nevermind 5.1.
Literally all I want from the realtek drivers that I didn't have as standard is Pro Logic 2 Psuedo Multichannel for stereo sources like music or 2 Channel Movie/TV Shows outputting over the Realteks analogue 5.1 outputs to my old receiver.
Can anyone help. I'm pulling my hair out at this stage!!
[EDIT] Sorted it myself....by reverting back to standard drivers. Turns out the included DTS NEO PC DTS Connect does exactly what I want and the reason it was having no effect on the sound was that I was using Youtube on Chrome. WHen I finally demo'd a stereo movie file on my PC all of a sudden I was getting sound coming from my Centre and rears. Then I tried the youtube music vids again but in Microsoft Edge browser this time and DTS Neo PC was working on that too with sound coming from all my speakers. So I knew it wasn't a problem with my realtek drivers nor with youtube but bloody Chrome!!!
Turns out there is a bug in Chrome that outputs a 5.1 flag even when the audio file playing in chrome is only stereo. What this flag does is tell DTS NEO PC that it need not do its Psuedo Surround thing because a genuine 5.1 file is playing....except of course its only 2.0 but the flag stops Neo PC. First results for a solution was to add --force-wave-audio to the Chrome shortcut target but then readf posts from people saying that Google had broken that method too with an update last year. Finally found a working fix.
Type chrome://flags/ into your chrome address bar. You get a page called experiments use at your own risk blah blah
In the Search Flags search bar enter: Causes audio output streams to check if channel layouts other than the default hardware layout are available.
Enable
(Causes audio output streams to check if channel layouts other than the default hardware layout are available. Turning this on will allow the OS to do stereo to surround expansion if supported. May expose third party driver bugs, use with caution. – Windows)
Thats it. DTS NEO PC now worked on youtube in chrome with Psuedo 5.1 coming from all my speakers. Thats all I ever bloody wanted and it was always available to me in the standard drivers all this time it just wouldn't work because of a bug in Bloody Chrome!!! Wasted days on this!!
10-22-2018 08:05 PM
10-25-2018 08:35 PM
10-27-2018 01:41 AM
10-27-2018 01:02 PM
Hurricane28 wrote:
Nice!
I guess this also works on the C7H? It has the same codec. Thnx.
10-27-2018 03:09 PM
01-22-2019 02:48 PM