In the tragic case that you can't hear your buddies in a voice chat, and you've gone through all the steps in this article to try and solve them, you can break out Discord's super secret ultimate weapon:
The Voice Debug Panel!
Cue glorious choir of angels.
Before we go crazy deciphering what all the fancy tech jargon means, let's walk through the steps to get here in the first place.
1. Connect to a voice channel
Pretty simple. In this case, I'll be Mambo'ing it up in Mambo#5:
2. Pull up your voice info tab
3. Click Debug!
The Juicy Details
Alright, now that we're here, there's some good stuff to note. Keep in mind, The Debug panel is pretty chock full of technical jargon and more advanced VoIP-flavored details; not all of it is stuff that you are expected to deal with, but there are some key factors that act as a great tool for self-diagnostics. Let's dig in:
Ensure Transport Options & Data Flags:
First up: These are 9 checks that Discord is doing to make sure your client voice settings match the internal VoIP system settings. (You can see each check as you mouse over them). If you have any red "X" icons here, it's a bug on our end. Not yours! We'll go over how to save & send us diagnostics later in this article.
"Wait, I can do something with these.":
Here's where the Voice Debug panel starts to help out. The Check Input Volume Levels check serves as an extra reminder that your mic is plugged in, and it's volume is normal. Cool! The Check Ping box just makes sure your ping is at a decent level. If either of these boxes aren't green, you'll find a status message that explains what's going on upon mousing over it.
Input / Output: Under the hood
This section of the Voice Debug Diagnostics just makes sure that your audio input and output devices are accounted for and acting as normal. If something's wrong here, chances are your mic doesn't want to play well with Discord, so we'll take care of it on our end.
Ch-ch-ch-Check it out:
More internal tests. Not much here will be impacted by anything you'll do, though if a particular user in the voice channel hasn't spoken yet, you'll see the orange slash:
Simple fix. Just make sure they pass some audio through, and you'll get back to the green.
It's not You, it's Me.
We know that sometimes voice channels can get a little hectic, so we included these two checks. Check Users Who Have Low Volumes will double check if you've adjusted an individual user's volume too low, where Check Users Maybe Muted will remind you if you forgot to un-mute your friend after their rambunctious little sibling's screaming tirade passed. Happens to the best of us.
The Rest of it: What's useful here?
Of the four more pages in the Voice Debug menu, they can loosely be grouped into two categories:
1. Flags & Devices:
The Flags and Input & Output Device pages are pretty straight forward; the Flags page has some more in-depth detail about what kind of Encryption, Gain Cancellation, and Echo Cancellation are being used, what numerical values your mic & speakers as well as what value your Voice Activation Delay is at, and then finally flags just make sure you didn't mute yourself in the first place. It's pretty nifty if you're into the tech stuff.
The Input & Output Device page is a reference for us if we need to see if we can align a specific problem for your hardware. That's all!
2. Users: You and I
The Local User and Users page function quite similarly as well, showing ping and latency graphs for us, and what kind of packet transmission from you to your friends is present. It's more of a stat sheet that we can use to pinpoint problems, though it is pretty cool to see how much audio information you're throwing into the web. No making fun of your friends' toaster connections though, that's just not nice.
I have a problem, I know it! What now?
This brings up the last point. We've gone through the steps (be sure to thank your wonderful support agent!), and we've pinpointed the error. To help us tackle any remaining bugs on our end, we'll most likely ask you for two things:
A. Voice Debug Diagnostics:
This one's easy. See that "Save Diagnostics" link? No? That's ok, because I'll highlight it here:
That's going to drop a .JSON file into the directory of your choice. Send that our way; it'll help us a whole lot.
B. DirectX Diagnostic Dump
(note: this is a Windows user-only process. If you're on Mac, we'll have different steps for you.)
Ahh, Alliteration. For the other piece of the puzzle, we'll take a few more steps:
1. Open your Run menu:
If you're cool like me, you can hit the Start + R keys, or just google how to use it on your version of Windows. You can do it. We believe in you.
2. Run the Diagnostic:
In the Run window, simply type dxdiag, and let it run. We know you're super excited to share your specs with us, but wait until the green bar finishes loading:
Then grab the file, hit that Save All Information button:
And that's all! We'll take the reins from here. For reiteration's sake: most of the tools in this tutorial serve as a toolkit for us to handle some more in-depth bugs. If you're not getting the info you need, or have any questions about any thing listed, please shoot your questions our way and we'll get you sorted out.