No audio input / levels across devices, input capture formats

[smythp]

Hey folks, I've gone pretty deep on this and am a bit at my wit's end.

---

Yesterday I was setting up a new mic and got things working. Sat down at my machine today and cannot get any input from the new mic or any other input device. I don't get errors, logs look clean (to my eye). The level indicators in the mixer just sit there at nothing. I've tried:

- Adding global aux input in audio setting, using both default and targeting my mic
- Making sure I'm not stuck on monitoring in advanced audio settings
- Trying ALSA input capture source (no levels) and pulseaudio input capture (no levels)
- Making sure the track boxes are cehcked (all 6 are checked)
- Installing the pipewire plugin manually and switching to pipewire (also no levels)
- Switching from the flatpak version (what I was using) to apt stable using the PPA (just to mix things up and reset)
- A lot of unplugging/ replugging, restarting pipewire/plumber, restarting the machie, the uual jazz
- Looking in paviewcontrol to make sure stuff isn't muted. OBS is in the Recording tab and I can switch devices in there, but the volume is kinda grey and stuck on the normal level, not sure if that's usual.
- Input works fine in other utilities and I can see the levels in paviewcontrol

First, I have a couple basic questions to help me out:

- There's a visual indicator in the mixer when audio comes in, correct? On the green/red bar? I'm seeing no activity there
- In advanced audio settings, all devices are "active" but active is written in red. I have no idea if that's significant or just a weird color choice
- I am a relatively advanced Linux user but I'm visually impaired. It's possible I'm missing something really obvious in the GUI layer

cat /etc/os-release

➜ ~ cat /etc/os-release
PRETTY_NAME="Ubuntu 24.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.3 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo
➜ ~ pipewire --version
pipewire
Compiled with libpipewire 1.0.5
Linked with libpipewire 1.0.5

Log Link:

https://obsproject.com/logs/PSvd2OQ5IcuLO6jt

Really appreciate any thoughts on this.

 

[stephematician]

For the sake of trouble shooting; probably worth removing the noise suppression filter - and not run 'competing' sources; i.e. either try to get the global audio device running, or a pipewire source (within a scene), but not both at once.

The output of wpctl status could be helpful. Also; I'd look at pw-top to see what is happening at the PipeWire level when you're using OBS.

 

[smythp]

➜ ~ wpctl status
PipeWire 'pipewire-0' [1.0.5, patrick@patrick-chainguard, cookie:2364831457]
└─ Clients:
32. pipewire [1.0.5, patrick@patrick-chainguard, pid:3149]
34. WirePlumber [1.0.5, patrick@patrick-chainguard, pid:3148]
35. WirePlumber [export] [1.0.5, patrick@patrick-chainguard, pid:3148]
54. wpctl [1.0.5, patrick@patrick-chainguard, pid:45981]
92. Google Chrome input [1.0.5, patrick@patrick-chainguard, pid:41528]
98. GNOME Volume Control Media Keys [1.0.5, patrick@patrick-chainguard, pid:4216]
99. gnome-shell [1.0.5, patrick@patrick-chainguard, pid:3980]
100. GNOME Shell Volume Control [1.0.5, patrick@patrick-chainguard, pid:3980]
101. xdg-desktop-portal [1.0.5, patrick@patrick-chainguard, pid:5436]
195. OBS [1.0.5, patrick@patrick-chainguard, pid:43292]

Audio
├─ Devices:
│ 50. Raptor Lake-P/U/H cAVS [alsa]
│ 53. USB Audio [alsa]
│ 110. Shure MV7+ [alsa]
│
├─ Sinks:
│ * 42. USB Audio Analog Stereo [vol: 0.77]
│ 58. Raptor Lake-P/U/H cAVS HDMI / DisplayPort 3 Output [vol: 1.00]
│ 59. Raptor Lake-P/U/H cAVS HDMI / DisplayPort 2 Output [vol: 1.00]
│ 60. Raptor Lake-P/U/H cAVS HDMI / DisplayPort 1 Output [vol: 1.14]
│ 61. Raptor Lake-P/U/H cAVS Speaker + Headphones [vol: 0.89]
│
├─ Sink endpoints:
│
├─ Sources:
│ 40. USB Audio Mono [vol: 0.85]
│ 62. Raptor Lake-P/U/H cAVS Headphones Stereo Microphone [vol: 1.00]
│ 63. Raptor Lake-P/U/H cAVS Digital Microphone [vol: 1.00]
│ * 122. Shure MV7+ Mono [vol: 0.96]
│
├─ Source endpoints:
│
└─ Streams:
176. OBS
115. monitor_MONO
194. input_MONO < Shure MV7+:capture_MONO [active]

