Discord No Input Or Output Device
Mozelle Towers
When I start discord-canary, everything seems to be fine, even from the terminal, there is no noticable errors, but when I lead to the user settings in "Voice & Video", it tells me that there is no input/output devices. However, i have discord notification sounds and the internal webcam of the laptop is
working (as good as it always did (in reversed, but it's fine, I hate webcams )). But if the terminal output of discord-canary can help you, here it is:
First I tought it was package problem, so I downloaded the sources from the Discord official website and got the same result.
Then I guess a user permission problem, and I added myself to the audio group (wich is normaly no longer necessary, I have read, but... Who doesn't try get's nothing...), and then, just to see but with even less hope, to the wheel group...
As it happens on my 2 computers, it seems to be a general issue, but I didn't found anywhere a working solution (exept a guy who re-installed the .deb for his Ubuntu, if i remember right). In fact, duckduck and google were giving me very low amount of results.
That's a weird conclusion to make. If it doesn't work with ALSA chances that it has OSS support are much slimmer. And from everything I've seen, chromium/electron on linux does not have OSS (and even if it had, I doubt the discord shipped libraries link against it) support which is what discord is based on. You do have device selection with pulseaudio, that I can guarantee you. Pulseaudio doesn't have any correlation with OSS though.
Well, i'll continue to try to make it work, for both ALSA and OSS. But as pulseaudio is used for advanced configurations, I just installed it and apparently Discord needed it to work. I just talked a mate, just still a little problem, I have the sound only from one ear... But, it's better! We will manage it.
It's fine, thanks, I didn't really wanted to avoid pulseaudio. It's just that I thought it wasn't necessary, as I don't really want to put too much useless things on my setup. I was more affraid about using OSS, because I had some bugs with it, especially with my not-so-young laptop (birth in 2007-2008, if i remember right). It's time for me to learn more about pulse, it seems .
And also, after a complete afternoon, it looks that my audio bug about hearing from one side only has disapear. What is strange is that I did absolutly nothing about that, exept listening some songs, I had to deal with others things first.
I don't use headphones/microphone on discord, so far and am unlikely to start. With the windows discord app, when I change audio devices, discord prompts me to ask if I want to change audio devices. How can I get it to stop doing this? I've set input and output audio devices to default.
Even if you don't have audio built into your monitor, Windows often assumes you do. My machine also will occasionally switch to the non-existent HDMI audio out, in discord or elsewhere. And then I can't hear anyone until I manually switch back to the actual audio input.
So what is probably happening is that your monitor goes into power-saving mode, then when you become active again it detects the HDMI turning on as a "new audio device" (even if it doesn't support audio) and pops up that alert.
Go to the old Control Panel, click Hardware and Sound, and click Sound. In the list find the device that Discord keeps trying to switch to, such as the speakers in your monitors, and right-click and select disable for each.
I just migrated to macOS and I cant hear any sound coming through Discords voice chat. That includes server voice channels, private calls, voice channel live streams and also the "start testing" feature in the Voice & Video setting.
I have tested discord through chrome, and that does work, it seems like it is a problem that is specific to the app. I have also tested it with no audio interface and a different audio interface, and it seems to work perfectly fine. So I am quite sure that this is a unique Discord/RME problem on macOS (I have tested it on windows, and it works flawlessly).
I have sent Discord a support ticket, however since this also seems to be a problem specific to the RME Babyface Pro, I though I would also post here to see if anyone else has this issue, or could maybe help me out.
Hello,
has anybody news on this problem?
I have the exactly same problem with my Fireface 802 on MacOs. Discord is not outputting any voice to Totalmix. I have the same issue also with GoToMeeting.
As a workaround I am using my old Behringer Interface as output and connected it to analog-in on my Fireface.
Under Windows 10 I find GoToMeeting in Chrome unusable with Fireface UCX. The test sound works if I switch the sample rate to 32KHz but the actual meeting audio is unintelligible. I know the original post was for Babyface Pro and Mac but I'm posting here to show it's a wider problem.
Not sure if this is a good work around, but creating a Multi-Output device in Audio MIDI setup with only Babyface Pro selected, and selecting this audio device in discord outputs sound. However it is distorted (unsure what the interaction is there). Adding a audio output above the babyface seems to fix it.
I now have the same/similar setup. Fireface UCX II + MacOs 13.3 + discord 0.0.275 and creating a multi-output device in the audio MIDI setup in MacOS and selecting it in discord, as I've described above, seems to fix the issue. I can hear people talk in voice channels
I had the same issue using my Fireface UCX with Discord Voice. After selecting the Fireface UCX in Discord "Voice and Video," there is no audio. I tried the workaround above, and it worked, however! To summarize:
In MacOS, choose Applications > Utilities > Audio Midi Setup
Click "+" on the lower left side to create a new multi output device
Select the device from the available devices on the right hand side by ticking the box next to the device (Fireface UCX for me)
Rename the new multi output device (if desired). I renamed it as "Discord UCX"
Now audio is working fine in Discord through the Fireface UCX, and perfect audio quality so far, no dropouts, etc. I have replied to my support ticket with Discord and gave them this information, so hopefully the issue can be identified, or at least the workaround can be published.
Basically when I open Sony Vegas while in a discord voice channel I cant hear anyone until i leave and rejoin the channel. They can hear me but I am unable to hear them until I rejoin. Any idea on why this is happening?? It's a REAL pain.
Check your audio devices that Vegas is using. If it is using the same device that discord is using, that is what is causing your conflict. Typically pro audio editors (which vegas happens to be a DAW in addition to an NLE) will take control of an audio device in order to prevent conflicts from other programs trying to use is, this is especially true if you are using an ASIO based setup for audio. For instance, at my recording studio, if I am editing music and I try to go watch a youtube video, I have to make my DAW release the audio drivers before I can hear audio from youtube.
Look in the preferences, under "audio devices" in Vegas. You can specify which audio devices vegas is using to record or play back audio (the two can be set separately as well, so you can play back from one while recording form another).
How come I can't see anything like "realtek audio" device? I can only see: microsoft sound mapper, direct sound surround mapper, windows classic wave driver, and ASIOall V2. Should I use one of these? My default for windows is Realtek high def audio.
ASIO4ALL is buggy, it could be causing your issue. Microsoft sound mapper usually works just fine, but if you are having conflicts go into ASIO4ALL settings and make sure that you don't have 2 output devices enabled at the same time in your output (that can cause issues) and then use your ASIO device to output audio from Vegas, that should prevent Vegas from messing with windows audio playback (though I never have this issue on my system, so I think ASIO4ALL is the culprit here).
Hi, maybe it's a little bit late, but the only solution that you can do it's uninstall Asio4All driver. This is only a alternative if you don't use Asio4All driver on other audio program usually (more than Vegas). Hope it can help to you, or anyone who is reading this ;)
b37509886e