Yesterday, I still got crakling sounds, but i don't know how, it has been fixed, I just used my monitors jack, plug my headphones there, and then, come back to the pc jack, and it has been fixed.
Crackling audio after update to 2004
After updating Win10 to 2004, I get crackling audio when I use Razer Surround Pro software. When I switch my audio output, I get normal audio. This only happens when I use Surround Pro.
Edit: Still talking with razer support but I ultimately believe this is an issue with the 2004 update. I hope there's a fix for this soon, although I don't mind still using 1909.
Edit: this is the reply from Razer I got today:
Good day!
We receive an update from our appropriate department that our Audio team is checking on the path forward. Should there be a fix, it will come in the form of a software update. Please check the synapse update from time to time.
Thanks.
Edit: I don't understand why, but having bluestacks running in the background fixes the issue.
Windows for home | Windows 10 | Devices and drivers
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
129 answers
Sort by: Oldest
-
Anonymous
2020-08-16T01:41:42+00:00 -
Anonymous
2020-08-16T05:04:45+00:00 Well..since razer keep mentioning it is a legacy software, im switching to Dolby Atmos. Much better sound quality.
-
Anonymous
2020-08-16T10:30:05+00:00 lucky for you, your monitor has jack.
-
Anonymous
2020-08-17T09:07:39+00:00 To the people who say it suddenly works again:
Check your output device in Windows. Of course, you get interference-free sound when the output device in Windows sound control switches from Razer Surround to, for example, SONY TV *00 (Nvidia High Definition Audio) or Speakers (Realtek (R) Audio). As I said, I'm talking about the Windows settings, not the settings within the Razer software.
The problem still remains...
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more