sprite

7531 Comments

  1. August24 Aug 2016 @ 23:40

    ASUS Xonar D1, clean Win10 64bit Anniversary installation, UNi Xonar 1816/1823 v1.80a r3 installed without any issues. 24bit/192kHz analog 5.1 speakers working perfectly, as well as front panel headphones (flawless transition using XonarSwitch).

    Reply

  2. Bahlouda28 Aug 2016 @ 23:29

    Asus Xonar D2, Windows 10 Anniversary Update, UNi Xonar 1816/1823 v1.80a r3 installed without any issues. Stereo OK, analog 5.1 not working but Digital 5.1 seems to work. All was working on previous Windows 10.

    Reply

    • CarvedInside30 Aug 2016 @ 13:14

      Thanks for the feedback. When you say “analog 5.1 not working” can you explain what exactly is not working (all speakers, one of the speakers, speakers are mismatched,etc.)?

      Reply

      • Bahlouda01 Sep 2016 @ 00:57

        While (not) messing with Windows configuration (anymore), this is working now. But when it wasn’t working, it was like, some sounds were working (those added to movies) but voices didn’t.

        Reply

  3. martino cesaratto30 Aug 2016 @ 21:56

    asus xonar d2x, windows 10 x64 anniversary update, UNi Xonar v1.75a r2 -> updated to v1.80a r3 but the problem wasn’t solved (did 3 clean installs with disabled signature enforcement). Since the anniversary update, i’m unable to use more than one sound source at a time, meaning that for example, if i play music and i start a game, the game sound won’t work, even if the music is paused. As soon as i close the music player the game sound starts to work again. In the windows mixer the non-played sound shows up correctly, but for some reason it isn’t audible. Also every time i open an application that can play sounds when one is already open, i get few seconds of distorted audio from the already opened one, if that could help finding out the problem.

    LE: After some further testing, the problem is only with foobar2000, if it’s closed i can play youtube and games sound together, also i forgot to mention it all started with the anniversary update

    Reply

    • martino cesaratto01 Sep 2016 @ 02:08

      continuing to test: the audio just doesn’t seem to work with some programs, namely teamspeak, games (project cars, assetto corsa, raceroom), chrome, while it seems to always work with foobar, but when foobar uses it, no other program will play any sound. whatever sound doesn’t get played, shows up in windows mixer. Sometimes the audio won’t work even with foobar closed, but closing and opening all sound-using applications make it work again most of the times. one single time i had to reset because i was getting few secs freezes every time something wanted to play a sound, coupled with distorted sounds played, that time not even foobar or windows test sounds in configuration were working, but everything was still showing up in the mixer

      Reply

      • CarvedInside01 Sep 2016 @ 19:08

        Maybe you’ve switched to ASIO or WASAPI output device in foobar2000 and that is why sounds coming from other applications do not work. Check that and switch to DS (Direct Sound).
        For other problems try 1.75a drivers again.

        Reply

        • martino cesaratto01 Sep 2016 @ 21:01

          Thank you, it fixed the main problem, but i still have some looping sounds issues when opening/closing programs, but they happen rarely

          Reply

  4. Dylan31 Aug 2016 @ 01:47

    Hi there,

    I’ve just bought an 8 inch subwoofer to with my M-Audio 80 speakers. I used an adapter to plug the sub into the “center” channel of the soundcard while the speakers are plugged into the “front” channel. The speakers sound great of course but no sound is coming from the subwoofer. There is no setting for 2.1 sound, and setting the flexbass crossover only affects the speakers. What gives?

    -D

    Reply

    • CarvedInside02 Sep 2016 @ 09:05

      Hi. Connecting a subwoofer directly to the soundcard is not a standard 2.1 speaker configuration. In a standard 2.1 speaker configuration you connect the subwoofer to the speakers or amplifier. I’ve come up with a workaround that could make it work.
      Guide for Windows 7/8/10:
      1) Connect subwoofer to Center/Subwoofer output jack
      2) You need to have “Stereo upmix” enabled. Depending on your setup you either have to install drivers installed with “Re-enable stereo upmix to 4, 5.1 & 7.1” option checked or enable it in XonarSwitch.
      3) In the audio panel set the following: 2 channels and 5.1(or 6) speakers.
      4) If subwoofer isn’t sounding right, exchange center/bass channels in the audio panel.
      5) For speakers and subwoofer bass management look at the FlexBass option in the audio panel.
      If you have Windows XP then there is a different guide for that.

      Reply

      • Dylan02 Sep 2016 @ 21:58

        Before I saw your suggestion I set it to 5.1 and the bass starting working. The only difference was the sound became slightly quieter from the speakers. I’m not sure if it’s set up right but it sounds great so that’s good. I installed the XonarSwitch for good measure and played around, and the “Analog upmix via Dolby PLIIx” option didn’t seem to affect much so I’m going to leave it off. Love the drivers!

        -D

        Reply

  5. st0neh31 Aug 2016 @ 08:57

    So no matter what I do my Xonar DGX just flat out isn’t detected by Windows 10 AU more than 50% of the time, and if it is detected then it causes the system to hard lock up in use constantly. Windows Audio is pegged at 50% CPU in task manager, I assume because the card has just disappeared from the system (I’ve sat and actually watched it disappear from device manager in Windows. It’s so bad that the lock ups have actually managed to break the filesystem on my Windows 10 partition requiring a complete re-install.

    The card worked perfectly fine in the 1511 build for close to a year, and also works perfectly fine in Windows 7.

    I don’t even know what to say at this point. How do you break an OS so hard?

    Reply

  6. Mark01 Sep 2016 @ 15:23

    Quick question probally been asked before but thought i would ask.

    I have win7 64bit with xonar dg currently running last available drivers from ASUS which version should i download in terms of working/stable

    Reply

  7. Mr.sprinkles7901 Sep 2016 @ 23:54

    Hey people ive got a MAJOR issue going on with my dx. When playing audio at any volume very intermittently.. my system lets out a BLAST of white noise/static at FULL VOLUME.. i run the analog outputs straight to class d power amps.. rated at 300watts per channel.. Its going to give me a heart attack. Now 95% when it does this its from starting Youtube videos. It does it randomly and without any other symptoms(poping static ect). it will blast when i start a video and click the progress bar more than once..or on its own. or not at all. It hasnt done it in a few months. But has the last two nights. it blasts lasts for about a second then again every 3-4seconds till i close the player. again the only other time its done this once or twice in netflix and jriver. even once start the fallout3 launcher. but 95% its playing youtube. when i close whatever, i can her the cards relays click on. any ideas? it puts me into a cold sweat.

    Reply

  8. taclight05 Sep 2016 @ 12:08

    Hey today the sound for navigating through folders suddenly turned to that scratchy noise again, tried re-installing both the recommended and the latest driver with no success, please help

    Reply

    • CarvedInside06 Sep 2016 @ 22:34

      Tell us your OS, audio card, version of the UNi Xonar drivers installed and if you’ve set a different sample rate than 44.1KHz?

      Reply

      • taclight10 Sep 2016 @ 00:34

        Win7, asus xonar dx, default settings – this is a general problem with this specific sound and the sound card (navigating folders), you can find tons of posts online. The most reasonable fix to this problem is the one I suggested (edit the .wav in C:\Windows\Media)

        Reply

  9. Steven05 Sep 2016 @ 21:01

    Using UNi-Xonar-1823-v1.80a-r3.exe with Xonar Essence STX soundcard. Using ASIO with JRiver Media Player, W10 Ann. Update x64. Getting random bluescreen’s cmudaxp.sys error.

    Any fix for this as very annoying. Only happened three times in the last few weeks (use PC a great deal).

    Thanks

    Steven

    Reply

    • CarvedInside05 Sep 2016 @ 22:25

      Have you enabled GX by any chance? If so disable it. Other things you should try:
      Install the drivers with “Low DPC Latency” or “C-Media Panel” configuration and see if you still get the bluescreens.
      Install the v1.75a drivers.

      Reply

      • Steven06 Sep 2016 @ 11:57

        Many thanks for the helpful advice. I’ve now installed v1.75a with Low DPC Latency selected, in test-mode. (I tried the Windows Advanced Start-up method, but my keyboard locked when trying to select the number 7 (unplugged it and tried another usb port and keyboard, also locked with number lock light on!)

        I’ll report back here if I get the blue screens again.

        Reply

      • Steven06 Sep 2016 @ 18:29

        Another blue screen! Now reinstalled again with “C-Media Panel”. GX has been selected.

        Any other suggestions if I still get blue screening?

        Reply

        • CarvedInside06 Sep 2016 @ 22:31

          “GX has been selected” – I don’t get this part. If you’ve installed the drivers with “C-Media Panel with GX enabled” it is not good, it will likely show more blue screens. Anyway, if installing the drivers with “Low DPC Latency” configuration still showed blue screens then you will get them with “C-Media Panel” configuration as well.
          When you run the v1.80a driver installer (without going on with the installation), on the second page does it autodetect the STX card or does it detect it as a different card?

          Why do you install the drivers with Windows in “Test mode”? Don’t the drivers install without it?

          Reply

          • Steven06 Sep 2016 @ 23:50

            Sorry – typo – I meant to say GX has NOT been selected my error.
            Correct v1.80a would not install on Windows 10 anniversary edition without the test mode, as noted above.

            Please note I installed “UNi Xonar 1822 v1.75a r2.exe. Is that the one you wanted me to try???
            NB: I selected my STX card from the drop down list on the installation screen.

            Any other ideas?

            Reply

            • CarvedInside07 Sep 2016 @ 03:03

              Yes, v1.75a r2.exe I wanted you to install. I suggested you to try v1.75a and I’ve asked if you run v1.80 installer without actually installing, if the card is automatically detected. With v1.80a there is automatic card detection which if it would not work would mean that there is something wrong with the card.

              Reply

              • Steven07 Sep 2016 @ 09:47

                I see. Many thanks again. I really appreciate your help.

                I ran UNi-Xonar-STXII-11.5-v1.80b-r3 & my card was correctly identified as an STX. I have reinstalled that version again with
                Low DPC Latency selected to see if the blue screens reappear (as version 1.75a also blue screened).

                I wonder if anyone else has reported this issue running Windows 10 Anniversary Update x64?

                An updated driver would be great – ideally from Asus 🙂

                Reply

                • CarvedInside08 Sep 2016 @ 14:53

                  So far your report about this is the only one.
                  At the moment I don’t know what else you could do except maybe revert back to previous Windows build if possible.

                  Reply

  10. Yoram06 Sep 2016 @ 06:21

    Hi,

    What is the best of Uni Xonar, 1.64 or 1.75?

    Reply

  11. Elisey07 Sep 2016 @ 14:18

    So which driver better for Win 10 x64 2016 Anniversary Edition, UNi Xonar 1816/1823 v1.80a r3 or UNi Xonar 1816/1822 v1.75a r2 ? 🙂

    Reply

    • Steven08 Sep 2016 @ 09:30

      I’ve settled on UNi-Xonar-STXII-11.5-v1.80b-r3 & selected “C-Media Panel” on installation. Make sure you install in test mode (as above). No blue screens yesterday, but
      I’m sure the occasional one will appear 🙁

      Reply

  12. APoL009 Sep 2016 @ 07:37

    I updated from Windows 10 x64 to Windows 10 x64 Anniversary Update with an Asus Xonar Essence STX with UNi Xonar 1823 v1.80a r3 and I have worst audio quality than before the Anniversary Update with 8Channels, PCM 96 KHz, Headphones (Extra High Gain) and 7.1 Virtual Speaker and Dolby Headphone selected in ASUS Audio Center. I switched to UNi Xonar 1822 v1.75a r2 with a clean reinstall and the sound still being worst than before the Anniversary Update with that options selected in ASUS Audio Center.

    Reply

  13. That Ghost Pepper09 Sep 2016 @ 18:05

    Works Flawlessly on my asus xonar STX.
    Thanks a bunch 🙂

    Reply

  14. Jay10 Sep 2016 @ 07:53

    Updated to Anniversary Win10x64. STX II. 1.80b r3. I am connecting via all analog rca’s. Stereo mode ok, 7.1 ok, 5.1 mode NOT working properly. I have tried the Asus CC and the C-media panel. In both cases when in 5.1 mode, after 1-2 minutes all sound goes to the right rear surround. I then change to 7.1 or stereo and all is ok again. It seems the only problem is with 5.1 mode. Any ideas? Thanks!!!

    Reply

  15. Tom Yan12 Sep 2016 @ 01:17

    Hi all!

    So I am trying 1.80b “STXII” on an STX. The main reason for me to do so is the newly added “IEM” option in the headphone gain setting. I expected it to work on STX as well because STX II has the same DAC and HP Amp as STX does. However it does not seem to work. I do notice that switching from/to “IEM” to/from other gain options would cause “clicks” that we would get when we, for example, switch from “Speakers” to “Headphone”; while switching among the three other/original gain options would not. Yet the actual effect of “IEM” and “Normal Gain” sounded to be the same.

    So my question is, has anyone actually found that the IEM option does cause a difference when work with an STX II? Is it expected that it won’t really work on an STX?

    Btw, the (community) Linux driver introduced an extra gain option in correspondence to that. Instead of having an option that provides an even smaller gain than “Normal Gain”, the developer simply added an option that fills the larger gap between “Normal Gain” and “High Gain”:
    https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/sound/pci/oxygen/xonar_pcm179x.c?id=dd38dc1a9bf780b619ab93b3d7a5e90ebad441f5
    Is that NOT how the STX II driver has it done?

    It appears to me that, on both Windows and Linux, the gain setting does not actually adjust the HP Amp but the DAC. But now when switching from/to this new “IEM” option would cause clicks, I am wondering if it actually tries to bypass the HP Amp completely (i.e. RCA outputs, but merely routed to the Headphone jack). If that’s the case, is it really not possible for STX to have that as well?

    Reply

AdminAuthorFeaturedBuried

Leave a Reply

Your comment may be held for moderation. If it does not show up immediately, just be patient. Comments have to comply with these rules.