thuandb Posted March 21, 2019 Share Posted March 21, 2019 I've experienced the same issue lately, Mutec DDC driver getting disabled no matter if F8 or driver signature or AO3 Driver Helper were tried. What I've found effective in resolving the disabled audio driver is running "AO -e" command, reset afterwards, do your own things (i.e. setting fix IPs, adjusting audio driver's latency & buffers, etc.), install and activate JPLAY, then finally run "AO -u". AO3 executed in express mode appears to inject something WASAPI-related to the system that facilitates audio driver installation. A good sign of audio driver properly installed is that a speaker symbol appears and stays unchanged next to the driver in Device Manager. FelipeRolim 1 WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted March 21, 2019 Share Posted March 21, 2019 7 hours ago, TubeMan said: when you set static ip. by netsh, windows clear all ip settings that's why you need to set GW and DNS You should have said this in the first place 😉 WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted March 22, 2019 Share Posted March 22, 2019 I updated both PCs to Windows 2019 Datacenter 17763.379 a week ago and found the sound a bit on the sterile, bright side, almost unbearable. Swapping in an OS disk of 17763.316 to AudioPC and music came back. A couple days later, out of curiosity I put the 17763.379 disk back into AudioPC, let it sit and play for less than a day and surprisingly found the SQ improved. Today, about a week after initial update, 379 on AudioPC is getting better and closer to 316 in musicality (subjective) but probably never the same. Lesson I learned from this humble finding: never judge, even a newly installed OS or newly ripped songs/album, right off the bat. Intead, let it sit in and play for a good few days. While waiting for AO3 final release with excitement, I look forward to this month-end's Windows Update which promises to fix an audio related issue. Until then, I hope we all continue to enjoy the music. FelipeRolim 1 WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted April 9, 2019 Share Posted April 9, 2019 I’d try this: Install the driver run ao -e run st -r Then check the status of the driver in Device Manager. WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted May 8, 2019 Share Posted May 8, 2019 I know a good guy in JPLAY forums who has successfully installed and been using WS2019 core on two NUCs. His screen name is taxman2. shahed99 1 WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted August 26, 2019 Share Posted August 26, 2019 Congratulations! Thanks for sharing the experience. WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted September 14, 2019 Share Posted September 14, 2019 Try to find an Intel NIC I-350. Better yet, JCAT FEMTO NIC for best SQ. WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted November 12, 2019 Share Posted November 12, 2019 I’d check the driver settings, latency and buffers. WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now