What kind of performance/speed issue are you experiencing?
· Adding music to library take a long time/doesn't complete
Please try to reboot your Roon Server
· No, the issue is still the same even immediately after a reboot
Please try to reboot your networking gear (Router/Switches/etc.)
· No, the issue is still the same even after a reboot
Is there any change in behavior if you try to navigate to Roon Settings -> Library and set both Background and On-Demand Audio Analysis to Throttled or Off?
· No, the issue is still the same
Does the issue happen on multiple Roon Remotes (controllers) or just one?
· Issue happens on multiple remotes
Router Domain Name System (DNS) change
· I was able to change my router's DNS servers but it did not help
What is the operating system of your Roon Server host machine?
· Nucleus
Which model Nucleus do you have?
· Nucleus One
Timestamp of issue occurrences
· most days
Describe the issue
Ever since I purchased a replacement for my NUC (I went with Nucleus One) I have been having multiple problems. 1. ARC fails to download. 2. Roon is slow (takes a while to find server, takes a while to add files, regularly stops playing music mid-way through a song, says it is having issues. It was difficult to fill out your forms for this chat because it asks very specific questions but does not allow multi-select. Truth is, I am having issues with majority of items on your list. Of course I truly do not know what the problem is, but a simple view: I use NUC, everything works great. I replace with Nucleus, everything starts behaving poorly. I also want ARC to work in the worse possible, way, but it SUCKS. Sorry, but I have reported - you have done updates - it is a great idea, but it does not work (but that is another ticket I suppose). Basically, I am having buyers remorse. I pay for lifetime + Nucleus - your branding implies high quality, but gives nothing bus problems. Please help me troubleshoot this and/or refund purchase.
'typical home setup" is not going to help with any sort of troubleshooting, as frustrating as it is you need to give more information if you really do want help in making the Nucleus One work for you.
Buyers remorse is difficult to deal with, but the more information that you can add in this thread will make it easier to help you.
I am happy to fill out everything I have at home. but the form does not add specifics. I am slammed right now both at work and personal life, so 7 days may not be long enough before they close this. Please: ask me specific questions about my setup and I’ll try my best to fill out the data for folks. I just know on the form itself it did not ask specifics, just a generic question, for which I did not have the time to go look it all up. I do appreciate anyone’s thoughts and help. But you gotta understand, I watched the seminars on home network and did everything I could to match what was recommended. Something happened recently, and suddenly nothing is working. I keep hoping there will be some upgrade that fixes things, but for now I have no clue.
So sorry for the delay in an official response to this report. Our apologies that we haven’t reached you sooner.
First off, we recognize that this type of differential diagnostic troubleshooting with hi-fi networked audio is incredibly frustrating, particularly when the cause of the problem isn’t clear. It’s our plan to take the burden off of you from here forward by providing instructions that, if not simple, are at least relatively straightforward and clearly laid out. The problems you’re describing with ARC and your Nucleus One aren’t expected or normal for the system configuration and library size you’ve described.
We’ll similarly ensure this topic thread stays open until we’ve reached a clear resolution here.
Diagnostic logs from the Nucleus show two out-of-memory events. Usually, this would point to the library and associated metadata exceeding the spec’d RAM limit for the Nucleus One (about 100k) tracks. But your library has neither the track volume nor the volume of associated metadata to cause problems on this unit during indexing.
The actual cause of the crash doesn’t seem to be a leak; the server is going just over the treshhold because of two main factors.
First, there’s the downloading of Opus files to ARC. To prepare these for playback on the phone at 48Khz, the server performs some very heavy upfront transcoding in short bursts.
Second, there’s a queue of about ~900 unidentified albums that Roon is churning through while attempting to match them to known metadata.
Twice in logs, these download-transcoding bursts to serve ARC happened concurrently with the identification churn. This identification was backlogged because it did not complete during scheduled Background Work.
As a quick test, please try the following:
In ARC Settings, set the download quality to either “original format” or “CD Quality” and attempt to download files to ARC
Please try a “Clean Up Library” in Settings → Library
Please share a screenshot of the Skipped Files list from that same page
We’ll watch for your response. This will inform next steps and we’ll proceed from there.
Circling back on this to see whether you had a chance to try the ARC download quality change, set it to original format or CD Quality and see if downloads still trigger the issue. We also asked you to run Clean Up Library in Settings > Library and send us a screenshot of the Skipped Files list from that same page, so if you have those results, please share them when you can.
Please note, if we don’t hear back from you this thread may close automatically soon. If the thread auto-closes and you need further assistance, please submit a reopen support request via the technical support help form below and specify that the issue should be reopened. Thank you.
Hi I just saw this. I have been on vacation (and slammed getting ready for vacation). I have this page popped up on my browser to remind me to take whatever next steps. I really appreciate your note and willingness to help. I will follow up as soon as possible.
Sounds good @Karl_Mayhew! No rush at all, we’ll be here when you return. If the thread closes, you can access the Typeform to request the thread be reopened easily.
