Terrible audio quality in Windows 10 after recent software update
I'm documenting this question and answer for others for my specific situation that I hope is a benefit for others. I'm purposely being verbose in hopes that some sort of keyword search or general description will help more users find the solution.
I have a Dell Latitude laptop running Windows 10. After a recent software upgrade (it is likely the Spring Creators Update, but I'm not certain), audio coming from my speakers began sounding terrible. The bass was lacking, the audio was clipping, and it just sounded muddy, underwater, or like I was in a small enclosed room.
I tried different audio sources from different programs, but there was no difference. To isolate the issue and help with reproducing the issue, I chose to use a specific song played back using Foobar2000.
I tried different outputs from the same device - built-in laptop speakers, bookshelf speakers attached to a traditional external 2-channel amplifier powered by the headphone jack, a quality pair of headphones powered by the headphone jack, as well as the same external speakers via the USB-C docking station's headphone jack. Outside the difference attributed to the quality of the speakers themselves, the problem remained.
I also tried different devices. Luckily, I had another Latitude laptop running the same software to compare to, as well as an Android device with Google Play Music. The audio issue did not persist across devices, regardless of the speakers used.
That helped me rule out the music file, the playback software, and the output devices. It left me with the hardware or other OS software. However, since the audio was fine until a recent update and is generally left docked, I used some common sense to rule out the hardware as well.
After attempting to use the built-in audio troubleshooter (useless), trying different driver combinations, manually installing different driver packages, and even deleting the hardware devices (from Device Manager), there was still no change.
I checked with an audio engineer in the family, and they agreed the sound was like an equalizer had been applied to the system. But I had already ensured no OS-powered equalizer was running, nor was one configured in the DSP Manager for Foobar. My devices were all set to Stereo, not 5.1 Surround, so that wasn't the issue either.
So what was causing me to pull out my hair?
windows-10 audio dell-latitude distortion equalizer
add a comment |
I'm documenting this question and answer for others for my specific situation that I hope is a benefit for others. I'm purposely being verbose in hopes that some sort of keyword search or general description will help more users find the solution.
I have a Dell Latitude laptop running Windows 10. After a recent software upgrade (it is likely the Spring Creators Update, but I'm not certain), audio coming from my speakers began sounding terrible. The bass was lacking, the audio was clipping, and it just sounded muddy, underwater, or like I was in a small enclosed room.
I tried different audio sources from different programs, but there was no difference. To isolate the issue and help with reproducing the issue, I chose to use a specific song played back using Foobar2000.
I tried different outputs from the same device - built-in laptop speakers, bookshelf speakers attached to a traditional external 2-channel amplifier powered by the headphone jack, a quality pair of headphones powered by the headphone jack, as well as the same external speakers via the USB-C docking station's headphone jack. Outside the difference attributed to the quality of the speakers themselves, the problem remained.
I also tried different devices. Luckily, I had another Latitude laptop running the same software to compare to, as well as an Android device with Google Play Music. The audio issue did not persist across devices, regardless of the speakers used.
That helped me rule out the music file, the playback software, and the output devices. It left me with the hardware or other OS software. However, since the audio was fine until a recent update and is generally left docked, I used some common sense to rule out the hardware as well.
After attempting to use the built-in audio troubleshooter (useless), trying different driver combinations, manually installing different driver packages, and even deleting the hardware devices (from Device Manager), there was still no change.
I checked with an audio engineer in the family, and they agreed the sound was like an equalizer had been applied to the system. But I had already ensured no OS-powered equalizer was running, nor was one configured in the DSP Manager for Foobar. My devices were all set to Stereo, not 5.1 Surround, so that wasn't the issue either.
So what was causing me to pull out my hair?
windows-10 audio dell-latitude distortion equalizer
Check for the latest sound driver and install it.
– Moab
Jun 21 '18 at 14:37
As indicated, this was attempted in many different methods without useful results.
– D.N.
Jun 21 '18 at 15:00
add a comment |
I'm documenting this question and answer for others for my specific situation that I hope is a benefit for others. I'm purposely being verbose in hopes that some sort of keyword search or general description will help more users find the solution.
I have a Dell Latitude laptop running Windows 10. After a recent software upgrade (it is likely the Spring Creators Update, but I'm not certain), audio coming from my speakers began sounding terrible. The bass was lacking, the audio was clipping, and it just sounded muddy, underwater, or like I was in a small enclosed room.
I tried different audio sources from different programs, but there was no difference. To isolate the issue and help with reproducing the issue, I chose to use a specific song played back using Foobar2000.
I tried different outputs from the same device - built-in laptop speakers, bookshelf speakers attached to a traditional external 2-channel amplifier powered by the headphone jack, a quality pair of headphones powered by the headphone jack, as well as the same external speakers via the USB-C docking station's headphone jack. Outside the difference attributed to the quality of the speakers themselves, the problem remained.
I also tried different devices. Luckily, I had another Latitude laptop running the same software to compare to, as well as an Android device with Google Play Music. The audio issue did not persist across devices, regardless of the speakers used.
That helped me rule out the music file, the playback software, and the output devices. It left me with the hardware or other OS software. However, since the audio was fine until a recent update and is generally left docked, I used some common sense to rule out the hardware as well.
After attempting to use the built-in audio troubleshooter (useless), trying different driver combinations, manually installing different driver packages, and even deleting the hardware devices (from Device Manager), there was still no change.
I checked with an audio engineer in the family, and they agreed the sound was like an equalizer had been applied to the system. But I had already ensured no OS-powered equalizer was running, nor was one configured in the DSP Manager for Foobar. My devices were all set to Stereo, not 5.1 Surround, so that wasn't the issue either.
So what was causing me to pull out my hair?
windows-10 audio dell-latitude distortion equalizer
I'm documenting this question and answer for others for my specific situation that I hope is a benefit for others. I'm purposely being verbose in hopes that some sort of keyword search or general description will help more users find the solution.
I have a Dell Latitude laptop running Windows 10. After a recent software upgrade (it is likely the Spring Creators Update, but I'm not certain), audio coming from my speakers began sounding terrible. The bass was lacking, the audio was clipping, and it just sounded muddy, underwater, or like I was in a small enclosed room.
I tried different audio sources from different programs, but there was no difference. To isolate the issue and help with reproducing the issue, I chose to use a specific song played back using Foobar2000.
I tried different outputs from the same device - built-in laptop speakers, bookshelf speakers attached to a traditional external 2-channel amplifier powered by the headphone jack, a quality pair of headphones powered by the headphone jack, as well as the same external speakers via the USB-C docking station's headphone jack. Outside the difference attributed to the quality of the speakers themselves, the problem remained.
I also tried different devices. Luckily, I had another Latitude laptop running the same software to compare to, as well as an Android device with Google Play Music. The audio issue did not persist across devices, regardless of the speakers used.
That helped me rule out the music file, the playback software, and the output devices. It left me with the hardware or other OS software. However, since the audio was fine until a recent update and is generally left docked, I used some common sense to rule out the hardware as well.
After attempting to use the built-in audio troubleshooter (useless), trying different driver combinations, manually installing different driver packages, and even deleting the hardware devices (from Device Manager), there was still no change.
I checked with an audio engineer in the family, and they agreed the sound was like an equalizer had been applied to the system. But I had already ensured no OS-powered equalizer was running, nor was one configured in the DSP Manager for Foobar. My devices were all set to Stereo, not 5.1 Surround, so that wasn't the issue either.
So what was causing me to pull out my hair?
windows-10 audio dell-latitude distortion equalizer
windows-10 audio dell-latitude distortion equalizer
asked Jun 21 '18 at 2:47
D.N.
1266
1266
Check for the latest sound driver and install it.
– Moab
Jun 21 '18 at 14:37
As indicated, this was attempted in many different methods without useful results.
– D.N.
Jun 21 '18 at 15:00
add a comment |
Check for the latest sound driver and install it.
– Moab
Jun 21 '18 at 14:37
As indicated, this was attempted in many different methods without useful results.
– D.N.
Jun 21 '18 at 15:00
Check for the latest sound driver and install it.
– Moab
Jun 21 '18 at 14:37
Check for the latest sound driver and install it.
– Moab
Jun 21 '18 at 14:37
As indicated, this was attempted in many different methods without useful results.
– D.N.
Jun 21 '18 at 15:00
As indicated, this was attempted in many different methods without useful results.
– D.N.
Jun 21 '18 at 15:00
add a comment |
1 Answer
1
active
oldest
votes
I recalled a similar issue when I first received the laptop, associated with a software package called WAVES MaxxAudio Pro. It seems this audio "enhancement" configuration is limited to the software, meaning it is not tied to any Windows-based control panel or system configuration.
I opened the application (located at C:Program FilesWavesMaxxAudioMaxxAudioPro.exe
) and switched to the "Playback" tab, noticing it had been turned on. As a side note, I had previously, forcefully removed the application from my system, but it must have been restored as part of a software update.
Turning off the "Playback enhancement" slider at the top immediately fixed the problem. What's interesting is it seems to be designed to boost the bass, but ended up cutting most of the bass response out.
Here is a screenshot of the interface for quick reference:
Update: After no longer trusting my ears to identify if the profile had reloaded itself, I decided to make a profile completely over-driven and awful sounding as the default, so I would be able to determine, without any doubt, if the (wrong) profile was active.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1333018%2fterrible-audio-quality-in-windows-10-after-recent-software-update%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I recalled a similar issue when I first received the laptop, associated with a software package called WAVES MaxxAudio Pro. It seems this audio "enhancement" configuration is limited to the software, meaning it is not tied to any Windows-based control panel or system configuration.
I opened the application (located at C:Program FilesWavesMaxxAudioMaxxAudioPro.exe
) and switched to the "Playback" tab, noticing it had been turned on. As a side note, I had previously, forcefully removed the application from my system, but it must have been restored as part of a software update.
Turning off the "Playback enhancement" slider at the top immediately fixed the problem. What's interesting is it seems to be designed to boost the bass, but ended up cutting most of the bass response out.
Here is a screenshot of the interface for quick reference:
Update: After no longer trusting my ears to identify if the profile had reloaded itself, I decided to make a profile completely over-driven and awful sounding as the default, so I would be able to determine, without any doubt, if the (wrong) profile was active.
add a comment |
I recalled a similar issue when I first received the laptop, associated with a software package called WAVES MaxxAudio Pro. It seems this audio "enhancement" configuration is limited to the software, meaning it is not tied to any Windows-based control panel or system configuration.
I opened the application (located at C:Program FilesWavesMaxxAudioMaxxAudioPro.exe
) and switched to the "Playback" tab, noticing it had been turned on. As a side note, I had previously, forcefully removed the application from my system, but it must have been restored as part of a software update.
Turning off the "Playback enhancement" slider at the top immediately fixed the problem. What's interesting is it seems to be designed to boost the bass, but ended up cutting most of the bass response out.
Here is a screenshot of the interface for quick reference:
Update: After no longer trusting my ears to identify if the profile had reloaded itself, I decided to make a profile completely over-driven and awful sounding as the default, so I would be able to determine, without any doubt, if the (wrong) profile was active.
add a comment |
I recalled a similar issue when I first received the laptop, associated with a software package called WAVES MaxxAudio Pro. It seems this audio "enhancement" configuration is limited to the software, meaning it is not tied to any Windows-based control panel or system configuration.
I opened the application (located at C:Program FilesWavesMaxxAudioMaxxAudioPro.exe
) and switched to the "Playback" tab, noticing it had been turned on. As a side note, I had previously, forcefully removed the application from my system, but it must have been restored as part of a software update.
Turning off the "Playback enhancement" slider at the top immediately fixed the problem. What's interesting is it seems to be designed to boost the bass, but ended up cutting most of the bass response out.
Here is a screenshot of the interface for quick reference:
Update: After no longer trusting my ears to identify if the profile had reloaded itself, I decided to make a profile completely over-driven and awful sounding as the default, so I would be able to determine, without any doubt, if the (wrong) profile was active.
I recalled a similar issue when I first received the laptop, associated with a software package called WAVES MaxxAudio Pro. It seems this audio "enhancement" configuration is limited to the software, meaning it is not tied to any Windows-based control panel or system configuration.
I opened the application (located at C:Program FilesWavesMaxxAudioMaxxAudioPro.exe
) and switched to the "Playback" tab, noticing it had been turned on. As a side note, I had previously, forcefully removed the application from my system, but it must have been restored as part of a software update.
Turning off the "Playback enhancement" slider at the top immediately fixed the problem. What's interesting is it seems to be designed to boost the bass, but ended up cutting most of the bass response out.
Here is a screenshot of the interface for quick reference:
Update: After no longer trusting my ears to identify if the profile had reloaded itself, I decided to make a profile completely over-driven and awful sounding as the default, so I would be able to determine, without any doubt, if the (wrong) profile was active.
edited Dec 13 '18 at 6:58
answered Jun 21 '18 at 2:47
D.N.
1266
1266
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1333018%2fterrible-audio-quality-in-windows-10-after-recent-software-update%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Check for the latest sound driver and install it.
– Moab
Jun 21 '18 at 14:37
As indicated, this was attempted in many different methods without useful results.
– D.N.
Jun 21 '18 at 15:00