From below, seems to be some Finder metadata. MacOS certainly does seem very happy to start tossing at least .DS_Store folders every time I would let some Mac connect to any of my network drives…
It should do. But as people suggest above, with the music library being large, but rather slowly changing, when you rip or download something new for it, you might just copy it to both Nucleus and your backup location as well.
Probably more of the way of MacOS moving that data to a mounted drive using a different file systen, so that tags are preserved. Linux would have no idea what to do with them, and Roon would ignore them.
The specifics of the Nucleus migration system are - as most posters here have been saying - pretty simple.
In some respects that may be the case when you’ve already done it: I think I’d find it less intimidating now if I had to do it all again. But I would respectfully suggest that Roon’s documentation could be clearer… sometimes there are two pages for the same workflow, which differ and leave off certain crucial aspects - that you have to relinquish your ‘old’ server login in favour of that of Nucleus’s, for instance.
And pages like This one, for example, are not 100% clear in explaining what happens when. And why.
The phrase ‘Ensure the backup you created above is accessible to Nucleus’, I’d respectfully suggest is unclear. In fact the USB backup of my Roon database became visible through the Roon ‘browser’. And worked
Similarly the instruction there to ‘…stop the Roon Server Software…’ under ‘Internal Storage > ii’ doesn’t make sense if the server is no longer running - in my (most?) case(s) on my iMac.
I confess, I’m maybe atypically ‘cautious’ when it comes to experimenting. But having laid out for Nucleus and Roon having become the very centre of my music-playing world, I really haven’t wanted to take any missteps. Hence the length of this thread, for which I apologize again!
But I appear to have got all my files in and imported.
Are these known bugs:
About a dozen Album Covers were missing and had to be re-added.
And I’d say roughly 25% of my tags did not make it over to Nucleus.
?
Still - compared with early November when I started this process - I know I’ve made good progress.
I also know I couldn’t have done it without the help of everyone here.
Accessible in any way that the Nucleus has for accessing things. Could be a USB disk or a network share, I don’t think there is anything else. If the backup is accessible in such a way, it can be restored during setup, but otherwise not.
It seems obvious to me but I understand that it won’t be obvious for everyone and maybe it would help to have a more detailed explanation right there.
(Though generally I don’t have a solution for a problem that has haunted me for decades: It’s always either „not enough explanations, I didn’t understand“ or „too long to read, make it shorter“ )
Until now, I’ve never had to use Samba or shares. Nor am I (yet) familiar enough with Roon OS to have been able to see immediately how ‘accessible’ translates itself into a user interface like the Mac’s Finder or the Roon browser.
Having done all of this, it now seems strange that I had such trouble knowing exactly what to do.
Hindsight.
And of course all your help (and that of Boris and others)!
Bearing in mind the ‘journey’ which I’ve taken in this thread (a very successful one!), and that everyone’s gaps between what they know, what they don’t know and what they need to know are different, how about - as Mario says - something like:
'…“is accessible to Nucleus”. That is, is visible:
either in the Finder - probably on a USB device such as a thumb drive,
or by navigating to it via Roon’s file browser’
?
BTW none of this is a criticism from me. I love Roon, am a lifetime subscriber and would be happy to feel I might be contributing to a minute improvement in some way, if possible.
'…“is accessible to Nucleus”. That is, is visible in Roon’s file browser’
The reason being that “Finder” is a Mac term, that is not applicable to the Nucleus.
One could very well have a Roon Backup held somewhere that can be accessed via a Mac’s Finder, but that doesn’t mean that it is equally accessible to a Nucleus, unless that Backup sits in a folder that has been shared by the Mac over the network and the Nucleus file browser has been used to set up access to the shared folder…
3 Likes
Bill_Janssen
(Wigwam wool socks now on asymmetrical isolation feet!)
337
Maybe it’s the transition that’s the problem. You had a Roon Server on a Mac, complete with backups and music, and you suddenly transitioned to a Linux system (the Nucleus). What’s more, the Nucleus is designed to be a utility box. What’s more, the set of terms (and file systems) used by Linux are different from the set used by macOS. What’s more, both Apple and Roon cloak the actual terms and processes used generically by computer practitioners in their own “customer-friendly” terminology (Finder! Pah!). What’s more, you’re using explicitly Apple-centric software (CCC) to operate on a Linux machine. Or SMB, a Windows file protocol native to neither macOS or Linux.
I continue to fail to understand the lure of a Nucleus. They seem to be expensive middle-of-the-road Linux boxes. For someone who’s familiar with macOS, wouldn’t a better idea be to simply buy a new Mac Mini and use that as the dedicated Roon Server machine?
I would agree that this is somewhat unclear. To a computer person this is likely to mean “put the backup on a file share accessible from Nucleus.” To a lay person, as we see, it can mean just about anything. Or nothing. Wouldn’t it be better to state explicitly that the backup should be “put in a file share access… or saved on a USB drive formatted using ”?
Chicken and egg And average person setting up Nucleus needs to know first what would be visible in Roon’s browser. And of course if you back up to a USB drive (which would work) it will not be visible until you actually plug it into Nucleus…
To be fair, this has been more or less an “industry standard” thing supported by both MacOS and Linux for ages.
Completely agree there. Although some utility PC in a good enough quiet case is probably a better vsalue and more expandable.
(I understand your scepticism about the Nucleus. For me - if you can believe it - the incentive is… ahem, simplicity and that it’s ‘built-to-fit’; and - if you can even believe this - the chance to learn about new devices, systems and ways of doing things.)
Also enjoying the wonderful spirit (not to mention expertise) of this forum.
It’s a beautifull box but remember that it’s just an Intel NUC (and not the newest….) PC inside…
I bought an i7 NUC and it took me 10minutes to get up and running. Has never ever had any issues. Look at YouTube and you will see that it’s just an off the shelf NUC PC.
If money is not a problem the Nucleus is a nice design
Now that I’ve got everything in place I am happy. I still think I made the right choice.
Support and the absence of DIY are two of the main reasons why I decided on Nucleus. And the fact that I thought I deserved a ‘rest’ now.
I’ve done a lot of DIY: built valve and transistor radios with breadboards and something called veroboard in the 60s; indulged in major tinkering with the Acorn sideways ram and Eproms in the 80s. And much more.
Other posters’ comments (e.g. those on the presence of two USB ports and HDMI etc) have also made me realize that there is an element of off-the-shelf. I hope that the volume in which it is thus being produced means that the Nucleus is likely to be around for some time.
But all points of view add to the picture. Thanks!
Sometimes lowest price is not the main consideration. I wanted a Nucleus, so that’s what I bought. I got it directly from Roon for $1119. I just liked the look of it and did not want to fool with DIY. I did have to replace the m.2 drive after 3 years, but I did that myself in less than 1 hour for $26 plus tax and freight.
.
)