You will have to narrow down and specify your question here since the client is complex and it is not clear how to reproduce the issue.

I tried https://discordapp.com/activity, selected a microphone and could see the Input Sensitivity meter move when I touched the microphone. How can I set up a call with another user or can I make a call between two tabs?

On your Linux machine:

Does https://webrtc.github.io/samples/src/content/devices/input-output/ work?

What results do you get from: https://test.webrtc.org/

- Is there a difference between with or without unified plan default on?
- I saw a conference failure due to createObjectURL being removed, anything in the js debugger?

Hi Henrika,

I feel there is an issue in Chrome itself. Chrome does not detect 3.5 jack as a microphone at all. If using USB headset or camera microphone camera microphone is detected.

https://webrtc.github.io/samples/src/content/devices/input-output/ -> No microphone

https://test.webrtc.org/ -> not working as well. 


I checked in other Linux machine from our colleague as well. His observations in his own words, 

1. Hangouts - Not working
2. Even youtube is not working
i mean audio
USB headset works in the same device

@Huib: I dont think it is related to Unified plan. I see the same with and without the flag. Infact it seem to be the same in Stable version as well(70.0.3538.77). I have tested many times earlier in the same machine with 3.5 jack. It is really strange why not working now. 

P.S: Tried with hangouts and meet as well. Thus renaming this ticket to GetUserMedia specific issue and not related to Discord app. 

I'm guessing this could be an enumeration problem, e.g. that it doesn't update properly when plugging/unplugging devices. Is this on your workstation? Which jack are you plugging it into? I've what looks like a "headphone" and a "microphone" jack and they each give slightly different results when I plug in a trrs 3,5mm headset.

I can reproduce the problem, but I seem to have some Pulse Audio issues on my machine.
Some Chrome builds use pulse and some don't. Curiously, when I run a build using Alsa alongside a build using Pulse, the pulse version detects the built-in microphone.

Assigning to ossu@ for further investigation, since this seems related to r562383.