Crackling/static in Discord with default audio output port (PulseAudio)
I installed Ubuntu 18.04 less than a week ago and 99% of what I need to work has been no problem. When I first installed Discord, from the instructions on their website, everything was fine. The Snap package had problems starting and refused to go past the update sequence, as if it had no internet connection. However, the first time I join a voice chat after a reboot, I get loud crackling anytime someone speaks. It fixes itself if I change the output of my headphones from Line Out to Headphones or vice versa (headphones setting sounds better to me).
I initially thought it was the Line Out setting being the issue, so I changed it using this as a guide. That did not fix it and no matter which one I set as default, the crackling returns equally as bad in Discord until I change it. After that, either port sounds just fine. I'm trying to figure out how I can have it sound good without having to flip the setting in PulseAudio, but I'm clueless.
All other audio seems fine. Even in games like CSGO there isn't this problem with voice chat, and I'm able to play other games, watch video, and listen to spotify just fine. It only seems to be affecting discord.
If it matters, the exact settings are "Line Out (plugged in)" and "Headphones (unplugged)" although despite the forum in the link above, I was able to set the Headphones as default anyway and it recognizes that port. I'm using the PulseAudio Volume Control (pavucontrol) app from Ubuntu Software to change these settings, and the terminal to set the default port.
My only connected audio devices are my headphones for output, plugged into the motherboard port; my mixer and headphones are listed in input (headphone mic muted), both also plugged into the motherboard. Mixer is a USB interface. My webcam was listed at one point, but I'm not sure where it has gone and if that can affect things somehow.
If anyone knows of a fix, please let me know! Thank you
sound pulseaudio headphones
add a comment |
I installed Ubuntu 18.04 less than a week ago and 99% of what I need to work has been no problem. When I first installed Discord, from the instructions on their website, everything was fine. The Snap package had problems starting and refused to go past the update sequence, as if it had no internet connection. However, the first time I join a voice chat after a reboot, I get loud crackling anytime someone speaks. It fixes itself if I change the output of my headphones from Line Out to Headphones or vice versa (headphones setting sounds better to me).
I initially thought it was the Line Out setting being the issue, so I changed it using this as a guide. That did not fix it and no matter which one I set as default, the crackling returns equally as bad in Discord until I change it. After that, either port sounds just fine. I'm trying to figure out how I can have it sound good without having to flip the setting in PulseAudio, but I'm clueless.
All other audio seems fine. Even in games like CSGO there isn't this problem with voice chat, and I'm able to play other games, watch video, and listen to spotify just fine. It only seems to be affecting discord.
If it matters, the exact settings are "Line Out (plugged in)" and "Headphones (unplugged)" although despite the forum in the link above, I was able to set the Headphones as default anyway and it recognizes that port. I'm using the PulseAudio Volume Control (pavucontrol) app from Ubuntu Software to change these settings, and the terminal to set the default port.
My only connected audio devices are my headphones for output, plugged into the motherboard port; my mixer and headphones are listed in input (headphone mic muted), both also plugged into the motherboard. Mixer is a USB interface. My webcam was listed at one point, but I'm not sure where it has gone and if that can affect things somehow.
If anyone knows of a fix, please let me know! Thank you
sound pulseaudio headphones
add a comment |
I installed Ubuntu 18.04 less than a week ago and 99% of what I need to work has been no problem. When I first installed Discord, from the instructions on their website, everything was fine. The Snap package had problems starting and refused to go past the update sequence, as if it had no internet connection. However, the first time I join a voice chat after a reboot, I get loud crackling anytime someone speaks. It fixes itself if I change the output of my headphones from Line Out to Headphones or vice versa (headphones setting sounds better to me).
I initially thought it was the Line Out setting being the issue, so I changed it using this as a guide. That did not fix it and no matter which one I set as default, the crackling returns equally as bad in Discord until I change it. After that, either port sounds just fine. I'm trying to figure out how I can have it sound good without having to flip the setting in PulseAudio, but I'm clueless.
All other audio seems fine. Even in games like CSGO there isn't this problem with voice chat, and I'm able to play other games, watch video, and listen to spotify just fine. It only seems to be affecting discord.
If it matters, the exact settings are "Line Out (plugged in)" and "Headphones (unplugged)" although despite the forum in the link above, I was able to set the Headphones as default anyway and it recognizes that port. I'm using the PulseAudio Volume Control (pavucontrol) app from Ubuntu Software to change these settings, and the terminal to set the default port.
My only connected audio devices are my headphones for output, plugged into the motherboard port; my mixer and headphones are listed in input (headphone mic muted), both also plugged into the motherboard. Mixer is a USB interface. My webcam was listed at one point, but I'm not sure where it has gone and if that can affect things somehow.
If anyone knows of a fix, please let me know! Thank you
sound pulseaudio headphones
I installed Ubuntu 18.04 less than a week ago and 99% of what I need to work has been no problem. When I first installed Discord, from the instructions on their website, everything was fine. The Snap package had problems starting and refused to go past the update sequence, as if it had no internet connection. However, the first time I join a voice chat after a reboot, I get loud crackling anytime someone speaks. It fixes itself if I change the output of my headphones from Line Out to Headphones or vice versa (headphones setting sounds better to me).
I initially thought it was the Line Out setting being the issue, so I changed it using this as a guide. That did not fix it and no matter which one I set as default, the crackling returns equally as bad in Discord until I change it. After that, either port sounds just fine. I'm trying to figure out how I can have it sound good without having to flip the setting in PulseAudio, but I'm clueless.
All other audio seems fine. Even in games like CSGO there isn't this problem with voice chat, and I'm able to play other games, watch video, and listen to spotify just fine. It only seems to be affecting discord.
If it matters, the exact settings are "Line Out (plugged in)" and "Headphones (unplugged)" although despite the forum in the link above, I was able to set the Headphones as default anyway and it recognizes that port. I'm using the PulseAudio Volume Control (pavucontrol) app from Ubuntu Software to change these settings, and the terminal to set the default port.
My only connected audio devices are my headphones for output, plugged into the motherboard port; my mixer and headphones are listed in input (headphone mic muted), both also plugged into the motherboard. Mixer is a USB interface. My webcam was listed at one point, but I'm not sure where it has gone and if that can affect things somehow.
If anyone knows of a fix, please let me know! Thank you
sound pulseaudio headphones
sound pulseaudio headphones
asked Dec 18 '18 at 5:19
MiquedMiqued
156
156
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I fixed it by modify /etc/pulse/default.pa
. Find and replace:
load-module module-udev-detect
by
load-module module-udev-detect tsched=0
Then restart PulseAudio using this command:
pulseaudio -k && sudo alsa force-reload
1
That was it exactly. What does that do/why does that work?
– Miqued
Jan 8 at 19:14
I think it's the conflict between Discord and PulseAudio. Refs askubuntu.com/questions/371595/…
– Jared Chu
Jan 9 at 8:23
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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%2faskubuntu.com%2fquestions%2f1102738%2fcrackling-static-in-discord-with-default-audio-output-port-pulseaudio%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 fixed it by modify /etc/pulse/default.pa
. Find and replace:
load-module module-udev-detect
by
load-module module-udev-detect tsched=0
Then restart PulseAudio using this command:
pulseaudio -k && sudo alsa force-reload
1
That was it exactly. What does that do/why does that work?
– Miqued
Jan 8 at 19:14
I think it's the conflict between Discord and PulseAudio. Refs askubuntu.com/questions/371595/…
– Jared Chu
Jan 9 at 8:23
add a comment |
I fixed it by modify /etc/pulse/default.pa
. Find and replace:
load-module module-udev-detect
by
load-module module-udev-detect tsched=0
Then restart PulseAudio using this command:
pulseaudio -k && sudo alsa force-reload
1
That was it exactly. What does that do/why does that work?
– Miqued
Jan 8 at 19:14
I think it's the conflict between Discord and PulseAudio. Refs askubuntu.com/questions/371595/…
– Jared Chu
Jan 9 at 8:23
add a comment |
I fixed it by modify /etc/pulse/default.pa
. Find and replace:
load-module module-udev-detect
by
load-module module-udev-detect tsched=0
Then restart PulseAudio using this command:
pulseaudio -k && sudo alsa force-reload
I fixed it by modify /etc/pulse/default.pa
. Find and replace:
load-module module-udev-detect
by
load-module module-udev-detect tsched=0
Then restart PulseAudio using this command:
pulseaudio -k && sudo alsa force-reload
answered Jan 7 at 18:50
Jared ChuJared Chu
163110
163110
1
That was it exactly. What does that do/why does that work?
– Miqued
Jan 8 at 19:14
I think it's the conflict between Discord and PulseAudio. Refs askubuntu.com/questions/371595/…
– Jared Chu
Jan 9 at 8:23
add a comment |
1
That was it exactly. What does that do/why does that work?
– Miqued
Jan 8 at 19:14
I think it's the conflict between Discord and PulseAudio. Refs askubuntu.com/questions/371595/…
– Jared Chu
Jan 9 at 8:23
1
1
That was it exactly. What does that do/why does that work?
– Miqued
Jan 8 at 19:14
That was it exactly. What does that do/why does that work?
– Miqued
Jan 8 at 19:14
I think it's the conflict between Discord and PulseAudio. Refs askubuntu.com/questions/371595/…
– Jared Chu
Jan 9 at 8:23
I think it's the conflict between Discord and PulseAudio. Refs askubuntu.com/questions/371595/…
– Jared Chu
Jan 9 at 8:23
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1102738%2fcrackling-static-in-discord-with-default-audio-output-port-pulseaudio%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