Core Machine (Operating system/System info/Roon build number)
Nucleus+ running OS 1.0 (build 219) and 1.7 (build 555)
Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Apple Wifi, Netgear switches, cable modem for internet
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
dCS Debussy, Meridian Explorer, Apple TVs, Control4.
Description Of Issue
I just migrated to Nucleus+ (bought directly from you via your Amazon store) from a Mac Mini. Everything seems to work OK except that my date added data was lost or is unreadable or something.
I rely on date added to let quickly find the albums I have recently uploaded or found on Tidal or Qobuz.
So, this is a major issue for me. HELP
I also have many ripped file and an itunes library. My library is about 4300 albums. 200 Qobus, 500 Tidal, 100 other digital downloads, and 3500 or so CDs ripped through itunes. There are a few things from random other sources.
Yes, I used a fresh backup, done right before the migration. All of my itunes data and ripped albums are located on a Samsung SSD 1Tb. I attached that to the N+ after the “restore from backup.” I presume that’s what you mean by “move your tracks.”
Yes, moved your tracks means the ripped files on the external hard drive. Did you edit the old path to your attached ripped files in Settings > Storage?
Do you see all your music, ripped and streamed, when using the Nucleus as your core? I assume you’re missing play counts, date added, etc on all your music, whether it’s ripped, Tidal or Qobuz?
After you restored to the Nucleus and launched, did you see Roon importing all your albums or were they already showing?
Just USB and very recently added Tidal an Qobuz. I removed the USB drive and everything else is in the proper order. With it removed, my history file shows all my plays for the last several days. Actually, more than a month - I didn’t look further back. The USB files are listed, but shown as unavailable.
“Date added” uses the operating system’s “modification time” field for the corresponding files AFAIK. If you copy the files over without preserving that field, you get the effect you described. Learned that the hard way. It may not be possible to preserve that field when moving from macOS to Linux (which Nucleus uses) except by using a bulk file copy program with the right flags (such as “-p” for rcp). I suspect Nucleus is too locked down to allow that kind of shell-level maneuvers, unfortunately.
Thanks Fernando. I am not sure that is the problem here. I simply moved my USB SSD from the Mac Mini to the N+, no copying involved. You clearly know more about Linux than I do, but would that cause the issue I have?
When you restored the Roon database to the Nucleus, the original Storage location for your USB drive would have been wrong (since it pointed to the drive attached to the Mac). Going to Roon Settings >Storage would have shown this.
When you attached the USB drive directly to the Nucleus, you then had to be careful how you added this “new” storage. What was extremely important was that you Edit the original storage path and change the path from the Mac to the Nucleus. If you added a new Storage location, that would result in you losing your edits.
Hope that make sense. How did you set up the storage?
Hello @Craig_Martin, Greg has the proper next steps here. Also thanks for the feedback on the article! We’ve got some exciting things happening for the knowledge base in the future and will be sure to highlight sections such as this.
Let us know if editing the path one you’ve restored the original backup gets things back on the right track!
I reattached my SSD to the Mac Mini, did a new backup of the system. Installed it on the N+, then moved the SSD to the N+. Edited the storage to point to the SSD. Success!
One caution for others, if you don’t edit the exact storage location that was used by the Mac Mini for the SSD, it still fails. I had four locations being used by the Mac Mini version. If you don’t pick the exact same location to edit, it still treats the albums as new. I had used several locations over the years and hadn’t removed them when I stopped using them. As a result, I picked the wrong storage location to edit. That doesn’t work. The next try I fixed that and it worked!