Video
├─ Devices:
│ 45. Integrated Camera [v4l2]
│ 46. Integrated Camera [v4l2]
│ 119. Elgato Facecam Pro [v4l2]
│ 198. Elgato Facecam Pro [v4l2]
│
├─ Sinks:
│
├─ Sink endpoints:
│
├─ Sources:
│ * 56. Integrated Camera (V4L2)
│ 171. Elgato Facecam Pro (V4L2)
│
├─ Source endpoints:
│
└─ Streams:

Settings
└─ Default Configured Node Names:
0. Audio/Sink alsa_output.usb-Generic_USB_Audio_20210726905926-00.analog-stereo
1. Audio/Source alsa_input.usb-Shure_Inc_Shure_MV7__MV7__4-d930a0f50b3c6b5a94296bc07abb85d9-01.mono-fallback
➜ ~
➜ ~ wpctl status
PipeWire 'pipewire-0' [1.0.5, patrick@patrick-chainguard, cookie:2364831457]
└─ Clients:
32. pipewire [1.0.5, patrick@patrick-chainguard, pid:3149]
34. WirePlumber [1.0.5, patrick@patrick-chainguard, pid:3148]
35. WirePlumber [export] [1.0.5, patrick@patrick-chainguard, pid:3148]
54. wpctl [1.0.5, patrick@patrick-chainguard, pid:49352]
92. Google Chrome input [1.0.5, patrick@patrick-chainguard, pid:41528]
98. GNOME Volume Control Media Keys [1.0.5, patrick@patrick-chainguard, pid:4216]
99. gnome-shell [1.0.5, patrick@patrick-chainguard, pid:3980]
100. GNOME Shell Volume Control [1.0.5, patrick@patrick-chainguard, pid:3980]
101. xdg-desktop-portal [1.0.5, patrick@patrick-chainguard, pid:5436]
195. OBS [1.0.5, patrick@patrick-chainguard, pid:48084]

Audio
├─ Devices:
│ 50. Raptor Lake-P/U/H cAVS [alsa]
│ 53. USB Audio [alsa]
│ 110. Shure MV7+ [alsa]
│
├─ Sinks:
│ * 42. USB Audio Analog Stereo [vol: 0.77]
│ 58. Raptor Lake-P/U/H cAVS HDMI / DisplayPort 3 Output [vol: 1.00]
│ 59. Raptor Lake-P/U/H cAVS HDMI / DisplayPort 2 Output [vol: 1.00]
│ 60. Raptor Lake-P/U/H cAVS HDMI / DisplayPort 1 Output [vol: 1.14]
│ 61. Raptor Lake-P/U/H cAVS Speaker + Headphones [vol: 0.89]
│
├─ Sink endpoints:
│
├─ Sources:
│ 40. USB Audio Mono [vol: 0.85]
│ 62. Raptor Lake-P/U/H cAVS Headphones Stereo Microphone [vol: 1.00]
│ 63. Raptor Lake-P/U/H cAVS Digital Microphone [vol: 1.00]
│ * 122. Shure MV7+ Mono [vol: 0.96]
│
├─ Source endpoints:
│
└─ Streams:
176. OBS
115. input_MONO < Shure MV7+:capture_MONO [active]
194. monitor_MONO

Video
├─ Devices:
│ 45. Integrated Camera [v4l2]
│ 46. Integrated Camera [v4l2]
│ 119. Elgato Facecam Pro [v4l2]
│ 198. Elgato Facecam Pro [v4l2]
│
├─ Sinks:
│
├─ Sink endpoints:
│
├─ Sources:
│ * 56. Integrated Camera (V4L2)
│ 171. Elgato Facecam Pro (V4L2)
│
├─ Source endpoints:
│
└─ Streams:

Settings
└─ Default Configured Node Names:
0. Audio/Sink alsa_output.usb-Generic_USB_Audio_20210726905926-00.analog-stereo
1. Audio/Source alsa_input.usb-Shure_Inc_Shure_MV7__MV7__4-d930a0f50b3c6b5a94296bc07abb85d9-01.mono-fallback

I created new logs just with pilseaudio added as a source. But I've had a lot of combos of global and scene-based inputs during troubleshooting.

New logs:

https://obsproject.com/logs/CZAKcKEsSbcsDprL

Do you know if the "active" in red on the advanced audio settings means anything?

 

[stephematician]

Regarding your specific questions.

1. There's a visual indicator in the mixer when audio comes in, correct?
   Yes, you mean something like this - the bright part represents the level of the input:
   
   
2. In advanced audio settings, all devices are "active" but active is written in red...?
   Yes, it means almost nothing for most sources, just that the source was initialised (I see some exceptions on Windows and Mac). It is documented here: https://docs.obsproject.com/reference-sources#c.obs_source_audio_active
