01-16-2023, 10:24 AM
(01-14-2023, 12:40 PM)Tim Curtis Wrote: The result of step 1 suggests that bluealsa-aplay has not been started by Bluetooth or has crashed. It's the player that Bluetooth launches when a client connection is successfully established and is what moOde looks for to trigger displaying the BT overlay screen.
After step 1 you can try:
bluealsa-aplay -l or --help for more options.
Also if it's not running (pgrep bluealsa-aplay = blank) you can try to run it manually using the MAC address of the CM150 to see if it prints any errors.
sudo systemctl start bluealsa-aplay@MAC_ADDR
systemctl status ...
Hello,
Code:
bluealsa-aplay -l
However, unless I connect another BT source to moOde, I have to manually start the bluealsa-aplay@MAC_ADDR.service to get it to work and see the BT overlay screen with the device name displayed.
I also have to manually stop the bluealsa-aplay@MAC_ADDR.service otherwise BT overlay remains displayed without device name when the CM150 is powered off and moOde doesn't fallback to MPD.
As for latency, with a length of 20 ms set for output buffer, sound and picture are almost perfectly synchronised without noticeable dropouts
So, the problem now is that the bluealsa-aplay service is not starting nor stopping automatically with the CM150.
Romain