You are viewing comment page 71 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.
I have a question, I did try the v1.4 drivers first and now the 1.51 beta's which work ok more or less as I posted above. With the 1.4 drivers the ASIO driver window latency went down to 2ms and now with the latest beta's the same ASIO driver window only offers 10ms as the lowest setting. Can I ask why I am seeing this and is it my system or do we all see this.
We all see this only 10ms and above. Don't know why C-Media decided to change this.
When using the "Dolby Headphone" mode... what is the best mode for 3d games... Studio / Cinema / Hall ?
Just to be sure I got that right...In the FAQ for troubleshooting was mentioned that upmixing to 5.1 for stereo sources does NOT work on Vista/Windows 7 ???
What the ...?
Is it possible with the original drivers for my Xonar D1?
I tried your UniXonar drivers 'cause I wanted to get the best sound out of my card.
Its on by default with original drivers and you have to check a box to enable it in UNi Xonar installer.
The thing is that stereo upmix on Win7 works slightly different from Win XP. On XP if you set the output to 6 channels you always get the upmix (with original drivers)
While on Win7 it work if you set this settings in Xonar/Cmedia Audio Panel: audio channels:2 sound analog output:5.1 speakers , and not audio channels 6 and analog out 5.1.
IMHO If you want the best sound out of your card you have this disabled.
Also check Kado's post.
@everyone (upmixing stuff)
My audio setup before d2x was Winamp with Wumpus openal output for quad audio output (front and rear play the same audio) with a Creative SB Audigy 2 ZS, but openal+creative+multi therad cpu in windows 7 = bsod!
I changed to the Xonar D2X (stock drivers) and I noticed that stereo sound was always played in 5.1 and that was just horrible.
These drivers (unixonar) were really great as they restored audio to their supposed behavior, 2.0 as 2.0, 4.0 as 4.0, etc.
Now if you want to mess you audio just enable the upmixing option in the drivers setup.
Stereo music being played in 5.1 is just not right for me as the center speaker just mess everything.
For movies and anime (I mostly watch anime) with 2.0 audio track I upmix to 5.1 using Media Player Classic HC and ffdshow audio settings to a greater surround experience, this way you have control you your audio instead of having forced settings as those with stock drivers.
If it wasn't for the bsods I probably would still have the Audigy 2 ZS in my computer, although the D2X surely sounds clearer (but hardware acceleration was way better for the A2ZS as audio was really hardware processed and not software emulated).
Well that was just my opinion and if any one needs help setting Winamp and MPC HC just say it! 😉
Could you help me setup my MPC? I have a Xonar DG on the latest UniXonar drivers
Another question, can I ask when this latest test build will be made into a final release. Or the next driver release date. Thanks.
The 1.50 version has the experimental tag because it didn't had the valid catalog files for the driver files for Win7x64 and I had to used a experimental method so people could actually install them (with test mode and all).
Next driver? Probably when I get my hands on newer driver files.
Thanks.
Yes test mode was OK for me using my Windows 7 SP1 64bit for the install. I don't now use the C-Media control panel for two reasons 1. The FP headphones switch will only switch on and never off, and 2. I love a large shiny Hi-Fi style volume dial 🙂
I have noticed and was not to sure about the 1.50 driver's ASIO latency setting only allows me to set it at 10ms whereas the 1.4 allowed 2ms. Using the latency checker I get 30-100 μs (while running Utorrent as well) with odd spikes for things like pressing any button on my connected xbox360 controller or when Windows Live Mail (client app versions) plays a new email message sound.
Nothing but problems with this card (Xonar D1) and UniXonar drivers (v1.41) on Windows 7 32-bit.
Every second or third time I boot into Windows 7, there's no sound from the analog outputs. Only a reboot restores the sound to normal when this happens.
But that's not all - there's an even bigger problem with this card/driver/OS combination: After playing some music tracks (mostly MP3 files) in any audio or video player, the right stereo channel suddenly dies (no sound). Only a reboot restores the sound.
This is a much worse experience than the minor issues I had with the previous Creative card, which I dumped for this one.
Other things I noticed:
* I installed the driver with the low DPC latency option (ASUS control panel). When the driver installation finished, I didn't get a message to reboot the PC and the ASUS control panel was loaded in the taskbar tray. When I reboot the PC, the ASUS control panel isn't loaded on startup. Is this by design? That's with the silent install option.
If I untick the silent install option, I get the reboot prompt, but if I select 'Yes', the final step (check this box if you have a Xonar D1 card) is skipped and the PC reboots automatically.
* The Windows Driver details window shows that the driver is NOT digitally signed (CmiFltr, cmaudxp.dll and cmaudxp.sys don't have a certificate)
NOTE: I have WIn7 UAC set to full.
Sometimes the right channel is not completely dead (still playing, albeit at a much lower volume): http://vip.asus.com/forum/view.aspx?id=2010091602...
I stumbled upon this link:
http://vip.asus.com/forum/view.aspx?id=2011011017...
Looks like someone has modified the ASUS driver to fix this specific issue (see post #9)
Has anyone tested this build yet?
@r00k
only checked the posts today...
please get mpc and ffdshow from http://www.xvidvideo.ru/ and lav filter from http://xhmikosr.1f0.de
install them all.
add ffshow audio decoder to the external filters list and set as "prefer".
I'm assuming you want to upmix 2.0 to 5.1... i'll upload my preset and post the link later on.
check this pic for quick ffdshow settings http://img18.imageshack.us/img18/3985/ffdshow20to...
also just add lfe cross over and add it before the mixer just like in the pic.
sorry for the offtopic post.
thanks! sadly I can't try this out until the morning, but I'll let you know if I run into any issues
For the 1.50 release:
Anyone have issue about the test mode? it just don't work on my computer even when in the bcedit configuration it is marked as "yes" and no watermark appear.
The only way for the driver to load is by hitting F8 after the bios post and chosing "disable driver signature".
TestMode is totally borked for me on this particular Windows 7 install for some reason. It is enabled via bcedit, Group policy and the like. It just doesn't actually stick.
I suggest downloading ReadyDriver Plus as it will macro those steps for you automatically.
I have accepted it for the remainder of this particular install until my next clean Windows install.
Thanks for the suggestion but installing the .cab from qaz resolved the issue without the use of the testmode.
Just when I thought I could live with the sound off / channel muting issue of the ASUS (UniXonar) driver, the problems got even worse.
Today I experienced the worst ASUS driver issue ever - the dreadful noise bug.
I was watching a video in MPC Home Cinema with the sound playing through headphones (plugged directly into the front output jack of the soundcard) and the master volume set to a low, but still loud enough level (8%). Half way through the video, suddenly white noise blasted through the headphones at full volume. It was a shockingly bad experience - worse than a horror movie.
Imagine what this bug could do to your ears if you're using a pair of highly sensitive (>115dB/mW) headphones.
The horrible noise lasted for 2 minutes and then disappeared. It's definitely *not* a hardware issue, since setting the windows 7 master volume to 0% got rid of the noise / muted the soundcard during the noise blast.
ASUS drivers (and even the hardware) is made by brain dead monkeys.
Yes, even the hardware. Unlike Creative cards, the 'gold-plated' metal rings around the jacks of Xonar DX / D1 cards are nothing but cheap imitations made of plastic sprayed with a gold-like paint.
Also, they used solid polymer caps instead of electrolytics in these. That's why the bass sounds so harsh, not 'round and meaty' as in all Creative cards.
I'm just statisfied with my Xonar D1 🙂 The first soundtest blew me away ! Before I always used soundcards by Creative but since there's no working driver on Win 7 x64 for me (tried every solution on this planet) I binned that card and got the ASUS Xonar D1... What a difference in sound quality!!! It's pure pleasure to my ears!
So, no issues at all 😉 5.1 Surround Sound never sounded more lively on my rig...
Hardware = Check!
Software = Check!
Sound quality = Check!
Others have reported about that full blow sound (here). And it has the potential to permanently damage ones ears.
Thats one of the reasons Asus should be sued.
IMO the problems you've been having (this and/or the channel muting) might still be related to a hardware problem so better return your card for RMA.
But in this case, it's a blast of white noise (http://en.wikipedia.org/wiki/File:Whitenoisesound.ogg) at full volume, not that high-pitched screeching 'eeeeeeeeeeee' sound.
Use this file for validating cmudaxp.sys/cmudaxp64.sys of version 1796 for Win7: http://www.mediafire.com/?oz777rcjckyqau7
Manual way: signtool catdb cmudaxp64.cat
But I strongly suggest integrating it into installer instead of stupid test mode self-signing.
That file is the original one that comes with Auzentech 1796 drivers I have that, which is the one that isn't the valid one for 1796 drivers (I am saying this to be sure that we are on the same page).
I don't understand it how "signtool catdb cmpudaxp64.cat" is supposed to fix this. Please explain.
It seems you don't understand how driver signing works on x64 Win7/Vista.
It works this way:
1) Unsigned drivers (.sys) aren't loaded until you switch system into test mode (and open pretty big security hole by doing so).
2) Unsigned .inf files result in complains when installing, but works fine.
3) Our specific: .inf files are the same for each version and differ only in unimportant text string (date/version).
4) Usually files are not signed by itself, but rather their signing is stored in .cat files.
Actual drivers (.sys files) of 1796 version are properly signed (in that .cat file) and can work without any test mode perversions. But as they came not from ASUS we have no relevant signed .inf files for them. As explained, it's not a problem and you can either ignore that they are unsigned, or use signed .inf files from earlier versions with additional .cat file from there (1793 WHQL recommended).
With "signtool catdb" you can directly add (and remove) .cat files to system database without installing/uninstalling anything. So having previous version installed, just execute that command, replace relevant .sys file - and everything is signed and works fine.
Thank you for taking the time to explain some things.
A while back, some .inf files got messed up and ended up being unsigned, some people managed to install the drivers and some didn't. Virus helped me out with that and with 1.41 drivers everyone could install the drivers. This is why I signed 1.50exp1 this way. So for whatever reason, point 2) is partially true.
I have a dilemma thats bugging me and maybe you can help. You said that the .sys files from 1796 are properly signed in the cat file, but how did you check this? SHA-1 from the cmudaxp64.sys is different from the ones stored in the cat file, and the same thing is for lets say cmudaxp.dll. This is the same with 1794 1.41 driver files.
I recently managed to figure out the date/version of the xonar infs that where used when the 1796 .cat file was generated, but I wasn't sure about the signature for the .sys files.
Ok, now I think I understand what signtool catdb does. In driver installer use signtool catdb CMUDAXP64.CAT (1793 one) and start the installation of lets say 1796 with 1793 xonar infs. Right?
The sad thing is that singtool seems to be that isn't a redistributable tool and this might pose a problem.
Looks like you understand the main idea now. ^_^ Your installation scenario is exactly how I had it in mind. There is some more specific stuff like WHQL, but it's not really important to make things work.
SHA-1 used by MS in signing when computed over PE file (exe, dll, sys,...) skips several areas, so regular tools won't do. Over other files (like .inf) they are the same. The mentioned signtool can check the signature and compute this kind of hash.
It would be nice if you can guess the changes in .inf to be validated by 1796 .cat, but I wasn't able to (it isn't sys build or release date).
The other problem is it seems that uninstallation doesn't remove all old files on Win7: there are files left in WindowsSystem32DriverStoreFileRepository... and some records in some system dbs. They are removed when you uninstall the driver with pnputil -d, so just deleting files in system32 isn't true uninstall.
The signtool catdb might come in handy someday.
Regarding the changes in .infs , it was 03/10/2011,7.12.8.1795 instead of 03/10/2011,7.12.8.1796. But don't know how I missed it the first time I got my hands on the 1796 drivers.
You are right about the remaining driver files files, will see what can I do with pnputil -d and maybe add it to the installer cleaning routine.
Thanks for the help.
Indeed 03/10/2011,7.12.8.1795 verifies with that .cat, but it makes no sense at all: date equal to 1794 (that was actually built on 2011.03.10), when .sys file is built on 2011.06.04, has in-file version 1794 and Auzentech package named 1796 2011.06.21.
Probably, this version should be called 1795 as nothing inside files says 1796.
About ancient driver in each installer: is it really needed? I understand what it for, but not the reason to add it for each new version. It should be one separate installer as nothing changes there (and I doubt if there are more people who need it or people who accidentally (re)install that version).
I also got my hands on 1795 drivers, and can tell that 1796 auzentech drivers are compiled after 1795. 1795 was build on 2011.05.21.
The stupid thing here is the 1796 azntech .cat doesn't contain the signature for other cards except 1795 asus ones.Its clear that Auzentech/C-Media screwed up when compiling 1796 driver package.
In 1795 .cat contains all signatures except for HDAV.
The ancient driver in the installer is used for ASIO Patch. The no 1 reason I still add it to each version is that you can get new UNi , GX and Audio Panel fixes even while using this older audio driver because of ASIO 1.0 compatibilty. Will think about how it your suggestion.
I replaced my .cab file with yours uninstalled and deleted my previous driver, after this i reinstalled the new driver with your .cab a pop up appeared telling me if i want to install the drivers or not i chose yes and everything worked fine.
Thanks.
UniXonar v1.41 - in the Cmicnfgp.ini.imi file, there's a typo (HARADWAREID instead of HARDWAREID):
INSTALLED_HARADWAREID=PCIVEN_13F6&DEV_8788&SUBSYS_834F1043
It looks that line is generated from by cmedia/asus installer.
Im not sure if its a good idea to correct this, it might be only recognized this way, try and see if something changes.
Don't think its of much use as that file might be used only by Asus Xonar Audio Center, if its ever used.
There are three .ini(.imi) files created by the installer. One is located in the /Windows/System folder, one in /Windows and the last one is in Username/AppData/Local/VirtualStore/Windows.
All of them have similar contents and at least two typos.
UniXonar driver for windows8 please..
Try running the installer(1.41) in Windows 7 Compatibility mode (Proprieties->Compatibility->Compatibility mode).
Thank u so much qaz! u the hero!!! everything works nice now with the new .cat file and without test mode! thank you so much!!!!!