It does, but your screenshot shows that your Roon Remote is on the Production stream, and it has already updated to the latest release (build 1353) of that stream.
As noted, Early Access is not entirely without risks. If using it, I very much recommend that you read the information that is made available, the link above and the release notes for each respective build that you will find here:
The only issue I’m seeing with Build 1354 is I have to clear the image cache multiple times per day to get album covers to display.
EDIT: This happens every time I shutdown the Roon GUI. This is on my Dell Windows 11 laptop server using Verizon cellular data. Since I’m out of town, I don’t know if this is an issue when using Nucleus or Mac Mini servers.
Still freezes. Jumping from one track to the next and to the next again on an album. Ios on iPad. Have to wipe the app and connect again. Then ok. Iritating.
I have reading lately the comments on the forum the last two build of Roon have been very problematic on iOS. But is not only on iOS, running my Roon on a synology ds3615xs I am suffering a lot of issues.
For example, long wait when changing tracks, search is slow to a point that stops Roon and music playback constantly, sometimes Roon restarts without a motive.
Streaming stops with multiple device brands, naim, Eversolo, if I zen stream, Sotm sms 200 ultra, bluesound, even streaming to iPad.
I not a network issue, because it was working perfectly two versions ago, after the 1310 update the issues started and the 1354 helped with sime but maintained the ones I described above.
I know we are on early access, but there are a lot of users on the oficial complaining about the same problems on build 1353.
Some of this issues make Roon sometimes almost frustrating to use and should be a priority on the bug listo to correct and give as a fast update to finish at least some of the issues, and make Roon fast and responsive again.
That may well be, but there are also others (most) without problems and some reporting overall improvements. What I mean is just that in software (or any technical field) it is important to name precisely how a problem presents itself because it gives hints at possible causes. Overstatement clouds the issues. Maybe the affected setups have something in common that triggers the issue(s) but it’s clearly not effecting all setups.
My iMac was in version 1297 early access, never updated and Roon was working fast as expected, no slowdowns, no network issues, simply was working as I remembered until I also updated today to the last 1354 on the imac, and now the same issues are present…
Yes, you are right, the iMac was not on for months and had an old version of early access, and for an hour or two it worked as a champion, at least until I updated Roon to the latest 1354 version, then the same issues that I Am living on the synology Roon server lately appeared.