What’s the disk? Roon specifies an SSD. And it specifies macOS 10.14 (Mojave) or better. So your setup is pretty antique, though a Core i5 should be OK. I’d try upgrading your Core hardware to something that Roon officially supports. You might consider replacing that ancient version of macOS with a Linux distro like Ubuntu, which would bring you into spec if you already have an SSD.
Specs are at https://help.roonlabs.com/portal/en/kb/articles/faq-what-are-the-minimum-requirements#Typical_Usage
Hi Bill,
It’s SSD. And, I checked with Roon on whether it was supported before I recently subscribed, and it was. (Possibly, that has changed, although that has not been indicated).
Upgrades are always nice … as I well know from years of upgrading in this hobby - not the computer side.
Thanks, for your thoughts.
Hi Bill, Roon 880 seems to be, in a nutshell, very flakey. I experienced some of the issues @William_Macdonald highlighted initially - the Android App seemed to be the last to hit the world, so after updating the core, Android controllers wouldn’t work as the 880 updated controller wasn’t available. A few hours later, this was resolved.
My Roon control Apps seem to constantly lose connectivity with the core - and there’s no way it’s network/hardware related. Roon runs off a bunch of RAID 0 SSDs (Core App and DB) on the RX1217. The Syno RS3617 has 32GB of RAM and a quad-core 3.3 GHz Xeon CPU. Network is 20GB/s to the main switch and all end points are cabled in Cat6 (Cat5e to a couple of the Sonos end-points - but they’re only 100BASE-T ethernet anyway). I’m on the fastest mainstream cable internet available in the UK and my speeds regularly exceed 600Mb/s.
I’ve also experienced issues with Qobuz since the update - had to logout and login several times to maintain access.
In my >12 months experience of Roon, this is the worst it’s ever been by a long way…
Hi, couple of Pennies/Cents Worth.
I complained about an issue yesterday about meta-data (after the up-date) but after looking at other post’s thought I would give the people who are are trying to sort this out a rest as poor Rebeka must be knackered with the lack of back up she is getting and a lot of customers are getting major problems when mine is a minor problem.
The more I look at the posts the more my mind goes back to the lack of business ethics with in ROON.
If I cock something up and cover it up (developing new techniques to manufacture turbine blades for commercial airliners) a plane may come down, people may die and I may spend time behind bars. This focus’s the ball’s up response.
ROON seem to reply on diversionary tactic’s.
ROON Guy’s, it’s better to admit a ball’s up, come clean with your hands up (even if you don’t know why yet), give an explanation and advise people how far you are along the timeline of getting things back to being usable or you end up looking like the worse politician out there.
Also, I don’t come to ROON to ask for way’s of fixing something I have done in my professional career because I tend to take responsibility for my own business actions so why doesn’t ROON.
It doesn’t work, it worked yesterday, analyse, repair, get it sorted internally. If you are a volunteer community then fine but you are a business taking money of people to provide a service. Why release if you think it may cause problems, will it help the business or not to release it???
Just a bit of handy advice, I will now leave you to get on with your extra work (caused by yourselves) as I luckily can use my system and hear some music (for now). Hope all others do before the Holidays.
All the best.
OK, I finally got Roon Update 880 back up and running. It was a pretty time consuming thing for me - oh, let’s be honest, I found it a big pain! (For many of you it’s probably a minor chore).
In the end, I uninstalled Roon Core and reinstalled.on the Mac Mini. And the Roon Remote App is now also working on my Samsung Galaxy Tab S2 same as before the update.
On the bright side, it appears that I didn’t lose all my albums, artists, playlists, etc. (So, that would point to the fact that my “data was not corrupt”, in my mind. (If so, (which Roon “tech Support” said in other posts) then, the question is: “Why did the Update not work for my Roon setup, without all this trouble?” Will that ever be answered by Roon?
Setting that aside, and the most important bright spot, is the SQ. (Incidentally, (and mentioned not to boast) I have acquired a very revealing 2-channel “audiophile / music lover” system over the years. At this point, I’m referring to everything BUT the computer side of my music system. That is all the other methods of playing tunes. My “computer-fi” at this point was intended to just ‘dip my feet in the water’. Not to get in too deep AND too EXPENSIVE! But, long story short, this update - upon initial listening - is an upgrade in sound quality. Sadly, it took so long to get any tunes that I’m tired of it right now. I’ll make one more post here as I listen a bit more in the days to follow.
One final note: in order to avoid this happening UPDATE crash scenario again, I’m updating my Core machine and will be running ROCK. I (hopefully, not wrongly - nor naively) feel like if Roon can’t seamlessly update to their own ROCK operating system, then …?! (And it will negate the type of comments posted above by @Bill_Janssen -as a possible excuse / cause of any future update grief.
Unfortunately, this was not an update that I wanted to undertake (financially) in the slightest right at this moment.
Finally, thank you to all the kind and helpful people on this forum for trying to bale out what I (still) consider inadequate Roon corporate responsibility for an actual company Support system. I say, this not withstanding Rebeka’s genuine efforts and attempts to help. Thank you, Rebeka - I think you are hamstrung by a cumbersome system in an admittedly challenging diversity of customer situations.
Onward and upward with Roon! (but, beware … you’ve got competition barking around. I still like Roon and really want to support it! Please make it bullet-proof for your customers that are simply music fans who want good tune and no hassle.
Cheers to all and Happy Holidays!
I never paid attention to the updates of my Roon Core but the last few days the usability has ground to a halt. Right now I have trouble playing music from my library. Short story: Roon Core running on Intel NUC 8th Gen i7 Windows 10 that has a LAN cable to the switch that my Router is also hardwired to. I have trouble navigating the Roon Core on the NUC. Pages load slowly, artwork even slower. Clicking on things take a few seconds to register. Playing music: music is slow to load if at all. My music is stored on a 4TB SSD that is in the NUC. Playback has drop outs then stops. Roon Core disappears when view from my iPhone App even though I have it up on my NUC computer simultaneously.
I have not had any issues with Roon till recently but it’s making me yearn for the days of physical media when I could put something on and sit back and listen.
Also, some of my music zones have disappeared and/or the labels I gave them have changed.
I have 1.8 Build 882. Perhaps others have had better success?
Uh oh! Unfortunately, as of right now I can’t get the upsampling to work, anymore. (My DAC is capable up to DSD 128 and/or PCM 384). This worked fine before the update.
Also, I have yet another unpleasant ramification of this “update” to report.
I use tags quite extensively on my Roon subscription. (One of the ways I use tags is to mark the Absolute Polarity of my Tidal recordings. Then it’s just a quick flip to the correct “phase” on my system).
After the unsuccessful Update all of my Tags are gone. Just another time consuming annoyance to replace as I listen again. 
Sorry to have to report. But, Roon should be aware.
OK, for the other member’s benefit, posting this:
Jaimie from Roon sent me an email letting me know that Rebeka was away for the holidays and so Jaimie was happy to jump in and help. This was on Tuesday.
I answered, updating and recapping the situation as follows:
"Hi Jaimie,
Running now, but cannot get upsampling to work properly, as it did prior to (forced) Update 880.
My DAC does not happen to be contained in Roon’s compiled list of DAC’s in the Settings. It is an Exemplar Audio modified Oppo BDP105D (with the latest firmware which took it to PCM384 and DSD128, contrary to the original specs.). It is fully capable of this resolution. And, the prior Roon build before the Update provided upsampling flawlessly to DSD128 - to clear.
I want to get that Upsampling feature back.
My Roon endpoint is a Sonore UltraRendu (connected via Cat 8 cable) from my Core. (which was running on dedicated Mac Mini.
Today, (largely because of all this trouble) I’ve updated the machine running the core to a purpose built server running ROCK - built and setup by an IT specialist engineer, in order to avoid issues like this in the future - with Roon forced updates. Way, way past minimum specs.
Still Upsampling not working as before. Have tried all kinds of things i Settings, but, unable to figure out the problem. Could well be something simple … or the operator, lol.
A couple of other (relatively) minor issue losses also incurred. But, at this point, I don’t even want to bother mentioning these here.
Today, is Thursday … nothing further heard from Roon Support.
(I don’t even want to say what I really think). keep with the festive spirit.
Good on you for keeping a festive spirit. If I know the Roon team a little, I know that they are working hard on finding solutions for this release’s issues. In light of ever more time being consumed on the forum, a decision was made to reduce the founders’ online presence. This means that it can appear that we are not heard but I like to think the reduced online presence translates to being able to spend more time on the product. So, if your issue cannot be solved in the next day, please have confidence that it will be solved at some point. I can’t imagine otherwise. I have an outstanding issue myself but compared to what some are experiencing now, it seems futule. Anyway, I hope you can still enjoy Christman. Best, Christiaan.
I Updated to the new “Roon Version 1.8 (build 884) stable” on the new server running ROCK, yesterday. Still can’t get upsampling.
Sorry for the delay in getting back to you. Looks like you’ve posted multiple tickets to our ticket system as well as posting over here on Community. Let’s try to keep all of our communications in one place so we’re not repeating ourselves in multiple places. This also helps us to get to customers more quickly by reducing the volume of duplicate tickets. We appreciate your help with this.
I’m glad to hear that you upgraded to ROCK. That should help improve your Roon experience quite a bit.
It sounds like the problem that you’re having now is related to your Modified Oppo endpoint. Roon will recognize the default settings for certified devices but may not for older or modified equipment. Are you seeing DSD 128 as an option for the Oppo in the Device Setup settings in Roon?
A couple of questions for you:
How is the BDP-105D integrated into Roon now that you’re running ROCK?
Are the switches you’re using still in the Sonore UltraRendu signal chain?
Please provide a summary of your connection points from ROCK to the Oppo.
IE: Core>connection type>Oppo input. Please indicate which input you’re going into on the Oppo. Pictures would be helpful as well.
Thanks! We’ll get back to you as quickly as we can.
Hello again @William_Macdonald
The Oppo knowledge base states that the device has to be connected using the USB DAC input to support DSD128. Can you please check which USB input you’re connected to? Thanks!
Responding to your last two responses here:
(1) “Looks like you’ve posted multiple tickets to our ticket system as well as posting over here on Community. Let’s try to keep all of our communications in one place so we’re not repeating ourselves in multiple places. This also helps us to get to customers more quickly by reducing the volume of duplicate tickets”.
Answer: Not accurate. After I posted here and waited a reasonable amount of time for a response (here) and when none was forthcoming, I opened one Support ticket “on your system”
(2)
Answer: (a) The Oppo is not (and never has been) the problem. It worked fine (as a DAC) before 880. For the record - and as stated at the beginning of this thread - my “Roon Ready endpoint” is a Sonore UltraRendu. Nothing changed - except the Update.
(b) For the record, the fact that it is an ‘Exemplar’
Oppo (i.e. “modified”) has absolutely no bearing on the situation. This is because there is NO modification to the DAC in regards to the digital processing encompassed in the Exemplar mod.
(3) [quote=“jamie, post:35, topic:181672”]
How is the BDP-105D integrated into Roon now that you’re running ROCK?
[/quote]
Answer: exactly the same as before 880 and as detailed above.
(4) [quote=“jamie, post:35, topic:181672”]
Are the switches you’re using still in the Sonore UltraRendu signal chain?
[/quote]
Answer: Yes, same as before 880
(5) [quote=“jamie, post:35, topic:181672”]
Please provide a summary of your connection points from ROCK to the Oppo.
[/quote]
Answer: See the originally posted chain listed upon starting this thread. Nothing changed except 880. Since I was completely down I went to a ROCK server instead of the Mac Mini … even though the Mini was not the issue - 880 was.
(6)
quote=“jamie, post:35, topic:181672”]
IE: Core>connection type>Oppo input. Please indicate which input you’re going into on the Oppo.
[/quote]
Answer: Clearly, this is the digital audio input used - at all times - both BEFORE and AFTER 880. Again, nothing changed - just 880.
(7) Finally, as I notified you in response to your email to me:
After ROON later issued further update 881 after 880, I was able to get my system up and running again (including Upsampling as before 880). This was accomplished with the help of a fellow Roon member reaching out - Thank you! (Unfortunately, (in my view) not by Roon corporately).
