You are viewing comment page 195 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.
My xonar stx has lost the ability to do anything but 2ch stereo since recent windows updates. Its an older card and none of the drivers seem to help. Is there still support for this card in the future, anyone have a functional stx?
Actually 1.80a r3 is working for me. Not perfect but movies are playing in proper 5.1 now. Going to play around more with all of these great drivers and addons. Thanks for the hard work guys. To bad Asus doesn't work harder on their drivers because there are probably a lot if people in my situation. It took me a few days of tinkering and searching to find this site.
Please add restart card function to the driver pack. Sometimes my Xonar DX stops playing sound in right chanel and I’ve had to restart computer, to restart the card.
I will consider it.
I've had the exact same problem for years, over multiple windows installs. Have the D1 btw.
Right channel cuts out and only comes back after restart. Log off does not cut it.
It's only very intermittent, so not the end of the world, but annoying.
This would be great, I have the same problem.
You should try putting the system to Sleep and resume afterwards. If sleep in not available in Start menu-> Shut Down options, you need to go in BIOS/UEFI and enable an option called something like Standby S3, Standby STR, or Standby Suspend To RAM.
Ok, while that is no fix for the actual problem, this is much faster than a reboot and fixes the sound. Thanks, I can live with that!
I'm not sure a permanent fix it's possible as I think this is a hardware problem with your Xonar card.
I am happy to hear my standby solution is of help to you. I've come up with a possible better solution that resets the relay switch that sometimes gets "stuck". To test this solution, download this file and launch it when you run into the problem again. Please let me know if it works.
BTW Thank you for the donation.
Got the DX recently, and faced this annoying problem. Rebooting the PC and restarting the relays using this file does not help at all, the relay clicks but the sound remains quiet. Is there any solution?
What's the annoying problem? The sound output on with your DX card does not work? Has it ever worked? Are you using analog or S/PDIF?
My xonar does the same thing. I found that wasapi is causing it. Firefox uses wasapi and watching youtube sometimes i get this loud white noise, i stop the video and after that the right channel doesn't work. Sometimes there's no white noise just the right channel cuts off. No restart just disable and re-enable the sound card in device manager, you will hear a click when disabling and two click when enabling. My guess is bad relays, bad hardware quality overall, not too pleased with it.
For the loud white noise issue you should check this page and also repost your comment there. Mention your sound card, motherboard, video card, and OS.
This is the first I hear of both issues happening at the same time. For restarting the card, I made Xonar driver restart, might be more useful than manually disabling and enabling it.
Sorry if i don't read through 195 page.
Is it possible to run two Xonar in one PC?
I have a Essence ST and got a HDAV1.3 today.
I think they should work. Read FAQ Q&A 22 on how to change settings for each card.
First i did install the HDAV with just C-Media Panel - that worked. Then i plugged the ST in but had only the yellow exclamation mark in the device manager.
So i did install the driver again but still only exclamation mark. It does not work.
By the way: XonarSwitch says the HDAV is not supported.
What it says under "Device status" in ASUS Xonar ST Proprieties from Device Manager? Have you tried without having the HDAV card plugged?
Which drivers have you installed?
Yeah, forgot that XonarSwitch does not currently support HDAV cards. You could also control settings for each card by disabling one in device manager and launching ASUS/C-media Panel.
I did not check what the status was. I tried v1.80a and v1.80b. You mean taking out the HDAV, install the ST and then putting back the HDAV?
Thanks for trying to help but i have bigger problem to solve now 🙁
I was looking a long time for a H6 board for my Essence ST.
Last week one showed up - a HDAV1.3 Deluxe.
So i bought the whole package because i was searching a H6 since a long time.
Now the problem is that i don't get sound from my ST after i plug in the H6.
The left and right speaker outputs stop working.
I tried UNi v1.80a, v1.80b, v1.75a and the Asus v8.1.8.1822 Beta driver.
I tried installing the driver with and without the "Re-enable stereo upmix to 4, 5.1 & 7.1" option.
Then to make sure the H6 is ok i did install the HDAV + H6 in my HTPC and it works.
If the H6 works with the HDAV i guess it is not defective?
But my ST analog output only works if i unplug the H6...
Was just thinking I should share my result after having BSOD with W10 Creators update:
UNi Xonar 1816/1823 v1.80a r3, UNi Xonar W10 1825 v1.81a r2, 1816/1823 v1.80a r3, UNi Xonar 1822 v1.75a r3 all caused BSOD when waking/starting the pc. The only one that, so far, have seen to be working is UNi Xonar 1821 v1.71 r2
Thank you for sharing. Beside being valuable information it's also very good that you told me this since I am planning of updating most driver packages and might have skipped th 1821 drivers.
If it's possible to give me me additional information. When did the BSOD problem started? Was it after installing Creators Update or somewhere further the line after additional Windows updates? Are you changing any Xonar settings after you install the drivers? You always get a BSOD when waking the PC or only sometimes?
Please keep us updated if the situation changes, if you get BSOD's with v1.71 or you no longer get them if you ever install newer drivers.
Sharing is caring. 😀
I was on W8.1 before and then did a total reinstall of W10 creators update and thats when I started experience problems. I tried both the "normal" installation and low latency installation for all the drivers. At the moment I am using the low latency mode.
I'm here to claimed that I have the same issue I'm on windows fall creator update build,
I'll try 1.71 and see if its fix the problem like you said.
Just reporting another case where driver v1.71-r2 resolved the BSOD after sleep issue. PC = Win10 x64 1709 with Xonar DX card. Version v1.80a r3 ran OK until about Feb. 2018, so something MS “updated” around then probably caused the BSOD/sleep problem. Tried v1.81a r2 but problem persisted. Thanks to suggestions above and by other users, installed v1.71-r2 three weeks ago and no BSODs since. Thanks for keeping these cards alive with your drivers.
Same issue here with LTSC 1809 on driver v1.80a r3.
I have potentially found a 'solution' which I have high hopes of working, instead of letting Windows recover from the former driver state:
1. Disable the driver before hibernation/sleep.
2. Once the system has resumed, re-enable the driver. (Hoping that the faulty state of the driver or some weird race condition doesn't occur with a fresh reload)
My solution is to hibernate/sleep either through a cmd or powershell script:
Stop-Service -Name "audiosrv" -Force # Disable any audio streams, otherwise the device cannot be disabledStart-Sleep -Seconds 1
Disable-PnpDevice -InstanceId 'PCI\VEN_13F6&DEV_8788&SUBSYS_85F41043&REV_00\5&30FA9A89&0&2000E0' -Confirm:$False # Disable the device driver
Start-Sleep -Seconds 1
shutdown /h # Hibernate
And now to automatically re-enable the Audio service and the driver automatically after a Windows resume I have a powershell script running 24/7 in the background, started by task scheduler, that monitors windows event log (Sadly this can not work for going into sleep/hibernation as the event for that comes too late in the process and there is no time to do anything):
# Monitor Resume from Hibernation/sleep
$query = "SELECT * FROM __instanceCreationEvent WHERE TargetInstance ISA 'Win32_NTLogEvent' AND TargetInstance.EventCode=107"
Register-WMIEvent -Query $query -Action {
Start-Sleep -Seconds 1
Start-Service -Name "audiosrv"
Start-Sleep -Seconds 1
Enable-PnpDevice -InstanceId 'PCI\VEN_13F6&DEV_8788&SUBSYS_85F41043&REV_00\5&30FA9A89&0&2000E0' -Confirm:$False
}
Subsequently I have removed the 'Hibernate/sleep' button from the start menu (reg key) just in case I forget to use the script with the new method.
I will reply to my original post in a week or so (of continuous hibernations) and verify whether this solution is successful or not.
Oh and I have removed the 'Hibernate' button from the start menu just in case I forget to hibernate with the new method (I only hibernate once a day so errors easily happen).
$Path = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FlyoutMenuSettings"; if(-not (Test-Path -Path $Path)){ New-Item -ItemType String -Path $Path }
New-ItemProperty -Path $Path -Name "ShowHibernateOption" -PropertyType Dword -Value 0 -Force # Disable as we want to hibernate through batch file or MTHaxTool (STX II)
This will also take a few days or a week to make sure it really works, as it seems to only happen every few days.
Btw: I keep mentioning Hibernation as i use full disk hibernation (No hybrid or anything silly like that). But this should also work for regular sleep/standby with some small adjustments.
I have an uptime of exactly 7 days now (With sleeps in between) and still going strong! 🙂
This seems to work.
Last update: Now months later I slept PC almost every day, not a single BSOD occurred since.
Solution works! 🙂
Hello MT
I have has the same issue for a long time already, and reverting to version 1.71a or disabling Nvidia Audio didn't help, so I thought I would give your script a try. Now I don't have any experience with Powershell, but I found out how to create and run them, so I started by trying to run the hibernate script. The hibernation itself worked well, but the other lines don't. And I don't really understand why... Can you help me out?
Stop-Service : Service 'Windows Audio (audiosrv)' cannot be stopped due to the following error: Cannot open audiosrv service on computer '.'.At C:\Users\daffy\OneDrive\Documenten\Hibernate.ps1:1 char:1
+ Stop-Service -Name "audiosrv" -Force # Disable any audio streams, oth ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : CloseError: (System.ServiceProcess.ServiceController:ServiceController) [Stop-Service], ServiceCommandException
+ FullyQualifiedErrorId : CouldNotStopService,Microsoft.PowerShell.Commands.StopServiceCommand
Stop-Service : Collection was modified; enumeration operation may not execute.
At C:\Users\daffy\OneDrive\Documenten\Hibernate.ps1:1 char:1
+ Stop-Service -Name "audiosrv" -Force # Disable any audio streams, oth ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Stop-Service], InvalidOperationException
+ FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.PowerShell.Commands.StopServiceCommand
Disable-PnpDevice : No Win32_PnPEntity objects found with property 'DeviceID' equal to 'PCI\VEN_13F6&DEV_8788&SUBSYS_85F41043&REV_00\5&30FA9A89&0&2000E0'. Verify the value of the property and retry.
At C:\Users\daffy\OneDrive\Documenten\Hibernate.ps1:3 char:1
+ Disable-PnpDevice -InstanceId 'PCI\VEN_13F6&DEV_8788&SUBSYS_85F41043& ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (PCI\VEN_13F6&DE...FA9A89&0&2000E0:String) [Disable-PnpDevice], CimJobException
+ FullyQualifiedErrorId : CmdletizationQuery_NotFound_DeviceID,Disable-PnpDevice
Thanks!
Davy
This might come too late for you, but for others who might read it in the future.
My guesses are: You did not run it as administrator and you need to copy the (YOUR) Device ID from the hardware manager (properties -> details -> device instance path).
What I came up with, based on previous solution, needs you to double click the same file two times.
Once two disable and sleep/hibernate and once to enable again after waking up.
You can combine it or tweak it... e.g. if you prefer it to run more "silent".
It works by checking whether the Specified Device is enabled or not.
If it is enabled, it will disable the device and go to sleep or hibernate (edit the code). If it is disabled the assumption is, that we just woke the system up so it enables the device (and audio service).
That means this will not work properly if you enable or disable the device manually.
Otherwise you can "cycle"
1. Create a file wherever you want e.g. "Suspend.ps1" with the Code from below.
2. Create (a) shortcut(s) eg. on the desktop or taskbar, you can name it "Suspend".
3. Right click the created shortcut and set the target to:
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy RemoteSigned -file "C:\Users\Username\Path\to\suspend.ps1"
4. Set Start in:
C:\Windows\System32\WindowsPowerShell\v1.0
5. Click on Advanced and choose "Run as Administrator"
Suspend.ps1:
$deviceId = 'PCI\VEN_13F6&DEV_8788&SUBSYS_835C1043&REV_00\.....find your ID'$device = Get-PnpDevice -InstanceId $deviceId -ErrorAction SilentlyContinue
if ($device) {
switch ($device.Status)
{
'OK'
{
Write-Host "Disabling audio service, device and go energy saving"
Stop-Service -Name "audiosrv" -Force
Start-Sleep -Seconds 1
Disable-PnpDevice -InstanceId $deviceId -Confirm:$false
Start-Sleep -Seconds 1
#replace "Suspend" by "Hibernate" depending on what you use/is available or just use:
#shutdown /h
#and delete/comment the following two lines
[Void][System.Reflection.Assembly]::LoadWithPartialName("System.Windows.Forms")
[System.Windows.Forms.Application]::SetSuspendState("Suspend", $false, $false)
break
}
default
{
Write-Host "Enabling audio service and device"
Start-Service -Name "audiosrv"
Start-Sleep -Seconds 1
Enable-PnpDevice -InstanceId $deviceId -Confirm:$false
}
}
}
else {
Write-Warning "Device with ID '$deviceId' not found"
}
Same for me mate. This STX2.sys driver caused me to BSOD when waking up from sleep on Windows 10, Version 10.0.19043 Build 19043. I'll revert to the earlier driver and hopefully it won't cause this error anymore. Quite sad about it 🙁
I'm having a similar problem with STX2.sys, did reverting to v1.71r2 resolve the issue for you? Is v1.71r2 still the newest version that works without the BSOD?
The solution is mentioned above 😉
Basically disable Windows Audio (Service) and then STX II driver, hibernate/standby.
Resume -> Re-enable Windows Audio Service, and then STX II driver.
Now you just gotta automate it like i did 😉
Actually I think I may have tracked down the source of the problem. TL;DR at the bottom.
I have a Gigabyte z390 Aorus Master motherboard, Asus Xonar Essence STX II sound card, and Nvidia Geforce RTX 2080 Ti graphics card, running Windows 10 and using the official Asus audio drivers downloaded from their web site. I've been having consistent BSODs when waking from sleep (DRIVER_IRQL_NOT_LESS_OR_EQUAL, with the offending driver listed as "STXII.sys") ever since I built this PC maybe two years ago. At first it wasn't too frequent but sometime in the last year it starting happening maybe 3 out of every 4 times I woke the computer up after sleeping more than five minutes. Also note that my previous Windows 10 PC had an Asus Xonar Essence STX sound card and I never encountered this problem using the official Asus drivers.
For unrelated reasons my computer suffered some OS corruption recently and I decided that if I'm going to reinstall Windows I might as well take the opportunity to track this BSOD problem down once and for all. So I disconnected most of the peripherals, did a clean install of Windows, and started slowly adding the peripherals back (and installing the relevant drivers) one at a time over the course of a few weeks, waiting maybe three days between each alteration while waking and sleeping my computer at least twice a day to see if the BSODs had come back. Here's what I found out:
1. No BSODs with no expansion cards installed and using integrated graphics (no surprise there).
2. No BSODs after adding only the STX II and installing the official Asus drivers (interesting).
3. BSODs after adding the Nvidia 2080 and installing the Nvidia drivers (!!!).
4. No BSODs after removing the STX II and uninstalling the Asus drivers.
5. BSODs after adding my previous STX I and installing the corresponding Asus drivers.
At this point it seemed clear that the root cause of the BSODs was some sort of conflict between the sound card and the video card, since the BSODs only occurred when both were installed. And since the BSODs occurred with both the known-good STX and the STX II, this pointed to some sort of driver conflict rather than a faulty STX II.
So I swapped my STX II back in, started googling around, found this page, posted the above comment, and then saw a somewhat unrelated troubleshooting step that suggested disabling integrated audio via the BIOS. I didn't think that was necessary with a modern BIOS, but I did it anyways just to be safe, and then figured I might as well disable any other audio devices in Device Manager as well. I went into the Device Manager, saw two non-Asus sound controllers named "NVIDIA High Definition Audio" and "NVIDIA Virtual Audio Device (Wave Extensible) (WDM)", and disabled them.
Lo and behold, the BSODs stopped. After a few days I went back into the device manager, re-enabled the two Nvidia devices, and the BSODs immediately came back. Disabled them a couple of days later, BSODs went away.
At this point I'm feeling pretty confident that the root problem is some sort of conflict between the Asus and Nvidia audio drivers, and was likely introduced after either an Nvidia driver update or a Windows 10 update (since the same Asus drivers and STX worked fine with my old PC). Last night I re-installed Windows and all the drivers from scratch, and disabled the two Nvidia audio devices immediately after installing the Nvidia drivers. I've spent most of today putting the computer to sleep and waking it back up again and running some 3DMark benchmarks to check system stability, with no BSODs so far. I won't be able to authoritatively say the problem is gone for a few more weeks, but I wanted to post this here while it was all fresh in my mind. Fingers crossed.
In the meantime I'd be interested to know if you (along with the other commenters experiencing this BSOD) also have an Nvidia graphics card, as that would bolster the evidence for this theory. It wouldn't surprise me if the correlation has been overlooked - I didn't even know the Nvidia audio drivers existed until recently, when they hijacked my speakers as the default audio device.
TL;DR: Open "Device Manager", expand "Sound, video, and game controllers", and disable "NVIDIA High Definition Audio" and "NVIDIA Virtual Audio Device (Wave Extensible) (WDM)" by right-clicking on each and clicking "Disable device".
Ah.
I dont even install any of these drivers and I programaticaly disable any non-used devices through bios and post-install powershell script.
Thats all I can say.
Unfortunately you need the nvidia audio for a VR Headset Audio. I dont need sleep mode anyway though
Did you have the same problem? Which sound card do you have? Which graphics card?
I dont know. I never use sleep mode like said. Soundcard is HDAV 1.3 and GPU is RTX 2080 Ti.
The information with "Unfortunately you need the nvidia audio for a VR Headset Audio" is a useful contribution. The rest leaves room for interpretation. You should have said something like "I didn't had this issue, but I am not using suspend.".
I cut the GX part of the comment since it is not related to the issue we are discussing in this comment thread.
Is there support for zero latency mic monitoring in windows 10? (see: http://i59.tinypic.com/2ijpxea.jpg)
Using the 'monitoring' feature in the mic or in the asus panel has about a 100ms delay.
I think you linked the wrong picture.
I don't know about this. Are you using the ASUS drivers or the UNi Xonar drivers? How do you measure the mic monitor delay?
Sorry, should have clarified. I want my control panel to look like that picture. In the options for my speaker I only see the volume, no extra devices. This is what mine looks like: http://i.imgur.com/95e3O1l.png
I initially had the ASUS drivers installed, then installed the UNI drivers afterwards. I installed with 'low latency' selected, on version v1.80a-r3
Can't help you with the changing what's being showed in Speaker Proprieties panel.
About the delay with mic monitor, did you had this problem when you had the ASUS drivers? If it's possible to tell me how did you measure the delay?
Yeah the delay was the same with the ASUS drivers and after I installed the uni drivers
I did a rough estimate of measuring the delay by turning on Monitoring for my mic, snapping my finger and recording it in audacity, and then editing it so there were 2 successive snaps with the same delay I hear in my headphones. It worked out to be roughly 100ms.
Apparently you're supposed to be able to see other devices in the control panel but it looks to be a driver specific thing. If I could get that to work there would be almost no latency.
As far as I know, it's not possible to monitor inputs on Xonar cards under Windows without added latency. One reason I still have a Creative card in my PC as well - I use my PC for playing guitar and it's just not possible with Xonar. Drivers don't matter, Asus or Unified, there's always delay.
The only way to get a zero latency input monitor on Xonar I've found is to use Linux...
Sometimes with opening any video in chrome, any video game,windows sounds, happens that loud white noise(so strange because my volume is about 56%).
os:Win10 creators update.soundcard: Xonar DX
driverversion:UNi Xonar W10 1825 v1.81a r2 driver , gonna try v1.80a r3
Please check FAQ Q&A18.
i read it before posting, thx.its happens really rare and as remeber starts only after creations update.
For example i start a youtube video noise happens but after browser restart its okay.
I see. Thanks for the report. At the moment I don't have any information on how to fix this.
While it's a long shot, you should check the Disable SpeakerCompensation tweak. Let me know if it has an effect on the loud noise issue you are having.
Have you got the chance to test the Disable SpeakerCompensation tweak. Is the loud white noise issue still happening with it?
I have the exact same problem with my Xonar DX. Doesn't matter which driver I use (also ASUS stock drivers), it happens now and then. Usually I have my volume at 20%, so it kinda gives me a heartattack everytime it happens...
Any eta when the planning of drivers will get updated?
Please check FAQ Q&A 13. Currently there are no new audio drivers available from C-Media. To be honest, I don't know if there will be any new audio drivers since audio card manufacturers shifted their attention to newer audio chips (not necessarily better) that have different drivers.
But I am planing on updating all the UNi Xonar driver packages with the two new improvements I've discovered (SpeakerCompensation and Microphone Volume Increase by 3dB tweaks) and with improvements to the UNi Xonar installer. I don't have any ETA on that.
Since a couple of days, the audio regularly stops working after using windows for a while only fixable by a reboot, some games even cause BSODs just minutes after starting (DRIVER_IRQL_NOT_LESS_OR_EQUAL caused by cmudaxp.sys or STXII.sys).
I tried the different driver versions and even reinstalled Windows 10 completely and tried all driver versions again, both issues persist. Did Microsoft release some update that broke the driver or could my STXII be broken?
Well - since the card stopped working even under Linux I think it's a hardware fault. I'm getting a replacement and will let you guys know if it fixes the issues.
If you still have the card you should check the card in another PC so you know it's the card and not a problem with the motherboard.
Just replaced it, bluescreens fixed, never had a sound card "break" like that.
I have a Xonar DX and have been on the 1.80 drivers for a while. I recently noticed that I couldn't change the speaker input from 2 channels to 6, it was on 2 and would flick back to 2 the instance I selected 6.
Anyway, I decided to try the 1.81 drivers. A bunch of BSODs and uninstalls/reinstalls later I'm back to 1.80 but cannot get the sound working. Specifically it no longer lets me change the input channels at all. It's just blank and reselects to blank every time I try to select anything else. Where are the settings stored? Is there a way to force the number of channels? Is that a symptom of another issue? What call is being made during the selection process that could cause this behaviour?
I'm hoping your can point me at a file I can hack to fix the issue.
Have you tried C-Media Audio Panel or XonarSwitch? Do they have the same behavior? The issue could be caused by some newly released Windows update.
The number of channels is a Windows setting, you can manually change it by going to Windows Volume tray icon->right-click->Playback devices->1 click on Speakers Asus Xonar(...) and press "Configure" button on the bottom left of the window.
Yes the same behaviour. Originally I was using both C-Media Panel and I had a couple of profiles in XonarSwitch. I noticed the profiles weren't being applied, so tried in C-Media Panel. This is when I did the Upgrade/BSOD/downgrade/etc. Since then I can still change everything except the number of channels in the C-Media Panel, but the windows configure button is non-responsive and I can't change any of the xonar properties through windows settings (as in it wont bring up the menus or in the properties window I have two tabs (should be more), selecting the second tab I see a blank page. I can't really interact with the windows sound settings at all really, it also wont let me set change/set the default device to a working one. I have to disable the Xonar in device manager to force it to change.
No subwoofer in Win 10 Creator's update with ASUS Xonar DSX PCIe 7.1 GX2.5 . Test from sound control panel applet works, also test from mixer. However, no bass from games and surround sound test apps. Same problem with built-in Realtek AC1150 (which is why I just bought the ASUS Xonar card.)
It sounds to me like a Windows 10 problem. You might want to contact Windows support.
I've found the root of the issue for the bug I mentioned in this post: http://maxedtech.com/asus-xonar-unified-drivers/comment-page-189/#comment-128503
The problem is that XonarSwitch sets an incorrect value for the InputMicVolL subkey in "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E96C-E325-11CE-BFC1-08002BE10318}\0000\Settings", when it tries to set 100% Mic Volume. It sets the REG_BINARY Data to "f2 12 fe ff", which pans the Mic slightly to the right, when it should be setting it to "00 00 00 00" to match InputMicVolR and giving 100% Mic Volume panned to center.
I know that it's XonarSwitch, which you don't develop. But is there any way you could pass the would along to the dev and he could do a quick update, since it is likely a very easy fix, being that it is only one registry value? If not, I understand. Thanks either way
I will let Giulio know about microphone issue.
In your linked post you've also mentioned about having the loud white noise and since you are testing the SpeakerCompensation tweak, I am curious if in your case the loud white noise still happens after you've disabled SpeakerCompensation. You can let me know in a reply to this comment.
No it hasn't. I will post another reply if/when it happens.
Just got the horrifying screech of doom and despair while watching a YouTube livestream. It sounded slightly different I think, but I didn't take time to analyze that too much -_-
I see, thanks for the report. I saw here that disabling HPET could fix the issue in some cases.
but why new drivers are windows 10 only? 😐
That's how they are made by C-Media.
I did modify cmedia panel dll to extend range of "Key Shifting" function (from -4 +4 to -20 +16).
Here is dll to replace, if anyone also like this function a lot, just like me (probably works only with version 1.80)
http://www86.zippyshare.com/v/5EBAW7rk/file.html
Replace it in C:\Windows\SysWOW64 (64bit windows) or C:\Windows\System32 (32bit windows)
Though I cant guarantee this will works for you (no tests on another pc) + i'm not good at assembler, hex editing and debuging.
...
I love how some songs sound with this effect 😀
A better suited place for your modification would be here. Please repost your comment there. Thanks.
After a fresh install of Windows 10 Enterprise 2016 LTSB, I was getting a stutter/hickup everyone 5-10 seconds or so when watching videos in VLC.
I originally had 1825 v1.81a r2 installed. I then tried 1823 v1.80a r3 which had the same issue.
After installing 1822 v1.75a r3 I don't have this issue anymore.
Thank you for the information.
Hi there. Has anyone found a solution for why teamspeak switch off the microphone over a driver 1.75a r3? But if you turn it on, it just works again.