Ripping CDs from NAIM Uniti Star to Nucleus One SSD

[Geoff_Bishop]

Just acquired a Nucleus One (now fitted with internal SSD) and a NAIM Uniti Atom amp/streamer. Both use wired connection to my home network. I copied all my music files from PC to Nucleus SSD with no problem using the drag and drop method. I can play these files in Roon via the Uniti Star. However when I tried ripping a CD with the Uniti Star onto the Nucleus SSD, the NAIM app tells me I need to “Configure Music Store” or “View Local Drives” but neither of these can see my Roon Nucleus. I tried making a USB connection between the two units but his didn’t change anything. I guess I need to add a Network Share, but from past experience, I’ve always had difficulty in finding an acceptable wording to define the location. As the Unit Star is classed as Roon Ready it should be possible to set this up. Any help appreciated. Thanks, Geoff

[ged_hickman1]

You can only rip from a Star to a locally attached usb drive.
Uniti star storage - Streaming Audio - Naim Audio - Community Uniti star storage - Streaming Audio - Naim Audio - Community

[Suedkiez (Just a fellow user like you)]

@Geoff_Bishop

As the Unit Star is classed as Roon Ready it should be possible to set this up

Roon Ready means that it works as a networked output for Roon with certain quality guarantees, nothing else.

Roon Ready

[Mike_O_Neill]

@echolane did something similar I recall maybe she can help ? I know she cracked it !!

see

Naim Uniti Core with Roon Server on SSD USB drive (was on QNAP)

As the owner of a Naim Uniti Core I will chime in. I started with this product, completely naive to streaming, and it served me about six months when I realized how simplistic it was. It could only rip and edit metadata and send music to my DAC from the files it maintained. I wanted Roon, so I bought a Roon Nucleus and an Audio Alchemy DMP 1 Media server and sent my meticulously edited music files through Roon. It was a total disaster. I asked Roon to use my metadata and Roon couldn’t read …

If I recall the Naim rips are not “readable” to the outside world its meant for s in Naim’s ecosystem only. Incidentally Nucleus rips are the same.

So you may be better sticking with using your PC and a ripping program. dbPowerAmp seems the favourite choice

[Suedkiez (Just a fellow user like you)]

@Mike_O_Neill

If I recall the Naim rips are not “readable” to the outside world its meant for s in Naim’s ecosystem only.

Not quite. I explained this in detail in the thread you linked. It’s important to set the Star to rip to FLAC, then you get proper file names and metadata.

But you still have to rip to a disk that’s local to the Star, then copy the files off it in some way.

@Geoff_Bishop wants the Star to rip directly to a remote location like the Nucleus SSD, and that’s not possible anyway.

However, when using a computer to copy off the Star and onto the Nucleus, it would be possible to automate the copying

[Echolane (Echolane, Roon Lifer)]

@echolane did something similar I recall maybe she can help ? I know she cracked it !!

In truth, I’m no help. I can just complain haha.
it greatly annoyed me when I discovered the stumbling block to moving WAV files ripped by Naim are not portable. Along came SongKong to the rescue. I hate to admit it, but SongKong just doesn’t match up to the way I think, so In fact I’m still a victim of that incompatibility. Had I known not to rip in WAV I would have ripped in FLAC, which seems to be universally portable. This issue still rankles, especially as I just read that Nucleus rips apparently cause the same sort of incompatibility.

I haven’t done it yet, but I intend to switch to using dbpoweramp. I don’t want to have to, but I see no alternative except switching to yet another streaming platform, like Innuos or Aurender, etc, which simply isn’t practical for me. Anyway, and almost certainly, their metadata edits will not be transferable either!

Actually Roon locks us in just as tightly as Naim does because our metadata edits do not update our music files. Therefore I have to assume our Roon edited metadata is not portable either. Personally, if I had the option, I would want my files updated with my metadata edits.

[Mike_O_Neill]

You never complain

I always edit outside of Roon , when I am happy I transfer to the NUC SSD

That way the files stay portable across most audio players and no stuck on Roon

I use JRiver the editting is superb,and I have it any way

[Geoff_Coupe]

@Echolane

Actually Roon locks us in just as tightly as Naim does because our metadata edits do not update our music files. Therefore I have to assume our Roon edited metadata is not portable either.

Hi @Echolane - this is actually not true. Roon offers the Export function. If you ever decide to leave Roon, then you can simply export all your albums to a location where a copy of all your albums will be made. The tracks will have the basic metadata written into them from the Roon database (if they did not already have them in place).

If you have ripped CDs using a CD drive attached to a ROCK NUC, then indeed in the Roon storage location you end up having folders with a date, and track names that are generic. However, the metadata is used in the export process to give the exported folders names following the Artist/Album naming convention, and track names are renamed from “track nn” to the title held in the track title metadata.

So you end up with a file and folder structure that is the same as the default naming convention used by dBpoweramp.

Export

And here’s an example of it in action:

What do you use to rip?

Here’s an example… First, what I see in Roon’s InternalStorage folder: [Roon%201088] I chose 4 of these albums and exported them to a folder on my desktop PC: [Roon%201089] Now Artist folders have been created, and within them, folders for the albums (bearing the Album Title). And further down, in an album folder, the tracks have been given the track title names: [Roon%201090] I sometimes think that discussions around here are like listening to Greek Philosophers arguing about the numbe…

[Suedkiez (Just a fellow user like you)]

Plus, Naim doesn’t lock in either. They just have a stupid default setting (and even stupider explanation), but users can think for a second and change it. (And do a quick test with one CD before ripping 10000 CDs)

[Echolane (Echolane, Roon Lifer)]

@Geoff_Coupe

@Echolane

Actually Roon locks us in just as tightly as Naim does because our metadata edits do not update our music files. Therefore I have to assume our Roon edited metadata is not portable either.

Hi @Echolane - this is actually not true. Roon offers the Export function. If you ever decide to leave Roon, then you can simply export all your albums to a location where a copy of all your albums will be made. The tracks will have the basic metadata written into them from the Roon database (if they did not already have them in place).

I’m unclear on this explanation. For example, I have a personal editing convention I follow on the Title field that helps me organize and find my albums. I would most certainly want my title edits exported. From your answer I wonder whether my title edits are exported, instead is the metadataj that Roon puts in the title exported?

[Geoff_Coupe]

Can you try a test to see what Roon actually does? Pick a few albums that you have edited in Roon and then use Export to copy them to a location that is not within your current Roon Watched folder(s). Then use SongKong on the copied files to see what Roon has put into the metadata.