Unhappy with Build 923, want to revert to Build 918

I use Roon Nucleus and just updated to Build 923. Since your Build 913 followed by Build 918, you managed to hit such a sweet-spot that the sonics were very-very natural and helluva like analog. But once again, it changed in your Build 923. Maybe, 923 uses more resource as compared to 913 or 918 and hence could be the reason.

Is there anyway I can revert to Build 918 from now 923 ? Will greatly appreciate it.

Thank you!


Haha! I know what you Roon guys will say … you can’t. Lemme see if I have a backup that I’ll use to get back to 918.

Updating to New roll ups can be suicidal


Changes for Build 923:

  • Web Displays and Chromecast overhaul
  • Now Playing screen refinement
  • Resolved a bug that could lead to repeated core crashes or significant increase in outbound internet traffic from the core
  • Improvement to search results when queried on part of a complete name
  • Improvements to scrolling and graphical performance on iOS and other platforms
  • Resolved an issue causing a crash in an attempt to add a track to the library with no library performances after visiting its composition details page
  • Resolved an issue where the content would be shifted on the browser’s page with an active text filter after returning from the details page
  • Resolved widget alignment issue in Composition section of the Search results page
  • Resolved an issue with a cropped text on the Onboarding page on Mobile
  • Resolved a crash in case of pressing “/” key while Credits tab is open
  • Resolved a variety of UI issues on an iPad 6 mini in portrait mode
  • Resolved a crash on iOS caused by Thai OS localization
  • Added absent week days strings to the translation system
  • Fixed absence of certain play actions on playlist and daily mix pages
  • Fixed inactive “Device info” link on Zone Settings pop-up
  • Removed incorrectly displayed bit-depth info for lossy codecs

Nope, nothing there could account for it. Is it possible you’re imagining the difference? The reason I ask is that Roon is, and always has been, a mechanism to deliver bit perfect data from one place to another. Not bit-perfecter, or bit-not-quite-so-perfect, just bit-perfect, i.e. an exact copy. It’s hard to imagine that the minimal changes between recent builds could have any significant impact, but not so hard to imagine that somebody else could imagine they could.


It doesn’t take long for a listener (who’s also a musician) and a highend audiophile for over 35 years to figure out sonic differences between builds. When Build 913 rolled out, I had the same question as to what has Roon done to make it sound so good and once again, same answer … we don’t know b’coz we haven’t done a thing that could influence sonic quality. But it did … not only I heard it but I have a handful of other audiophiles who too immediately felt it. Many went on to say it may be using much less resources hence sound better. But who knows.

Deleted post


Your post is interesting because what you write is both true but also not so true.

It could be true if your Core is “close” to the analog side of your playback system. USB directly connected from Core to DAC being the most susceptible to SQ by software changes.

It’s not true if your Core is isolated from your playback system (streamer, DAC, etc).

These two things are a choice and what I often don’t see posted, when someone says “the sound changed”, is a description of what camp, isolated or not, their setup is in. If someone believes that how busy their Core is impacts sound quality then they would be well deserved to isolate that as a variable.

Personally, I don’t hear a difference between Roon upgrades any more often than I hear difference when I reboot my Core, streamer, switch or some other bit of gear in the chain. Sometimes I think I hear a difference but mostly not and it goes away after a listening session or two. I’m not even all that well “isolated” either but I’ve tried to keep things separated as possible.

Roon Labs have been doing this a long time. I do believe they take an interest in sound quality of Roon. But, they also have a good understanding of why Core is not influencing sound quality.

1 Like

The Roon Help database has a page about downgrading.

I really can’t let you get away with insulting Audiophiles & professionals in the community because they don’t share your views. Many have audio/HiFi industry experience that extends far beyond your “20 years of fooling…”

If contributors can’t present a rational debate & accept that others have different opinions there’s no point, or benefit, in commenting. Treat others with the same respect you seem to demand then you won’t find the alternative views so offensive.

