What can we do in order to diagnose and fix that problem?
The Airplay connection to my player is not really satisfactory, so that’s crucial for me to enable native Roon connection. I can’t imagine to buy a commercial subscription without that.
After re-flash of OS image (recommended Raspberry Pi OS with desktop image v5.10) and installation of Roon Bridge on clear OS the result is exactly the same.
Two other observations:
Restart of Ronn Bridge service also solves the problem in two situations:
when player is started and visible in Roon (with Device not found tag)
when player is inactive - then during next launch of player, Roon shows it for a few seconds as “Device not found” but then it goes to normal state and starts to behave normally.
When I launch player, aplay -l for a while shows “Subdevices: 0/1”. Maybe lack of handling of those statuses in Roon is the reason for the problems described?
Please note the exact local time + date when this issue next occurs and the name of the track that was playing and upload your Roon Logs from the Core and the bridge by using these instructions. The best way to get them over to me would be via Dropbox / Google Drive, but if you don’t have either service please let me know and I can provide alternate upload instructions.
I’ve already solved this problem. Solution is far from ideal but works if you don’t need to use your device for other audio-related purposes.
There was a conflict between ALSA and pulseuadio (that is being installed on Raspberry PI images with desktop since the beginning of the year) and pulseuadio was locking audio device for 1-2 seconds.
Removal of pulseuadio:
sudo apt -y purge “pulseaudio*”
makes the conflict impossible.
Anyway, better handling of such situation in Roon would be useful for the future and other use cases.
