Ripped CDs Bit Recognized

Hello. I recently had an issue where the Roon and Windows app would not find the core on my Intel NUC ROCK. I found the solution on here, but now I can’t access music that was ripped.

In windows explorer, I can navigate to the ripped CDs folder and view the new files. However, for some reason, Room doesn’t pick it up. There is one CD that Roon did see back when I ripped it a few months ago. Now it can’t. Nor can it see the CD that I just ripped.

So I have two questions. How can I ensure that Room sees the music that I rip from a CD, going forward? Also, although when working properly Roon will display the proper information, in windows it’s just a a bunch of letters instead of the name of the albums. Is there software available to have the music tagged/labeled for the purposes of viewing in other Windows apps? Thanks, y’all.

What exactly was that issue?

Can it not see any local music or are only some specific albums affected?

Are you using a CD drive attached to the ROCK and Roon’s ripper?

Not sure what the cause was for not being able to see the core. I had to rename the server folder and then restart Roon.

Looking back, I’m not sure. I was only interested in the ripped files, at the time. I just checked and saw that I specified the drives, but didn’t select any subfolders. I left it at “Roon Storage”, thinking it would scan all folders beneath it, which included a “Music” folder and a “Ripped CDs” folder. I added each one, separately, and now Roon can see the files. Although, the recently ripped CD, a Shelia E CD, is still unnamed.

Yes, I am using a CD drive connected to the NUC. Until recently, I had ripped just one CD, but that ripped without a hitch. It is still in unnamed in windows explorer, but Roon applied metadata to the files.

I though it may have something to do with the new problem, but may not

It does for the ROCK’s internal storage. This is all I have, and it’s what ROCK sets up automatically:

And this are the folders on my internal storage. They are all found and included:

Well, as long as it works :slight_smile:

Maybe it’s just badly identified. Can you see it in Home > Recent Activity > Added?

The ROCK ripper is only intended for using the files within Roon. It does not create folders with artist and album names or files with track names. Instead, it uses guaranteed-unique names that have no meaning for humans, just for the computer. This is much more reliable for an appliance like ROCK. The downside is that they are not very useful outside of Roon.

From the Roon OS CD ROM documentation:

and

If you need the files outside of Roon, use a standalone ripper like dBPoweramp.

But now that you have them like that, your could theoretically have them identified, renamed, and tagged by some program like mp3tag, SongKong, or similar. However, I guess this means that Roon would re-identify them and I am not sure if this creates a mess and how big it would be.

1 Like

Roons ripper doesn’t name anything, it just matches the cd from its metadata to its sources and links in Roon only. The tracks are unnamed it’s basic and pretty pointless for use outside of Roon something they don’t seem to understand and never have changed a thing about its behaviours. You have to name them in tagging software to make them usable outside of Roon and move them into the main storage. If you don’t lose your database you lose your way of identifying what they are.

AND lose your database?

They do understand it. It’s the best way to do it for an appliance. Users should just follow the advice

Damned auto correct keeps doing this. Twice in a week.

1 Like

It’s not best at all when is it could to have hundreds or thousands of files named just track 1. Naming the files sensibly is not bad practice not one appliance ripper does what Rock does it’s just daft to have a whole lot of files with no album name or track titles. The ripper software they use is more than capable of doing this. It’s just bad in all ways.

It’s maybe not best but it is guaranteed that everything is unique because the tracks are in guaranteed-unique albums folders. Best would be to name each track with a random GUID.

The problem starts when people don’t read the instructions and want wo use the ripped files outside of ROCK

I don’t understand why anyone would use it at all. A free ripper will rip and be useable outside.

Well not everyone is guaranteed to even have a PC, and more people are not comfortable using them. It seems easy for you or me, but setting up and correctly configuring dbPoweramp, and then using it correctly in the more complex cases isn’t obvious to everyone.

Some people want the least hassle and just want to feed CDs into the autoripper. Of course, then it turns out that this isn’t hassle-free at all if there are identification issues (such as with multi CDs) but that’s not obvious from the start, either.

2 Likes

Mind you unless you only have a few to rip, looking at the posts people soon find the rock ripper shortcomings it seems :blush:

Which most people want to do. It’s just a feature not fleshed out in any way. And it doesn’t even do album folders you only get this nonsensical structure. And Roon won’t read these if you have to reset your database due to corruption which we all know it’s very capable of doing.

And as we know, only a small percentage of the Roon users visit the forum.

I don’t know. We only hear of those that do and chose the wrong tool for it.

It’s only nonsensical if you try to use it for something you shouldn’t, though

Is that so? No idea. I would have thought it would re-identify them as well or as badly as it did when ripping. Maybe not.

In summary, it’s not a very well fleshed out feature, but it has its place. People just shouldn’t use is it for something else, but that’s not completely obvious

They have no metadata nothing so without any naming it’s got zero chance of identifying them. Hence why it’s a poor man’s choice. It only identifies them at rip. When they announced it I was very happy then used it for a while and found it to be just a waste of my time and switched back to ripping on my pc where it’s just one step and copy files.

Oh OK, that sucks. It should have some way to identify and if it’s only an embedded ID that Roon understands.

I’ve seen enough of it that I wouldn’t recommend it to anyone if it can be avoided, that’s for sure