1. Dana Goyette30 Jan 2014 @ 04:51

    Hmm, I'm now using my Xonar DX via PCI Passthrough to a Windows 8.1 VM. It works wonderfully, but I can't get the Asus Audio Center to open. There's no error message, or anything.

    I was previously using the sound card flashed to call itself a D1, so it would shut up about the power connector not being connected. Unfortunately, that tended to result in one side's front and rear speakers being significantly louder than the other side's. I've now fixed (re-soldered) the power connector, and flashed it back to identify as a DX.

    The C-Media panel will do most of what I want to do, but it won't switch truly on-the-fly to the front panel. (Having to kill all applications and restart the audio driver does not count as "on the fly".)


  2. Alexander31 Jan 2014 @ 12:08

    Hi from Russia πŸ˜‰
    Interested in this question:
    I use the Xonar DX
    Use Logitech z-5500 5.1 SPDIF
    And headphones Creative aurvana live! stereo

    How to set up channels?
    When using 5.1 speakers I put 8 Audio chanel and press SPDIF (Ingame settings need put 5.1 ?)
    And when i use my headphones I put 8 Audio chanel too? and put Analog Out - headphones (next I use Dolby Headphone)
    Ingame with headphones settings need set 2.0 stereo or 5.1 or 7.1 ? (if i use Dolby Headphone) ?

    Thanks πŸ˜‰


  3. Vladislav04 Feb 2014 @ 22:30

    Hi, i install 1.72 drivers for xonar DG on Windows 8.1, and when i run Battlefield 4 i have BSOD. I don't know why it's happens, but maybe you can help with this issue?


    • CarvedInside04 Feb 2014 @ 22:58

      Things you can do: Turn GX off if you enabled it for some reason. Then try different drivers.
      Disable Xonar card and try with the onboard card only.Your BSODs might not have nothing to do with the Xonar card or its drivers.


      • Vladislav05 Feb 2014 @ 18:12

        With onboard sound card all works fine. I try to find reason of bsod in memory dump and here is what I found:
        *** STOP: 0x000000d1 (0xffffd00046391ff8, 0x0000000000000002, 0x0000000000000000,
        *** cmudaxp.sys - Address 0xfffff80003028675 base at 0xfffff80003000000 DateStamp


  4. Nicolas H.08 Feb 2014 @ 23:35

    Hi, CarvedInside!

    I happened to have tested ASIO with a software called Studio One Free, and it worked with latencies below 10 ms. The only issue I ran into was crackling sound when using 32 bit depth in the ASIO panel or when creating a new file.

    Now, my test consisted in typing random keys on the keyboard (tested several instruments), so I wouldn't call it extensive by any means.

    Anyway, I'd like to ask a question. You decided to make these drivers because you were dissatisfied with Asus's implementation of C-Media drivers, right? Was bad ASIO performance among the things you reproach Asus's drivers with?

    I'm asking because I never tested ASIO with the stock drivers.

    Thanks in advance! πŸ™‚

    LE:Replying to myself to clear things up. I forgot to mention that I have a D2, which isn’t 32 bit capable anyway, so the issue that I mentioned in the above post wasn’t an actual one.


    • CarvedInside10 Feb 2014 @ 17:49

      You should read the UNi Xonar Introduction and UNi Xonar Features pages if you hadn't. There isn't an implementation of the drivers from ASUS, they aren't applying any changes or fixes to the original drivers from C-Media, the only thing they add is the ASUS Audio Center, which might actually be made by C-Media.
      I didn't made any changes or fixes to how ASIO works. ASIO from UNi Xonar works just as ASIO would work from a equivalent driver version and ASIO version from ASUS.


      • Nicolas+H.11 Feb 2014 @ 08:40

        So Asus didn't make the Asus panel... Interesting. Anyway, I had alread read the features page many times before commenting, and I was aware of the differences between the stock drivers and yours (which is why I'm using UNi :)). I was specifically commenting on ASIO since this page tells us to use 10 ms or above for ASIO.

        Anyhow, I had a strange BSOD issue pointing towards the Xonar drivers, so I rolled back all the way to the stock drivers β€” version 1794. While trying to reproduce the BSOD with the stock drivers, I thought to myself, "Hey, why not give that Presonus Studio One soft a go?" So I did do a bunch of a tests with Studio One, and, lo and behold, the sampling rate and bit depth weren't what I had set in the ASIO config panel. The sound would also crackle at times, probably due to that inconsistency. I didn't have these issues with the UNi drivers. Besides, I was able to set the ASIO latency to 1 ms and everything was fine.


  5. semtexxl22 Feb 2014 @ 22:38

    I tried fix listed here for flash sound upmix issue but later versions than my installed 11.3 are still upmixing anyway. Any suggestion what am I doing wrong?


    • CarvedInside22 Feb 2014 @ 23:06

      If you are using Win 8 or Win 8.1 it appears that the solution does not work for them.

      If you are mostly viewing clips on youtube, you can try watching the videos in HTML5 video player instead of Flash. To do so go to https://www.youtube.com/testtube and turn HTML5 Video on.


      • semtexxl23 Feb 2014 @ 02:58

        I'm on win 7 here. So I guess I need to find that post from adobe forums explaining reverting back to old system by editing some file....


  6. Daniel23 Feb 2014 @ 04:21

    Most soundcards, especially my DS has worse performance at 44.1 (most cards are native 48kHz), setting windows to 48kHz and allowing it to do its own sample rate conversion should produce better results than the onboard reclocking.

    Also never run Windows at higher than 48kHz, the DSP has terrible ultrasonic filtering (If you're using ASIO it should by pass the DSP), and any ultrasonics will produce Audible tones.

    Here is an example with everything set to 96kHz: http://i.imgur.com/zu9Kevt.png notice how the 24-48kHz range is reflected back in to the 24-4kHz range.


    • Nicolas H.23 Feb 2014 @ 13:31

      I've always heard we should set the sample rate according to the source, because up- or downsampling will result in quality loss. What are your thoughts regarding those claims? I'm asking because you seem to know your way around in the sound department.

      Anyhow, if I understand correctly, I should only use above 48 kHz sampling rate when using ASIO?


      • Daniel24 Feb 2014 @ 04:09

        Software re-samplers are very good (or very bad in some cases (see old game emulators for example), Microsoft includes a very high quality re-sampler with about -120dB noise floor (well below the -102~dB of my DS), (and double-blind tests showed no audible difference) if you're using ASIO you can use Foobar2000 inbuild resampler (PPHS) or look around for the SoX plugin, or if you're using ASIO for professional work, run everything at 96kHz and render your final 44.1kHz with one of the super-overkill resamplers built in to your tools (or use sox).

        http://src.infinitewave.ca/ has a bunch of tests to show any flaws, note that the noise floor of the measure is -180dB well below Brownian motion of a room temperature metal, in fact you're probably getting down to nano-meter movements of electrons.


        • Nicolas H.24 Feb 2014 @ 08:12

          Wow, you do know a lot about sound. Thanks for filling me in! Much appreciated. =)


        • Nicolas H.28 Feb 2014 @ 12:07

          Hey, I was thinking about something. Is what you said about sampling rate valid for bit depth, too (i.e. should I leave the parameter to 16 bit)? I've always been told to try and match the source's bit depth (e.g. 24 bit for DVDs).

          P.S.: Would you happen to be Daniel K.?


    • CarvedInside12 Mar 2014 @ 00:44

      I've checked out what you've said about setting the sample rate and how most soundcards have worse performance at 44.1 kHz. I have done RMAA audio tests on my Xonar DX card and I haven't found evidence that what you claim is right. I've ran many combinations cause your statement is a bit vague (you are only mentioning setting windows at 48kHz). Maybe things are different on DS, I don't know, but unless you can provide evidence to back your claim, I think everyone should rest assured that setting everything at 44.1 is the correct and best setting. Here are my RMAA results.


  7. Mezziaz25 Feb 2014 @ 22:57

    Any plans to add Xonar U7 support?

    Why I'm asking is because I just bought it and I can't get the mic input to work. All I get is constant static with my headset, does not matter if I turn the mic on or off. Worked perfectly with with my previous onboard sound solution.

    I have installed and reinstalled the drivers, installed the latest drivers from the Asus website and disabled the onboard sound through BIOS.

    If I can't get it to work I will probably end up returning it.


    • CarvedInside26 Feb 2014 @ 00:09

      No plans.
      In my opinion it's not the drivers at fault here, it's the card.


      • Mezziaz26 Feb 2014 @ 01:30

        Thanks for the response!

        Well I just tried the "Plug & Play USB 1.0"-mode and then the mic does work. There is no software where I can do tweaks and such though with that mode so I do think the problem is driver related.


  8. Will Z01 Mar 2014 @ 15:40

    Hello CarvedInside. I've installed the latest drivers, and followed your setup guide. However I'm unable to select 24BIT ASIO within my music player (MusicBee). The option is set to 16BIT and greyed out. I've set Windows to 24BIT. Any ideas? Xonar DX. Thanks.


    • CarvedInside01 Mar 2014 @ 16:20

      Hi. It's probably because you are playing music at that time, stop the playback and try to change it after that. If you still can't, then close the player and launch ASIO Panel with right-click on the C-media/ASUS tray icon, and change bit-depth from there.


      • Will Z02 Mar 2014 @ 16:36

        Thank you. I hadn't realised I could change the bit-depth from within the Asus software. Changing it there also changed it in MusecBee as well. Great stuff! πŸ™‚


      • Xue11 Mar 2014 @ 04:39

        I am trying to change my ASIO settings in Ableton Live. Whenever I open up the ASIO panel through Ableton, it shows 24 bit, 80 ms. This is a lot of lag (total of 240ms lag) and I want to change it to a lower latency, say 20 ms. It says changes don't take effect until I restart the application, so I do that. When it opens again, it's still on 24 bit, 80 ms! No matter what I change, after a restart of Ableton the settings are the same. If I launch the ASIO panel with right click on C-Media/ASUS tray icon, and change it there, the changes do not show up when I open up the panel again through Ableton, and it still lags. I've tried restarting the computer and updating my Live from 9.04 to 9.11, which didn't do anything. The problem seems to be with Ableton, since I've tried changing latency in FL Studio and that works great. Do you have any idea how to fix this? Thanks!


  9. constantin02 Mar 2014 @ 13:16

    I istalled win 8.1 clean and 1.72 driver not working on mai xonar d1, I tried in safe mod and it's the same, my onboard sound card is disable


    • CarvedInside03 Mar 2014 @ 19:34

      Try the possible solution 1 presented here and make sure you don't select "Digital signature bypass" in driver installer.


  10. Mike Jones05 Mar 2014 @ 23:12

    You mention setting Windows audio playback to 24-bit might improve sound quality. I'm interested in learning how this is possible. Could you maybe provide some examples from personal experience?

    I mainly play games on my computer. Most (if not all) games use 16-bit output for sound. Would changing Windows to Studio Quality (24-bit, 44100 Hz) improve the sound quality with games? Or do I need actual 24-bit recorded source material to hear a difference?

    The reason I ask is from what I understand, setting Windows to 24-bit for 16-bit material does nothing except add 8 blank bits of data. Again, this is just what I've read from research.


    • CarvedInside06 Mar 2014 @ 16:38

      Well, there are a bunch of topics and information on this subject on the internet, here is one.
      From what I've read, yes it could improve the quality even for those audio files that are 16-bit bit-depth.


    • Daniel07 Mar 2014 @ 02:11

      When you sum two audio streams together you get about 1 bit more depth (technically you drop the volume by -3dB), its not uncommon for a game engine to have 64-128 channel mixes, when lowering bit-depth (24->16) you apply dither (noise) to filter out any quantization errors, Windows uses 32bit internally (you can not do operations on 24bit numders on a x86 cpu), you may not get better quality, but in the end there is no downside, the only benefit is you might have a mildly lower noise floor.


  11. Patrick08 Mar 2014 @ 21:20

    Hi Carvedinside

    dont know where else to ask but ive been using your driver for a few years and everything worked fine until I started mining some bitcoin. After about an hour chrome crashed randomly and ever since then the driver could not detect the sound card. Before all this happened i could run my onboard audio and my DSX at the same time, but now the only way to get the sound card to work is to disable onboard audio. any idea what i can do to allow both to run at the same time again? Thanks.


    • CarvedInside08 Mar 2014 @ 21:34

      Which OS are you running? Which drivers you currently have installed? Have you tried with other drivers since the issue started?
      How is your Xonar card showing in Device Manager when you have onboard card enabled as well? Like if it's properly detected , does it show an exclamation mark. Tell me what it shows in its Device status under General tab.


  12. Nikos09 Mar 2014 @ 15:41

    Hi,I just bought the DG model. After i tried the asus drivers and had the card stop playing every 1 -2 hours i tried the 1.72 and have the same problem.
    I'm using XP 32bit.Just now i'm installing the (according to the descr) stable 1815 1.64 rev 2 and see how that goes.
    Anyone else had problems with the DG in XP ?


  13. Christian09 Mar 2014 @ 16:14

    Hey CarvedInside

    Having an issue where the driver crashes when selecting how many channels its supposed to run. I open the program and the part where you select channels is blank, so I click on it and select 8 channels, then it crashes. If I select any other number of channels it also crashes. I've had the same issue on the official drivers from asus and from your modification of the driver aswell, and I have no idea why. The odd thing is that if I uninstall the drivers, install them again, then the program works fine, I can select as many channels as I want, but after turning off the computer and then turning it on again, it stops working.

    OS: Windows 7 64-bit
    Soundcard: Xonar DX
    Driver version: 1.70 UNi Xonar (I have tried different versions of official asus drivers, haven't tried different versions of the UNi drivers though)
    Audio setup: Running optical out to a mixamp TX - Astro A50 headset.

    Any ideas? I'd love some feedback on the issue, I have been clawing at it for a few days now.

    Thanks, Bob.


    • CarvedInside10 Mar 2014 @ 05:23

      Hi. Haven't encountered this before. This is a long shot but you could check to see if your card's EEPROM wasn't overwritten. Info here.


  14. Nikos10 Mar 2014 @ 14:18

    Thank you for the immediate response.I'll probably upgrade to the D1 model.


  15. Sander12 Mar 2014 @ 18:29

    Hello. I installed uni xonar 1.72 with c-media panel. After that I decide to unistall Uni xonar driver and install offical 1794 driver. I run driverclean.bat as admin, restart system, run driver fusion, restart system, install standard driver. And after that instead of standart Xonar audio panel I still have 'C-media panel - UNi Xonar Audio'. I tried to uninstall driver again and install UNi Xonar 1.72 with standard Xonar audio panel with no effect. How can I completly remove UNi Xonar Driver with it's c-media panel?


    • CarvedInside12 Mar 2014 @ 19:22

      Very strange issue. Can you tell me your OS?
      Things you could try :
      1) Uninstall the drivers that are installed. Delete C:\Windows\system\Cmicnfgp.ini and the 3 files named "Cmicnfgp" with different extensions from C:\Windows\. Install the standard drivers again.
      2) Install UNi Xonar drivers again, select Normal installation and install them, then uninstall the drivers from Control Panel "Add and remove" or Programs and features. Restart, and install the original Xonar drivers.
      3) Use system restore to revert back to a date before you tried UNi Xonar drivers.


      • Sander13 Mar 2014 @ 10:06

        Windows 7 32-bit

        I search for "cmi" files on my system disk and find some Cmicnfgp files in "C:\" and "AppData\Roaming\ASUS". Also I manually delete HsMgr.exe in C:\Windows\system\ And this helps.

        Also I delete UNi Xonar driver cuz it always downsamle 96 kHz and 192 kHz to 48 kHz and do that even without anti-aliasing. I think you know about this problem?


        • CarvedInside13 Mar 2014 @ 16:34

          I don't know about of the downsampling issue. How do you know it does that?
          Just so you know, if it where true, that does not mean that older UNi Xonar drivers have this issue too.


          • Sander14 Mar 2014 @ 11:14

            Just set 192 or 96 kHz in windows and driver for play and record and start RMAA test for frequency response or (better) play and record some full range sweep tone (for 96 or 192 kHz sample rate). In audio editor you will see 23 kHz cutoff and aliasing.



Leave a new commentReply to comment

Comment received.
Your comment may be held for moderation. If it does not show up immediately, please be patient. Comments have to comply with these rules:
  • English language only
  • Don't post insults or threats
  • Try to keep the discussion constructive and informative
  • Don't post questions without doing a search beforehand

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.