Article 5FHWP Applications no longer using Pulseaudio for output (not update-related)

Applications no longer using Pulseaudio for output (not update-related)

by
kev717
from LinuxQuestions.org on (#5FHWP)
This started yesterday and I have confirmed that no updates have been installed since Saturday. For the first half of this week, my audio has been working fine and I can capture desktop audio as needed, but yesterday I was no longer able to capture desktop audio. The vu-meter in pavucontrol remains at 0 for all outputs despite the fact that I can clearly hear desktop audio.

What I've tried:
1) restart (full power off + unplug and turn back on in case it's a hardware issue)
2) plugging in a USB audio interface (vu-meter still stays at 0 and cannot capture output)
3) using JACK (this works)
4) trying to capture from ALSA instead of pulseaudio (hw:1,0 device or resource busy)

I'm not sure what to make of this. It's working, but it's not "working" in the sense that I can capture desktop audio through OBS, audacity, ffmpeg, or any other capture script that I could use 2 days ago (and I can confirm that this started 2 days ago because I recorded a screen capture which worked fine).

Output from `pactl list sinks` (with media playing):
Code:Sink #0
State: RUNNING
Name: alsa_output.pci-0000_0a_00.3.analog-stereo
Description: Family 17h (Models 00h-0fh) HD Audio Controller Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 7
Mute: no
Volume: front-left: 40720 / 62% / -12.40 dB, front-right: 40720 / 62% / -12.40 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: alsa_output.pci-0000_0a_00.3.analog-stereo.monitor
Latency: 100089 usec, configured 100136 usec
Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY
Properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "ALC887-VD Analog"
alsa.id = "ALC887-VD Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "1"
alsa.card_name = "HD-Audio Generic"
alsa.long_card_name = "HD-Audio Generic at 0xf7700000 irq 52"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-0000:0a:00.3"
sysfs.path = "/devices/pci0000:00/0000:00:08.1/0000:0a:00.3/sound/card1"
device.bus = "pci"
device.vendor.id = "1022"
device.vendor.name = "Advanced Micro Devices, Inc. [AMD]"
device.product.id = "1457"
device.product.name = "Family 17h (Models 00h-0fh) HD Audio Controller"
device.string = "front:1"
device.buffering.buffer_size = "17664"
device.buffering.fragment_size = "2944"
device.access_mode = "mmap"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "Family 17h (Models 00h-0fh) HD Audio Controller Analog Stereo"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
Ports:
analog-output-lineout: Line Out (type: Line, priority: 9000, available)
analog-output-headphones: Headphones (type: Headphones, priority: 9900, not available)
Active Port: analog-output-lineout
Formats:
pcmIf I had to guess, I would think that applications are somehow bypassing pulse and writing straight to hw:1,0 via ALSA, but why it started doing that now is confusing.

Any idea how I fix this?latest?d=yIl2AUoC8zA latest?i=MtAZoGt02Ds:81zVnbO3-Vo:F7zBnMy latest?i=MtAZoGt02Ds:81zVnbO3-Vo:V_sGLiP latest?d=qj6IDK7rITs latest?i=MtAZoGt02Ds:81zVnbO3-Vo:gIN9vFwMtAZoGt02Ds
External Content
Source RSS or Atom Feed
Feed Location https://feeds.feedburner.com/linuxquestions/latest
Feed Title LinuxQuestions.org
Feed Link https://www.linuxquestions.org/questions/
Reply 0 comments