You are viewing comment page 179 of the post. View the post contents here.
Tip: Press Ctrl+F to search for a specific keyword or keyword combination.
We've noticed that you're using an AdBlocker
It's not just you, over 66% of our site's visitors are blocking the ads.
Please disable adblock for this website and refresh this page if you:
find the content useful
want us to create more useful content and software
want tech support through the comment section
The ads are placed so that there is minimal interference with page reading. There are no pop-up, pop-under or sticky ads.
Alternatively, you can support us by making a donation.
hello thanks, great drivers, on my essence stx on win10 (c-media install/panel type) i got just few problems with asio crash sometimes on fl studio, that seems is not present on the originals ones (but they sux alot not only on asio!)
did it's cause the original asus drivers are a more updated version? (sign is september 2015 vs lastest uni xonar june 2015)
ASUS original drivers are not newer than UNi Xonar drivers. In this case, if you've installed 1.80a drivers both use the same audio drivers (version 1823) and same ASIO driver component version. I don't see any reason why ASIO output would work better with ASUS original drivers. Maybe the conditions on which you've tested are different like other program running or some newer windows updates where applied. You should do a drivers uninstall and reinstall the UNi Xonar drivers with driver cleaning option enabled in case something when wrong the first install.
Hello there.
I just found this on the web. Is this going to have any kind of impact on your UniXonar drivers in the latest Windows 10 Anniversary Update?
http://www.pcper.com/news/General-Tech/Windows-10-Version-1607-Changes-Driver-Signing-Policy
I get the issue. Drivers are not longer available with Win 10 1607.
A message about card power supply appears always when you try to launch audio center,...
Did you make a clean Windows 10 b1607 installation or a update from a previous build?
If you go to Device Mananger, does the card shown as installed under "Sound, video..."? If it's shown as installed what's it say under Device Status if you double click the Xonar card? Thanks.
I made a clean install with format. The drivers installed normally without an issue. The card appears in Device Manager and everything works. (I'm a normal user games,flacs,mp3s). I didn't notice anything strange yet. Everything seems ok for now. Will this impact any future UniXonar drivers (If you release any)? I'm asking because I don't quite understand what exactly they did with the signing and if this will affect "unofficial" drivers like yours or not.
Thanks for the feedback. I don't know if it will be a problem since there are many conditions and exceptions to this new driver signature enforcement policy. If it will be a problem then it would be for ASUS original drivers as well since I use the same driver files and digital signatures as they do and the changes I made to the drivers where to the configuration files not the driver files.
I've been using the drivers fine as an Insider for some time now. I've had issues with some stuff like newer AMD drivers (which can be worked around by turning Secure Boot off), but no issues whatsoever with the Uni's.
Thanks for the feedback.
Some more feedback for Windows 10 Anniversary Edition in combination with UNi Xonar STXII 11.5 v1.80b r3 (Mainboard: ASUS Maximus Formula VIII, BIOS 1902):
- The drivers were indeed *disabled* after the update.
- However, after rebooting with driver signature enforcement disabled, they could be re-installed without a problem
- The STX II is recognized without any issues (currently in Low-DPC mode)
- MicMute / XonarSwitch are functioning flawlessly, too
Thank you for this, by the way. Absolutely great stuff!
As I know, older drivers than 09-2015 still will be installed. Even if they are self signed.
But nobody knows what future Win updates brings - it looks like the beginning of a big plan to make windows bsod free (does not work very well on my machine, even with sign drivers there are usb caused bsod´s 🙂
Im not 100% sure about the policy, but unixonars works fine on my machine, with a fresh install of 1607 Anniversary...
If not on your machine, try to disable secure boot in the uefi (can cause security problems if you don´t have brain.exe installed 🙂
BR
Xonar DX on Anniversary Edition, clean install, no problem installing driver, did not even had to disable driver signature enforcement and drivers seems to work perfectly.
P.S: I am new to this though, front panel audio doesn't seem to switch automatically, is that normal? Thanks
Thanks for the feedback.
Regarding the front panel switching automatically, the Xonar DX does not have this capability.
awesome drivers. installed flawlessly on win 10 anniversary with the "reboot to "Disable driver signature enforcement"" method. I only had a small problem with AVG - it detected CmeAuVist64.exe while installing the drivers. had to add the exe to the exceptions.
Thanks for the feedback. Did you try installing the drivers without rebooting with “Disable driver signature enforcement” and it did not work? Which driver version have you installed?
sry, for the later answer. yes, I also tried to install your latest drivers normally after the anniversary update because the card wasn't correctly recognized anymore. but it didn't work, the setup ran ok without problems but didn't have any affect.
upgrade keeps them clean fortunately...
It's unclear what are you trying to say. Please clarify.
I've a very high DPC latency even if I use the Low-DPC install method - 1000µs (1.0 ms) for watching a 1080p movie in VLC!!
I'm using LatencyMon for monitoring & it says I'm getting audio crackling etc.
My soundcard is the Asus DG & I'm using Win10 64bit.
In this case your problem might not be from the soundcard and it's drivers. Other drivers can cause a high DPC latency. Recently, drivers for Nvidia GTX 1060/1070/1080 video cards are causing high DPC Latency. With LatencyMon you can view which drivers are causing this high DPC latencies. You should also read The case of DPC latency – 4.Tips & tweaks in reducing DPC latency.
Updated to the Windows 10 Anniversary update. Drivers still work for me.
They did say that only for Clean Installs would it not work. But if you just do a plain upgrade from an existing install, it will still load your older drivers, signed or not. Meaning if you want to do a clean install of Windows 10 in the near future, you should do it with an ISO from before the anniversary update, install your drivers and then update to the anniversary update.
Thanks for the feedback and the information posted.
you can also just disable secure boot and unsigned drivers will work also with clean install
i've upgrded too and while the drivers are working the volume is very low for some reason.
apparntly the problem is with mpc-hc stable build and not with the drivers. mpc-hc nightly works fine.
For me the latest driver works well from update to Windows 10 Anniversary update!
but i have to clean install my system on Windows 10 Anniversary update and after installing the latest build the microphone is not working anymore 🙁
are you guys working on an fix?
Update:
Ok it was my mistake. How to Fix:
Front mic was set as default in Xonar Settings. Changing to “normal” microphone works now.
So After clean installing latest WINDOWS AU drivers work without any problem Asus Xonar DGX
I had Uni drivers and updated with anniversary updates. Everything still working perfectly 🙂 Haven't tried reinstalling though.
Well this is an awesome update. When my entire system isn't locking up randomly, half the time my Xonar DGX isn't even detected by Windows on boot. I even had it disappear while the system was up and running. Never had a single issue until the AU.
Thanks Microsoft.
We are only playing music with Foobar and ASIO (no interaction with the system while playing) We always used uni-xonar drivers to good effect with the mark one xonar card on w10.
We installed the Asus official drivers with the new mk2 card and all sounded very good. But for the sake of comparison, we just tried un-xonar drivers (low latency) with our new card. I expected no change in sound but hoped to reduce the ASIO latency (on this hardware we get dropouts at lower levels).
Whereas uni-xonar is very natural sounding it seemed noticeably 'more distant' (meaning probably a touch more mid tone, or perhaps less precision in the top end. This was not a side by side comparison - therefore we could be deluding ourselves. Is it likely we were? There were definitely some changes - with uni-xonar there was a click when starting a song which does not happen with the Asus driver on this system.
The uni-xonar driver did not permit us to reduce the ASIO latency setting to any good effect. We ended up getting clicks and drop outs at around the same level where we did with the Asus driver. Tried 32 bit and as per your advice, it sounded worse than 24bit which is what the card uses. I heard that 32 might be good since the data channel on the motherboard would be 32.
We have reverted to the official Asus driver again.
We have never noticed any change in sound quality with either drivers when setting the ASIO latency very low (80, where we get almost no clicks etc). Is there any advantage in sound quality terms for low latency for cached streaming music on a machine where there is little user interaction and minimal background processes interrupting?
It seems common sense that low latency is required in most other circumstances.
thanks for any thoughts
w10 1607 clean install
UNi-Xonar-1822-v1.75a-r2
installed ok and working fine so far
Thanks for the feedback.
I have installed the 1.80a drivers on my Xonar and there were no issues. Low DSP setting. However, this isn't a clean install, I reinstalled over existing drivers so I can't confirm 100% this is always working for all Windows installations.
However, to remove the balance bug (Right speaker was way too low volume) I had to manually delete HsMgr.exe from the Windows folder, then reboot. It's like magic. Now everything is crisp and clear.
The only plaguing issue I have is sometimes the card goes into "RANDOM MAXIMUM WHITE NOISE MODE" and screams out of nowhere. If I have headphones, it's instant panic. I strongly suggest you keep your hardware settings as low as possible and increase your software levels instead so that when it happens, it's a lot less worse. If you keep your amped speakers very high, it's going to jerk you off your seat.
In essence after all this I strongly discourage anyone from buying a Xonar chip. It's an excellent piece of hardware no contest, but the driver implementation leaves to be desired. If I didn't have MaxedTech, I would have snapped this card in 2, literally. In my hands. I also overpaid a bit for it I admit, 130$. Saw it on sale on the internet for 100$ after that. I guess its even lower now.
I'd use my on-board sound, but there is a bug with Stereo Expansion where it doesnt work unless I pick an EAX Environment. It's terrible.
By "Low DSP setting" you mean Low DPC Latency? Cause if you've installed drivers with "Low DPC Latency" or "C-media Panel" configuration then the HsMgr.exe is practically deactivated and deleting it from Windows folder doesn't have any effect at all.
Your feedback is based on using Windows 10 or Windows 7/8?
Sorry yes Low DPC. I preemptively deleted it because I had problems last time with another setting. Thank you.
I just did a clean install of Windows 10 (1607), and it seems like I'm able to install the 1.80a driver without any issues. I didn't have to disable secure boot, driver signature enforcement, or anything like that.
Thanks for the feedback.
I installed 1.80a/b version for win 10 pro anniversary. I can't get my mic to work. Phantom power gives power and the mic is ok. I'm using rear panel and using the microphone as input source at Xonar control panel. Still no audio after reboot or reinstalling drivers. Any ideas?
Problem solved, cables a broken inside the phantom D: