Closed c02y closed 3 months ago
I see (hear) the same on Fedora 39.
Connect Bose QC35II via Bluetooth, listen to something in native Firefox, start playing something in Flatpak mpv - headphones turn completly silent, playing test sounds in Gnome Settings are not heard - close Flatpak mpv, wait 10 seconds and sounds are working again.
Sporadically doing this reproducer will lead to the sound device of the headphones being completly lost when starting flatpak mpv. The headphones are still connected (confirmed bluez and gnome settings), but in sound settings only the built-in speakers of the notebook is listed. Closing mpv and turning the headphones on and off fixes the issue again.
I think this is the corresponding issue for this topic over at pipewire
with some more discussion and details:
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3384
I experience the issue sporadically also (using Manjaro, mpv from Manjaro repos v0.37, mpv audio-device=pipewire) with similar log entries (out of buffers
) as reported by @c02y .
The issue is difficult to reproduce reliably. As others have stated, audio is "lost" after switching back to play media from mpv
after playing media in another application (usually firefox
in my case) with a bluetooth audio device connected. I only recently switched to pipewire
, and never experienced it previously with pulseaudio
.
pipewire-1.0.6
(released 2 days ago) contains a potential fix for this issue. Can you still reproduce the issue on 1.0.6?
@Mershl I'm using pipewire-1.0.5 (Archlinux) right now, actually this issue has been gone for quite a while, I'll add an update if it happens again.
But I got another issue recently when I'm playing some game, when I try to launch a game or open some page inside the game, my audio will change, it seems it switches to another channel or something like that, the timbre is different and I will get an audio just like you toggle Bluetooth speaker on and off. It happens in just around 2 seconds, it will be normal again. Not sure it is the issue of pipewire though.
I've actually seen (heard) the same when trying to start certain games on Steam (the game was Zero Escape via Steam in my case).
Seems like this issue with mpv can be closed though.
Important Information
Provide following Information:
0.36.0-1
ArchLinux
Arch Linux repo
several versions across a few months
i3wm, 4.22-4
nvidia 535.104.05
If you're not using git master or the latest release, update. Releases are listed here: https://github.com/mpv-player/mpv/releases
Reproduction steps
Try to reproduce your issue with --no-config first. If it isn't reproducible with --no-config try to first find out which option or script causes your issue.
Describe the reproduction steps as precise as possible. It's very likely that the bug you experience wasn't reproduced by the developer because the workflow differs from your own.
Sorry I cannot reproduce this issue, since it happens totally randomly, sometimes if I play some video with MPV, my Bluetooth speaker is muted or maybe disconnected, the status of my Bluetooth device is not mute, but no sound comes out from the MPV video or other application such as Firefox which is playing YouTube video, I have to reconnect my Bluetooth speaker manually, then the sound is back to normal.
If I close the MPV window and replay the same video file, it won't happen again. This kind of issue only happens when I try to open some random video with MPV.
I know this is a tricky issue since it happens totally randomly, it already happened over ten time in the last few months.
I don't know what other info I can provide, if you need any info, please let me know.
Here is the
journalctl -xe
log for that period of time:Expected behavior
Actual behavior
Log file
Make a log file made with -v -v or --log-file=output.txt, paste it to https://0x0.st/ or attach it to the github issue, and replace this text with a link to it.
The issue will be closed for ignoring the issue template.
Sample files
Sample files needed to reproduce this issue can be uploaded to https://0x0.st/ or similar sites. (Only needed if the issue cannot be reproduced without it.) Do not use garbage like "cloud storage", especially not Google Drive.