With ao=alsa mpv does not close sound card when paused
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 37k
- Forks
- 3.5k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 22
Description
- mpv version: 0.33.0
- Linux Distribution and Version: Tiny Core Linux 11.1 x86_64
- Source of the mpv binary: I compiled from github tarball
- If known which version of mpv introduced the problem: Not known.
- Window Manager and version: fluxbox 1.3.7
- GPU driver and version: Mobile 4 Series Chipset Integrated Graphics Controller, driver=i915
Reproduction steps
Expected behavior
A few seconds after video playback is paused, "grep RUNNING /proc/asound/card*/pcm*/sub*/status" should return no hits. This is the observed behavior when mpv is compiled without the "--disable-pulse" flag and run on a system that has PulseAudio.
Actual behavior
mpv compiled with "--disable-pulse" flag runs fine on an ALSA-only system, but when playback is paused, "grep RUNNING /proc/asound/card*/pcm*/sub*/status" consistently returns "/proc/asound/card0/pcm0p/sub0/status:state: RUNNING". Other sound-producing applications (e.g., Brave browser) exhibit the expected behavior when running on my ALSA-only system.
Log file
Sample files
Any video or audio file will do.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the pause behavior with mpv built using --disable-pulse and inspect the linked output.txt log. Check /proc/asound/card*/pcm*/sub*/status before and after pausing with an ALSA-only system; done means no status entry remains RUNNING a few seconds after playback is paused.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100