The help offered by Roon professionals & community members is very supportive & unique, in my 50+ years of experience, hopefully you’ll learn to treat them with the respect they deserve even when you disagree with them.


Before doing any downgrading, clear the cache, reinstall the latest version, then clear the cache again.

I find sometimes the install can be a bit buggy.


Well, that’s the thing, Roon doesn’t sound like anything. There are plenty of components in a hifi chain that can change the sound, but Roon isn’t one of them, unless, as @ipeverywhere mentioned, a) your core is hooked up directly to your DAC, and b) your DAC is poorly constructed.


I have no experience with differences in sound quality between different versions of Roon but just saying bit perfect is bit perfect is wrong (at least to me). It took me two years of trials and testing before I eventually bought a lifetime license of Roon around 4-5 years ago. I used JRiver before and the biggest reason it took me so long to decide was that JRiver sounded better/different than Roon. I compared them on many occasions during that time. Both output bit perfect digital signal to my Mutec MC-3+ USB bridge but still, there was clear difference in sound quality. JRiver sounded smoother with little bit punchier and fuller sound when Roon had little bit brighter and clearer sound. My setup then matched better with the former. I can’t explain what caused this but the difference was constant every time I compared them during that time period. Eventually I couldn’t live without the superior UI of Roon so I switched to it and decided to forget the difference.

These posts make my head hurt…



Thank you for getting in touch to share your feedback about Build 923. As others have mentioned, there weren’t any changes in this update that would impact what you’re hearing sonically. If there had been we would detail those in the release notes and provide information on what was changed, and why.

I don’t want to speculate on your observations but I think oftentimes our expectations and interpretations can be influenced by our awareness that a change has taken place. That awareness triggers a different type of critical listening. We search for differences, and because of that, we often find them. Audiophiles are more prone to search for those differences, it’s just how we are! :joy:

While not wanting to appear unsympathetic to your request, as a general rule, we don’t provide a means for rolling back to previous builds. We’ve had quite a bit of experience with customers who forget to upgrade or avoid upgrading, and they always run into problems sooner than those who roll with the changes. We encourage you to spend some time with 923, the audio differences you hear now will likely diminish and new builds are being released on a 2-3 week cycle.


Hey @Sgr,

While we welcome and encourage you to share your thoughts about the new build, we ask that you not make blanket assumptions about Roon’s motivations or attitudes. The same goes when speaking about other customers.

Presuming to know the intent of others is risky; generally, assumptions say much more about the person speaking than those who are spoken about. Nobody has attacked @ARUP_GOSWAMI1 for sharing his opinion, in turn please don’t bemoan our Community for fostering behavior that hasn’t manifested. We appreciate your cooperation. Thanks.


What cache do you mean? Image cache in settings?

Hi @jamie ,

Thank you for writing to me. Indeed - upgrading is something I would always seek to do, this time unfortunately it didn’t work in my favor. We ‘long-term audiophiles with reference systems’ can hear minute and subtle changes thru our systems and the undesired change occurred immediately upon moving from Build 918 to 923 hence one can only deduce its got to do something with the software and nothing else. And “bits being bits” is also true, the undue additional loading of resources to the hardware seems to affect sonics that we hear.

I’m hoping and awaiting for another build to break thro and hopefully restore the sound I was seeking.

Thank you!

1 Like

It was @cereal_killer who mentioned a cache.

Bit of a blanket statement that assumes a lot….


These guys must have a secret handshake and sacrifice their first-born…


This sounds contradictory to me, since the hardware resource Roon uses are all in the digital domain. Regardless, if Roon’s use of resources affected SQ, then every change Roon makes that is completely unrelated to the transport (e.g. in UI, search etc.) could affect SQ, any OS update could do the same, and the whole streaming experience would just be a big gamble. I don’t think any software player development would be sustainable under these assumptions.

1 Like