@benjamin thanks, I tested with an Ethernet adapter as well in the meantime. Switched off Wi-Fi to be sure it is using the Ethernet connection… It too runs very nice and without any noticeable gaps, perhaps one or two seconds sometimes when switching to 192/24, but I think that this is absolutely acceptable.
And yes, MBP has an 8-core i9 CPU.
If I may ask, do you now also recommend replacing the M.2 SSD of the Nucleus? I would like to hear your opinion, just to have an “official” statement. Or are there other things to check before?
Just another user, again, but …
… backups contain the core’s database of library and settings only, which is operating system agnostic - so no worries needed here.
@benjamin, today I had an IT expert colleague do a health check on my M.2 SSD in the Nucleus - nothing wrong, all values in the optimal range, no bad sectors, etc.
The RAM modules have also been checked, they are fine, too.
What can I try next to get closer to a solution?
No offence, but I would really appreciate some feedback.
@Axel_Lesch, the MacBook Pro is only my interim solution so that I can listen to music while I search for the error on the Nucleus. Unfortunately, I have not received any answers from the support here in the thread, only counter-questions, and am now trying to find the error on my own. In the course of this, I will also replace the M.2 SSD of the Nucleus and check whether the system then copes better.
This is very poor service from support that they have not responded to your issues. No excuses for this when it’s their turnkey product that appears to be the issue.
Hey @UliR
As I have some time now, I would like to warn you that even a new SSD with your Nucleus may not completely solve the problem.
I have a concern about this:
Dealing with implicit messages is not easy. They have a great advantage that you don’t have to commit yourself, in case of doubt you can always deny and if all else fails, suspect the interpreter of not only good intentions. (Which I, explicitly speaking, do not have regarding Roon.)
What I didn’t realize until now was that your Nucleus Rev B only comes with an i3 processor.
So far I have always overlooked it, reading just Nucleus, and thought all good, - that could be wrong.
You may have already received the answer.
If you wanted to buy a NUC for Roon OS ROCK, would you even consider an i3 processor?
With the hope for a snappy gapless performance? And this is probably where the rub lies in connection with the latest updates, which may have changed something crucial.
Perhaps.
If you do some research, you can start thinking about it.
You wrote in this thread:
There was a post a little earlier, regarding the same problem you are having:
And a little earlier there was a post from @Danny regarding hardware requirements. Who may now be the only one who can clarify the specs required for a Nucleus today:
If you pick out the essentials here:
The Nucleus would hit CPU limits if you increased RAM
competing on hardware spec is not something we care to do because it doesn’t take into account software.
]…] will tell you that the iPhones all feel like they have better specs. It’s because iOS is tuned to make it feel great. Software decisions in iOS, like little-to-zero processing of backgrounded apps is the big reason why RAM is far lower than on all iPhones compared to […]
Fair enough.
But the question remains, what happens to a Nucleus if at some point, after an update perhaps, it turns out that “software tuning” is no longer sufficient to compensate for under-specced hardware …
or do we have to assume that this case will never happen?
As already mentioned, I would be glad if this turns out to be unfounded and your problem has another cause.
All the best.
Thanks @Axel_Lesch, for all the details. It is my great fear that my Nucleus rev B, which is a good 2 years old, simply no longer has the hardware power that Roon requires. No matter if with the original 4 or now with 16 GB of RAM.
However, I cannot accept the fact that I have up to 20 seconds pause between tracks, which does not correspond to my expectations of Roon. So I might have to buy new hardware for a core and make a flower pot out of the Nucleus. That would be a shame, as the device was not exactly a bargain.
At the moment, I just want to be able to listen to music sensibly and undisturbed again. This whole issue is no fun or pleasure for me, it’s just annoying.
An i3 is more than enough for Roon, my back up NuC is an i3 and has no issues like this at all and I have 3 x as many tracks as @UliR and run DSP. Increasing Ram is the first thing support recommend for larger libraries as well. I dont think this has anything to do with his issues especially given the low track count.
I really don’t know what I have done wrong, but it seems that I have done something wrong and thus am ignored here.
Well, it doesn’t help, but I would appreciate a clarification @support. Feel free to PM me.
@CrystalGipsy I installed build 1211 this morning, and even using my alternative Roon core (the MacBook Pro - the Nucleus is still turned off) I’m now back to 6 - 15 second gaps between tracks with different sampling or bit rates. This started immediately after the update and a reboot of the Mac. Before I had no gaps. I wonder whether I now have to, again, check the router, switches, network cables, ISP or even my “new” Roon Core, which had not shown any gaps before the last update.
I have not noticed gaps yet but I have not been playing from qobuz much of late.
Are you using any DSP at all in your signal path. Are you using cloudflare or google dns? Do you get the delays playing direct from system audio on the Mac?
Looks like this things take time. 
