-
Notifications
You must be signed in to change notification settings - Fork 28
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
pulseaudio: a52 sink doesn't stream audio from bluez source #32
Comments
I wonder if it is not because of using the plugin through a slave{} node. |
uh.. my comment self destructed? As I was saying, I tried a manual configuration (the provided, autoconfiguration doesn't create a "card", ie that can be listed by This appeared to have done the trick once, but cut out after a few seconds. Subsequently, audio from any bluetooth source streams just for an instant and is then cut off. Manual configuration:
|
This has evolved: The above configuration allows for the bluetooth stream to succeed once, per boot. If for some reason the stream is disconnected, fails, or I am not entirely sure what, subsequent attempts to stream music might make a blip before getting cut off. Take a look at pulse's output when it works (sample; basically this repeats over and over every so many seconds):
That latency seems crazy to me. Then later, when it connects but won't play any sound at all (sometimes there's a blip, often nothing):
373086903752879 usec is just shy of 12 years, btw. Maybe this is a pulseaudio problem, but why only AC3 and why does it sometimes work? |
The code comments in pulseaudio's src/modules/module-loopback.c do not inspire confidence:
|
I have filed another issue report with pulseaudio as I am not sure on which end this should be fixed. |
This issue suggests that the "extplug" approach taken by the DTS encoder is more compatible than the "ioplug" approach used by the AC3 plugin. |
Highly anecdotal, "I worked around this once" story. I worked around this once, sort of. The stream has occasional gaps. It still does not work out of the box: repeat, no. Edit: speaking of the box, that has changed: alsa-plugins 1:1.2.6-2 has been released in the Archlinux [extra] repository. Up until this I had been using the development tip. Tried to connect a bluetooth device while the output was in surround mode, POP... then silence. So I got creative. First I configured pulse for digital stereo mode (pavucontrol), and connected a bluetooth source (cellphone, bluetoothctl). That works as expected, except that bluetooth source:
has latched on to a certain abstraction device, which I call "Square Stereo", via loopback:
It attaches to the remapped stream like this even while the output is in "Digital Stereo" mode; not sure why. But that is what I wanted, anyway; thank you pulseaudio... Here's that abstraction's config from /etc/pulse/default.pa:
Next, I switched the card back to surrond mode, and to my surprise the stream continues playing! And here's some information about pulse running with this "working":
My bluetooth source is playing over my 5.1 output--particularly it is being played out of a 2x2.1 output I configured for this but I don't know how pulseaudio knows that. I'm afraid to reboot, but I worked around it once. Edit: Got this to work again with a different device. There are gaps in the audio stream. It gets annoying after a while. |
Sorry to beat a dead horse, and double if this is in fact a pulseaudio issue.
I recently configured bluez and pulseaudio to receive streams from devices over bluetooth (eg, to play audio from a phone over the PC's speaker system).
This works when the PC's sound card is set to profiles other than the A52 plugin (ie, pulseaudio's provided digital stereo output and also the DTS alsa plugin).
Only when set to use the AC3 output profile, audio from the bluez source is not produced.
pavucontrol shows the bluez source is producing sound (the level bounces appropriately), but no audio comes out of the sink (no level bounce in pavucontrol either).
Any ideas?
The text was updated successfully, but these errors were encountered: