You are not logged in.
Pages: 1
Ok guys, i'm finally giving into having asking around, because this problem has been bothering me for a long time.
Recently, I started using arch linux as my daily driver. I'm enjoying it a ton, being able to fix all the things I can break and reading such an amazing wiki, but so far there is only one thing I cant fix.
Discord.
At first, it was getting it to pick up my mic and such, but in the end it seemed to have fixed it self. Right now, though, the audio is terrible. From the calling noise, to any other sound of someones voice coming through the program, is EXTREMELY static-y. The audio is so crunchy it feels like my ears were just shoved between to large bags of lays that are being crushed to smithereens.
Ive been screwing around with gnome-alsamixer trying to fix it, but nothing seems to work. I also added
tsched=0
to the end of
/etc/pulse/default.pa
to see if that would work, but alas, it hasn't brought me any luck.
According to some of the people in the /r/linux_gaming discord, this also seems to be a problem along a few other distros, so I was unsure if this was fixable, or just a glitch with discord itself.
If anyone has any more ideas, or have experienced this problem themselves and fixed it, it would be hugely appreciated if you shared it. This is the only thing so far that has kept me from having a totally smooth experience.
Last edited by Slicercrush (2019-02-03 23:38:55)
Offline
First of all revert the tsched=0 , this is a band aid "fix" that unnecessarily increases your latency, when the actual problem isn't in pulse but in this case likely discord specific.
How up to date are you? There was this thread recently suggesting a discord bug, updating to the latest version in the AUR might help here.
Should the issue continue, post
aplay -lL
amixer -c$cardindex #Index Number from aplay -l's output
pacmd list-source-outputs
pacmd list-sources
journalctl -b --user-unit=pulseaudio
during a recording attempt.
Last edited by V1del (2019-02-03 19:49:43)
Offline
Hello,
Interestingly, I've had similar problem for quite some time now and I was never able to resolve it. tsched=0 did help but never completely eliminate it. I always got a buffer underrun whenever I enabled mic recording. Suggestions where to switch from IC to dedicated audio card with hardware acceleration. I've missed this thread https://bbs.archlinux.org/viewtopic.php?id=243715 and will give their suggestion a shot. Though, I recently upgraded from a piledriver to zen, situation like this is less often now.
Regards
EDIT: Another suggestion I came across but I never pursue was to make sure that USB mic and the sound card interrupt were never on the same CPU core. With my couple of Nic cards I have on another box, I find irqbalance to do a fine job distributing load.
Last edited by bugsmanagement (2019-02-03 19:57:02)
Offline
First of all revert the tsched=0 , this is a band aid "fix" that unnecessarily increases your latency, when the actual problem isn't in pulse but in this case likely discord specific.
How up to date are you? There was this thread recently suggesting a discord bug, updating to the latest version in the AUR might help here.
Should the issue continue, post
aplay -lL amixer -c$cardindex #Index Number from aplay -l's output pacmd list-source-outputs pacmd list-sources journalctl -b --user-unit=pulseaudio
during a recording attempt.
I was looking through that post you sent me, and noticed that he had downloaded a package called
discord-ptb
instead of just
discord
After installing this version, it all worked properly! Going to research more into this to see why this specific package worked better, but thank you for the link, I am ecstatic.
Last edited by Slicercrush (2019-02-03 23:39:25)
Offline
This specific package is a newer beta version than what's released as stable, so apparently the bug was identified and fixed by discord.
Offline
Pages: 1