And you won’t, I’d guess, because there are simply too many moving parts there for an informed opinion. Which DSP? For how many endpoints? How often? Etc.
If you’re looking for multichannel, @Archimago has been going on about it for months. See, for instance, Archimago's Musings: HUNSN [CWWK] RJ36 Fanless MiniPC: Intel i3-N305. Power-limiting, setup, Roon outputs - multichannel, crosstalk cancellation DSP, direct USB..
Would not say that. We have narrowed down the choice of CPU to a handful of models and I am familiar with several of these modern faster quad-core Celerons. Their performance is somewhere between the old Nucleus and Nucleus+. Added DSP and converting from DSD128 6-channel is not a problem with these ones.
Hi, looks will be a very good product for 98% of the market. In my case I need some clarifications about the technical content.
In my case, I have more than 300K songs in different formats, going from DSD, SACD, Hi Res ALAC, hi-Res Flac, common CD 16-44.1 resolution and some MP3 at 320 bits.
Reading the specs seems that can process DSP and handles 100K files. If I have NAS (that also I saw is supported), this box will be able to replace a NUC Rock (Intel based I7) and be more efficient?
Because now NUC is wth ASUS, and the newest version of NUC 13 is not certified at this time, seems that ROCK will be replaced at some point, in this case I believe Nucleus One or succesors.
Is this box equivalent as a I3, I5 o i7 processor?
Thanks in advance
Jaime
You can stop right there. Nucleus One does not support music libraries of that size.
AJ
Hi AJ, if that is the case is ok. However let me explain the reason of the question.
If you are using a NAS, the data music data is stored somewhere else. So you only have in the Roon Nucleus the content of the database will be about 20 GB. The real trouble start when you are using DSP, where the processor handles the audio conversion. In my case I am not looking for Nucleus One can handle my entire library.
I can see a real value in the box itself because I have used rock for several years, and had install several NUC with different configurations as my library grows. Having a manufactured box from the owner of the tool and could be supported in time if something that I want to invest, of course if works for me.
Now compared with the investment with a NUC (looking for memory, SSD and Intel Processor) is about 650-900 USD depending of the components, so the Nucleus One is affordable, if DSP works properly.
You’ll be better off with a Nucleus Titan with libraries of that size. Roon lists the maximum for the Nucleus One at 100.000 tracks.
From the German review posted earlier in this thread it seems the Nucleus One comes with a quad core Intel Celeron CPU and 8 gb of RAM. Totally not able to handle a 300k track library.
Edit:
I don’t think it matters. Tracks from Qobuz and Tidal also count towards the number of tracks in your library. Not just the tracks that are physically available on the Roon Server itself.
Thanks Sands, this is what I am asking for.
The way Roon works makes no difference where the music is stored. It’s about the ability to process the database and search it and process requests.
As the database gets bigger the processor and memory requirements goes up.
For your size of library an i7 and probably 32 GB would be recommended
Thanks Michael. i7 will be.
What specific hard drive do people plan on installing in this?
I provided a couple screenshots of the signal path as specific examples of my use case. I had hope with such specifics I would get an answer whether or not the Nucleus One could handle it. The gentleman from Roon Marketing responded he wasn’t set up to test such a use case. Certainly someone at Roon could?
I can understand as a general statement there are too many variables for Roon to be more specific about Nucleus One’s multichannel/DSP abilities, but when presented with a specific use case, certainly they know, or could find out?
I agree with you answers from Roon aren’t likely. Customers will have to just buy, and return if it doesn’t meet their needs, or rely on the kindness of other owners to test it. 
Thanks for the link. I’ll check it out. 
(Edit: Ah, I see he is talking about setting up a Roon endpoint, not a server.)
I’ve not seen anything specific, but I’m happy to be corrected. 
Your post is encouraging that perhaps Roon is offering something more capable than the original Nucleus at a greatly reduced price.
Would you expect the Nucleus One to handle the specific use cases I posted earlier? (Additional info; my track count is under 28k and I only use one endpoint at a time).
You want to live in a country with a weak currency and then ask for sympathy 
Our exchange rate is reported on the hourly/daily news , that’s how interested people are .BTW South Africa
I just specified mine , the shop put it together and tested it etc all I did was install ROCK and copy content .
No different than installing any software , maybe the BIOS settings scare people but they too are straight forward
Certainly. But to spend time seriously answering hypotheticals from someone who might or might not purchase a $500 appliance? Do it once, and everyone would be wanting it, too. Not going to happen. Now, if it was a $50,000 appliance, it might be different.
Sad, but likely true. 
I guess I’m old; $500 is still a lot to me. 
Good to see this - but I suspect your 16GByte of memory might be more than is fitted to the N1. This may be what allows you to get away with a Roon Library so far in excess (150%) of the recommendations for the N1.
As mentioned, the 100,000 tracks limit is not a hard threshold. If your library is not utterly complex, the N1´s quadcore Celeron with 8 GB of RAM should also be able to handle a library of 149k tracks. It might be reacting a bit slower, and with every track added, there is a risk that it runs out of RAM.
Just looking at benchmarks without ever trying one, I would say this N100 CPU is expected to be a bit faster than the Jasper lake generation quadcore Celerons being used most probably in the Nucleus One.
It is a lot for many people, and those people should be sure before they spend their money. So, if you want to ask Roon questions about a product before you buy, I think that is sensible. Now, as others have pointed out, Roon doesn’t seem to want to discuss hardware specifics for this unit, which is their prerogative, so you may never get an official response on that.
If knowing such is a deal breaker for buying the equipment, then I would suggest waiting for real world usage results (1) and the inevitable breakdown that someone will do and post the actual internal hardware information.
As to what does 100k tracks as a device limit mean, that is a potentially longer discussion. And, one I don’t think Roon can ever really pin a good metric for as there are too many moving parts and everyone’s library and Roon usage is unique.
I would suggest that the 100k limit assumes the user is using a small number of simultaneous endpoints, very little DSP, not very many Tags and Playlists, and a well groomed and structured library. And the further your use case and library move away from that the lower the expected track count.
(1) One such account is already here from @Jamie in his blog post.
Edit. If you are already close to the limit then you might want to think about something higher as most libraries are growing. For me, the real question is not what is your current library track count, but, what will it be in the future, say four years.