I'm currently working with the Roon Audio API to connect an external Linux device to Roon and build a Roon Relais. My Roon Server (Win 11) is running 2.48 (build 1517), and the Roon Client on my Win 10 PC has the same release.
When I start streaming via the API, the Roon Client on the Win 10 PC crashes. When I restart the client, it crashes again immediately as long as the Audio API streams data.
Using the Roon App on my iPad I encounter no crash and see the correct GUI. Also I can use Roon there with no issue. See attached Foto.
I suspect there's a bug in my Win 10 client GUI, because the music is correctly passed through Roon and arrives as it should at the audio streamer.
This is a screenshot from my iPad during URL playback:
I also have an additional request:
Would you please be so kind to tell me how to enable the “Next” and “Previous” buttons in the GUI (disabled in the screenshot above) and how to set and catch the events if I click on them.
Thank you for the report. We’ll need a set of logs from the affected Windows 10 PC Roon instance. At your convenience, please use the directions found here and send over a set of logs to our File Uploader?
We’ll investigate the failure and proceed from there. Thank you!
Hi @DrCWO,
Thanks for letting us know. We’ve spoken with our developers about your case, and it looks like they’ll need to conduct a deeper investigation. While I can’t provide an exact timeline, please know we’ll keep you in the loop with any updates as we receive them. Let us know if anything changes in the meantime!
I checked the ticket status and it looks like some work was completed, but the ticket is still in the QA testing phase. Please be on the lookout for improvements in our next Early Access release and then the Production one following the EA release, thanks!
Hi @DrCWO,
Thanks for the update. I checked on the status of the fix and, unfortunately, it wasn’t included in the most recent release. I know that’s not ideal — sorry about the delay. While I can’t provide an exact timeline, the fix is still on track and should be coming soon. We’ll keep you posted here as soon as we have a more definite update.