This afternoon I have updated Roon Server. Roon Server (on Linux) has updated to 2.56 (build 1577) earlyaccess.
Roon on Windows 10 has updated to 2.55 (build 1559)!!!
Roon on macOS Tahoe has updated to 2.55 (build 1559)!!!
Roon on macOS Big Sur has update to 2.56 (build 1577) earlyaccess
I can run at the same time a macOS and Windows but not the 2 macOS at the same time. The macOS that first runs Roon starts flickring the UI while the second macOS keeps waiting for the Roon Server.
Hi, thank you for your report. Just to clarify, these clients have always been running a production branch? Which machine is running your RoonServer?
Thanks!
–
Ivan
Hi @ivan
My RoonServer is running on Linux (Debian 12) and is running an EarlyAccess version, the same as the other Roon clients.
As far as I know, all three clients (Windows 10, macOS Big Sur and macOS Tahoe) are (or were) running EarlyAccess versions. As a matter of fact, every time I received an update message at one of them, I received the same message at the others. Besides, I am pretty sure that the same version build were installed on them (unless the new version was only for a OS platform explicitly for any reason). I noticed yesterday that the build number was different on two of them.
I don’t use more than one client at the same time, but yesterday due to the update proccess, all three clients were running at the same time and then I noticed that when the 2 macOS were running at the same time something went wrong, in whatever order I started them. There were no problem with single clients nor the Windows one and any of the two macOS.
I even thought that could be a multicast issue, so I linked all three computer to the Ethernet. I use Windows and macOS Big Sur on Ethernet, I connected the Tahoe also to Ethernet, but it seemed that was not the problem.
Thank you for the clarification. I requested diagnostic reports from your remotes, could you please launch Roon app on those machines so that the diagnostics data can be gathered and forwarded to our servers?
–
Ivan
Done!
I started at 16:07 (GMT+1) the Windows 10 Remote, at 16:08 (GMT+1) the Big Sur Remote and at 16:09 (GMT+1) the Tahoe Remote.
On my Windows 10 Remote the Update available banner is shown right now. On the Tahoe Remote, the last started, once is running, the Big Sur (the second started) started to flash the UI from time to time and the Tahoe showed the Waiting for Server text.
Addendum: I have closed the Big Sur Remote so I let the Tahoe remote to start and this one also shows the Update availabe banner. I have this banner on the two mistaken remotes.
Just in case it could be interesting. When I clicked the update banner for launching the update process on the first Remote, the Big Sur one if I am not mistaken, the album that was playing at that point was “A Scarcity of Miracles”.
After the update, this very album couldn’t be opened in any Remote. I guess this had nothing to do with this album, I guess the issue was with the “most recently played album” that eventually was this.
I could play another album and when this album ceased to be the most recently played then I could play it again with no problem. I have had no other issues with other most recent albums, just this one after the update process.
I have updated the Tahoe Remote. It updates to 2.56 (Build 1582) production. After the update, the problem remains the same.
I am not sure why this Remote is in the Production line (as well as the WIndows 10) or how it moved to that line.
Now, I have downloaded the macOS EarlyAccess version and reinstalled on my Tahoe laptop. Now both macOS are running 2.56 (Build 1577) EarlyAccess versions… I still can’t run both macOS remotes at the same time. Just one at the time.
Windows 10 also updated and gone to 2.56 (Build 1582). Unistalled Roon and reinstalled the EarlyAccess installer. Now all the 3 remotes are on version 2.56 (Build 1577) earlyaccess.
Both macOS Remotes still can’t run at the same time. No problem with the Windows and one macOS and no problem with any of them individually.
Understood, thank you.
Can you please use the directions found here and send over a set of logs to our File Uploader from both macOS machine and post the timestamp when your reproduced the issue? Once logs have been uploaded, please let us know so that we can check the server for your files, thanks!
Thanks!
–
Ivan
The log file have been uploaded with the names Logs_acatala_bigsur.zip and Logs_acatala_tahoe.zip.
My activty prior to zip the folders:
18:28 [TAHOE] Start and play High Hopes (David Gilmour)
18:29 [BIG SUR] Run Roon. Problems begin with Tahoe UI, Gilmour keeps playing, and Big Sur is waiting for Roon Server.
18:30 [TAHOE] Stop music
18:31 [TAHOE] Close Roon. Big Sur begins to work after Tahoe is closed. Big Sur shows Update banner
18:32 [BIG SUR] Click to update.
18:34 [BIG SUR] Run in 2.56 (Build 1583) earlyaccess
18: 35 [BIG SUR] Close Roon
18:36 [TAHOE] Run Roon. It is updated also to 2.56 (Build 1583) earlyaccess. I didn’t asked on this machine, but it is updated. Anyway, it is fine.
18:37 [BIG SUR] Run Roon (Tahoe still running Roon). Same problem as before.
18:38 [TAHOE] Close Roon. Big Sur starts to work.
18:39 [WINDOWS 10] Run Roon, Big Sur still running Roon. NO PROBLEM.
18:40 [BIG SUR] Close Big Sur.
I wish this notes help you with the logs.
Thank you, @acatala!
–
Ivan
FYI. Just updated to 2.57 build 1584 EarlyAccess and it behaves the same. I guess that the issue hasn’t been addressed yet. Still, no problem running a single macOS instance, that it is my common case after all.
3 posts were split to a new topic: AirPlay2 device not working after the latest EA release