borine

This branch is no longer maintained, so I think there is little value in leaving the PR open. Closing.

> The "multi" alsa plugin that makes this happen seems to be the cause The multi plugin was originally designed to be used with just one soundcard. That card provides...

> Audio is very hard Using low-level tools such as alsa-lib and alsaloop to achieve complex systems is hard. You need a deep understanding of what each ALSA plugin and...

Looking at the latest logs posted in #666 it is clear the bluealsa lockups captured in the earlier logs most likely were caused by this issue after all. A specific...

Looking at the server logs, it appears that the Onkyo is dropping the A2DP transport soon after it has been acquired. Perhaps it has a timeout waiting for the first...

Have you had success with this receiver when sending music from a phone or other OS (mac/windows)? If so, it would be useful to test it with pulseaudio or pipewire...

I think I can explain the application lockups. When Bluez unexpectedly changes the transport state to "idle", the BlueALSA daemon releases the Bluetooth socket and stops the encoder I/O thread,...

If I'm right about the cause of the application lockups, then the following simple patch should fix it for `speaker-test`, `aplay` etc that use `snd_pcm_abort()` in their signal handlers. Other...

> Had to kill aplay and speaker-test and no sound. The "no sound" problem is most likely somewhere in the BlueALSA server, so my patch was not expected to fix...

Just quickly scanning through https://repairalmostanything.com/thread/767/never-wanted-onkyo-firmware I see that Onkyo receivers use Linux on the chip that performs audio decoding, networking and USB. So it is possible that Bluetooth functionality is...