3. I am a relatively advanced Linux user but I'm visually impaired, I may have missed something:
   If this does turn out to be the case; let me know if you want me to raise an issue/ticket to improve the UI or if you need any help to raise one yourself. I'm not an expert in OBS's UI implementation, so I wouldn't be the best person to tackle the implementation, but I can at least test and review the code etc.

The output of wpctl looks promising; here's what I see in the "Streams" section related to OBS:

       100. OBS: Audio Input Capture (PipeWire)                         
            104. input_MONO      < Behringer C2 Voice Filter:capture_MONO    [active]
            135. monitor_MONO

Basically the same thing you're seeing. That and the default configured node name for Audio/Source at the end looks about right, too.

In your log, OBS looks like it has identified the default audio input:

09:31:05.504: pulse-input: Server name: 'PulseAudio (on PipeWire 1.0.5) 15.0.0'
09:31:05.505: pulse-input: Audio format: s32le, 48000 Hz, 1 channels
09:31:05.505: pulse-input: Started recording from 'alsa_input.usb-Shure_Inc_Shure_MV7__MV7__4-d930a0f50b3c6b5a94296bc07abb85d9-01.mono-fallback'

- Input works fine in other utilities and I can see the levels in paviewcontrol

Can you show me what you mean by this vs what you see for OBS in pavucontrol?

Also - do the other microphones work in OBS?

 

[smythp]

Really appreciate your conscientious and generous reply.

Thanks for responding to the questions about the UI. That's what I assumed about the levels and the red text for "active."

Below are screenshots from Paviewcontrol. I am testing with the Shure mic (though I have tried other mics now). I can see levels in the input tab in Paviewcontrol but I get no levels and nothing records in OBS. I also attach a screenshot of the Recording tab, and for fun a screenshot of my OBS interface with the advanced audio settings open.

Other mics do not work and exhibit the same behavior.

Does the output suggest I have a voice filter on? I don't see any filters when hitting the filters menu on the source in the mixer.

I'll be traveling for some time after tomorrow so if I don't respond I haven't forgotten about this thread. Thank you again.

 

[stephematician]

It was only in your original log that I saw a "Noise Suppression Filter". In the new log it wasn't there; so I'm going to assume that wasn't the issue.

The fact that other microphones are not working in OBS is interesting.

Is "Enable Push-to-talk" deselected in Settings -> Audio -> Hotkeys?

 

[smythp]

Good trouble shooting thought as it does seem to be something global set in the software since it's such a blanket effect. But the hotkey seems to be disabled.

 

[CoryL]

If all your mics are dead in OBS, it’s likely an issue on the software or system side. I’d try launching OBS in portable mode (obs --portable) with a fresh config and see if that makes any difference with the levels.

 

[smythp]

OK, I closed out OBS, nuked the config, and started in portable. The settings were reset. I a dded a source (Shure mic) and no levels. Then deleted the defaulte global desktop and aux inputs and tried it, no levels. Could there be a permissions issue or some way it's gettingmuted going in?

 

[stephematician]

I'm pretty stumped as to what could be wrong within OBS (flatpak or APT); this seems like there's something going on with the system. And have you tried the Pipewire capture plugin again (with no other sources attempting to use the device and with monitoring OFF)?

Might also help to attach the output of pactl info > pactl.info.txt and pactl list sources > pactl.sources.txt?

 

[whutwhutwhut]

I'm having the same issue. Audio works in Audacity but no sound in videos recorded in OBS. The audio meters don't respond at all during recording, but in sound settings testing my speakers work just fine. When I import the video into Kdenlive, the audio track is flatline. When I import it into Audacity it is also flatline. But recording audio into Audacity works just fine and imports just fine into Kdenlive. I switched up USB ports and cables and got the same results.

 

[Babs Johnson]

Sorry I'm late to this party, I can't help but noticed that the audio isn't set to "monitor and output" which should give you sound.

Sometimes it's the simple things.

 

[stephematician]

Sorry I'm late to this party, I can't help but noticed that the audio isn't set to "monitor and output" which should give you sound.

Sometimes it's the simple things.

• "Monitor off" should result in the audio being processed but not heard on the monitoring device (e.g. a headset) while using OBS and it should be:
  • visible in the peak meter,
  • be heard in both streaming and recording.
• "Monitor only" should mute the audio output in the stream or recording video, and will still;
  • be visible in the peak meter,
  • be heard on the monitoring device (e.g. headset) while using OBS
• "Monitor and output" means the audio is heard while using OBS, is visible on the peak meter, and is also present in recording and streaming.

I don't see how this setting will change the result if the audio device seems completely mute (even on the peak meter).

@whutwhutwhut - looks like you're using Mint and Flatpak version of OBS, right? Have you tried other versions of OBS (either flatpak or via APT) and got the same result?