-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
a52 plugin crashing pulseaudio #28
Comments
Please try to catch the crash with gdb and check the backtrace, identify which place it's triggered. |
It seems that something is slow. PA with |
Here's pulseaudio getting started by systemd and then killed, a couple of times, from
EDIT: I tried adding Good news: pulseaudio does not immediately die when a client attempts to send audio through plug:a52 Bad news: CPU usage maxes out and no audio is produced. In fact, even |
BugLink: #28 Signed-off-by: Jaroslav Kysela <perex@perex.cz>
Try latest sources from repo, please. |
Also, try tsched=0 for PA. It's a blind shot, but this is always the first thing for a problem on PA. |
AFAICT your recent two commits probably fixed the problem :) Let's just wait for the @quequotion final test... :) |
Indeed, this has done the trick! How do I buy all of you a round for the Zoom party we're having when this gets to release? |
Ever since f11e7a8, the recent commit that brings the a52 plugin up to speed with ffmpeg's requirement for s32le format sampling, sending any audio to plug:a52 from any pulseaudio client crashes pulseaudio.
I posted this log earlier in #23, in which audio from mpv crashes pulseaudio.
I have tried other clients since and they all crash the same way.
This is with a default pulseaudio configuration, as shipped in Archlinux, and the following
/etc/asound.conf
:To enable the use of plug:a52 in pulseaudio without configuring it manually, I select the "Digital Surround 5.1 (IEC958/AC3) Output" profile in
pavucontrol
.Pulseaudio, as far as I know, is agnostic of how ALSA plugins work internally. This leads me to think there is something not getting done right in the new patchset, even if it is tolerable in an ALSA-only setup.
The text was updated successfully, but these errors were encountered: