Roon 2.0 Build 1354 Issues

I just got Roon 2.0 Build 1354. I wonder what this is?

I went against my better instincts and installed it on my Dell Windows 11 laptop. It seems to be working OK. I’ll hold off updating my Nucleus and Mac Mini pending an official announcement from Roon. I assume it’s a “clean-up” of Build 1351. “Cleanup on aisle 51.”

EDIT: I just checked my Nucleus and Mac Mini at home using Splashtop (we’re out of town) and Build 1354 is pending for them.

1 Like

Funny, I’m not seeing any updates. Staged early access update? :wink:

Probably a phased rollout that got out prematurely or someone forgot to post the announcement and change log??

EDIT: By the way, I did not have to reboot my Dell for this update to complete. It was seamless.

Part of the fun of Roon, they keep you guessing. :wink:

EDIT: It’s been 12 hours. It’s strange that Roon has not posted anything about Build 1354.

Installed well with a Nucleus+; seems to be working :wink:

2 Likes

I got this too. Hopefully @vova will let us know what is going on soon.

1 Like

Was showing as available for me last night… the popup popped up again this morning… and now it isn’t… and both (server and remote) W10 installs are showing as ‘you have the latest version’.

Odd…

The update appeared yesterday too. After completing it I realized there were no release notes.
Maybe it was pushed by mistake and then withdrawn?

Thank you for bringing this to our attention. It appears there’s been a leak in our staging rollout process, and I’m currently investigating how this occurred. I wanted to clarify that build 1354 is identical to 1353. My original plan was to release it post-production, but given that it has prematurely gone live, I’ll prioritize shipping it as soon as possible.

3 Likes

I never got the 1353 update, LOL. I am still on 1324, no harm no foul.

Hi Chris,

Build 1324 is a production release, and you should get 1353 hopefully by the end of this week as the rollout concludes.

You won’t get 1354 unless you switched over to Early Access, but that has its own risks of course.

1 Like

Just a suggestion, but maybe Early Access releases should carry a totally different numbering sequence from Production releases to help distinguish the difference. For instance, instead of Build 1354, it could be build 2354.

EDIT: I just updated my Roon Nucleus and Apple Mac Mini Roon servers to Roon 2.0 Build 1354 using Splashtop with no issues. Thanks @vova.

EDIT2: Build 1354 seems like a very good update.

1 Like

I got a 1354 update on iOS through Test Flight, which wasn’t mentioned in the belated 1354 release announcement :slight_smile:

2 Likes

Is there a EA build 1354 for Roon remote on windows? I currently have 1353 and having issues with artwork now showing up correctly…

Clear the image cache.

But, to answer your question, yes, but you have to be on Early Access. It’s supposedly identical to Build 1353 for Production versions.

1 Like

Thanks. Clearing the image cache did it. Odd as I’ve never had to do that before. Appreciate the heads up. EA build for Windows remote still says 1353, but working fine.

By the way, I’m using a Sonic Transporter for the Roon server. There’s a button in the settings to use early access which I have clicked. The server software is 1354, but remote is 1353.

1353 is not Early Access

Yesterday I was listening to music on my old smartphone which I almost always use in offline mode (where I work the connection is poor and I prefer to download the music, listen offline and try to connect only to update the server).
When I tried to connect via wifi, ARC logged out again, resetting everything and deleting all downloads (again… :tired_face:).
I’m writing it here because ARC was offline when I updated to build 1354 and the reset occurred when I reconnected and because I don’t know if it’s an ARC problem or something else

Did you read the EA instructions?

Hello. I’m sorry but the only instructions I know for EA are to click the button in the Sonic Transporter software settings.


Here’s what I currently have. Like I said, everything appears to be working fine, just wondering why the build numbers (1353 and 1354) don’t line up.

Thanks!