The whole point is that Roon doesn’t need to write metadata to the track files, rename them or rename folders - all the information that Roon needs is held in the Roon database.
However, Export will do exactly what dbPoweramp does…
Would love to see Discogs used as a metadata source
2 Likes
Still curious to hear from Nucleus users - have you hit the limits of the already wobbly forum based support system? What’s your experience? Have you have to send back your units? And most importantly:
-
Has it been bad enough to make you go (back?) to setting up your own devices under general purpose operating systems so you can service yourself?
-
Or maybe the other way around! Are you so happy that you will never bothering tinkering with general purpose OS for your Roon rig again - appliance all the way for you.
Many angles to consider. The currently supported NUCs are still fairly capable, for example. If you are a ROCK user with one of those, you should be fine for the moment. Yet, if that was me, I would worry that once those become obsolete no alternative would be offered - buy Nucleus or setup your own.
I am not saying that Roon might do that. I think that is improbable. But it is not impossible. So I would worry.
Heck I AM WORRIED RIGHT NOW! 
What if Roon decides to go to a model of ONLY NUCLEUS + Roon Ready COMMERCIAL devices only? I shudder to think…
I bought a Roon Nucleus in late 2019 (US$1119) and have no regrets. I did have to replace the M.2 drive once but bought it from Amazon for $26 and replaced it myself. I also run Roon server on a Mac Mini and Dell laptop.
I’m not sure what you are trying to stir up here or why.
4 Likes
I guess that would be me. I pieced together a NUC8I7BEH/Rock in 2019 and have not experience any issues related to the music server or the software that affects the music playback, going on 6 years now. It runs 24/7 and starts playing music anytime I want.
I recently needed to upgrade my laptop daily driver and went reasonably high end so I could use it as my backup server while working on the NUC replacement. I know the NUC won’t last forever.
1 Like
It’s all there! “Just curious” - one has the right to think things, right?
But from your post I learned something significant - the Nucleus is repairable. THAT IS GREAT. Makes me think of mostly Apple, how their devices are becoming less and less repairable.
1 Like
I assumed that would be the case for lots of people - there are a few sayings which they all could interpreted to mean “your opinion depends on your experience” and there is wisdom there! And that was the intention there - it is interesting how depending on your experience you can be driven to the lowest or the highest complexity thing depending on your impression/opinion of what needs to be done!
From there, I thought of the Nucleus - one thing is to setup your own NUC the other thing is the premium implied with the Nucleus and what it means in relation to support. Because well, my impression and experience colours my thinking.
I was thinking the same.
2 Likes
Why?
Roon is a commercial product which will go the path the shareholders choose, like anything else.
If it turns into something you don’t like, use something else.
Have choices.
2 Likes
At one time, Roon Labs were certainly looking at including Discogs as a metadata source, but I don’t think anything came of it. I think that was because the metadata quality varied too much, but I can’t find the forum post where this was stated. Here’s the post (from 2018) when it was said that they were looking at Discogs:
You seem to be implying that those of us with IT experience will gravitate to using a system built on a general purpose OS, while those with no IT experience will want an appliance.
I may be an outlier here, but I think I can claim to be fairly experienced in IT, and I went from using Windows to using RoonOS precisely because it gave me a music appliance.
5 Likes
I’m retired from IT and want to stay that way with kit at home. Putting together PI endpoints for RoPieee is fine, as is ROCK on a NUC but I wouldn’t want to run a windows system I wanted to rely on. Too many updates and reboots for comfort.
1 Like
There’s this, but I vaguely recall reading something about the API, too.
No, not training or education or familiarity I mean experience with the product, that is if you ROCK never had issues, you will probably will stay with it.
In my case, it went like this: not being able to diagnose and/or fix the issue meant a reinstall. Now, I thought, “well if I am gonna reinstall, better do something I can myself maintain”.
Otherwise, like you, would have stayed with it. And so I thought, maybe that is a good conversation.
1 Like
Nah! No need to think that hard.
It’s all there! “Just curious” - one has the right to think things, right?
hehe! you just gave me reason to worry. That would take time and work I don’t want to put in.
You probably ought to stick to physical media as you have full control over it and it requires little effort.
Anything else that relies on 3rd party commercial software and needs maintenance of a server of some description needs a degree of time and effort.
The measure of good applications and IT is that it is used without having to think about the software etc.
That, is the user is focused on the task in hand, e.g., writing a jounal, updating a finance record, listening to music etc.
So, I’d say, simples is best, and therefore, Roon as an appliance is great. I used ROCK for years, and only changed this when rationalising my server(s).
In my experience, most IT projects (typically) fail to deliver what’s needed because of too many choices and inevitably a focus on the wrong requirements.
1 Like
Of course, that is VERY obvious!
And I am a physical media person. But as with any technology usage, inertia is comfortable… I settled on Roon and while perfectly capable of, well very capable tech-ing… having to redo with Volumio, Audirvana or similar… well, like it’s been said in the thread… once is working…
ALTHOUGH
TBF, when I think about it, moving away from Ropieee and ROCK did take some work… yet I stayed with Roon - I do like the platform, in spite of what, well, what I don’t like about or wish it could be done differently. And I have been very clear ! Support away from this forum and into a real support platform, Linux Client, and other stuff here and there…
That is all 100% true. What I am curious about is what happens when things break.
Like I mentioned in other posts, when faced with a broken ROCK and the fact that only a reinstall would do, I decided to fall back to something I could service myself. What if after a reinstall, I was still unable to mount my drive in the reinstalled unit? Reformat the drive and risk data loss with the steps required to do this?
I imagine that would be the case for the Nucleus, for example… if a reboot and/or reinstall won’t fix issues, what’s next for the user? Send back the unit?
I really was looking for some insider info! maybe there IS a service backdoor, that it is just not documented. Heck, given the target audience of the Nucleus maybe even a reinstall would be too onerous… not in every case of course, but that is a real possibility. How are those people helped?
All possibilities, all valid - guess the Roon users run the gamut. Was just curious about the general makeup. Again, like I mentioned, I am a techie, and just like the poster above, in spite of that, I was happy running ROCK until it just did not do it FOR ME due to my experience with it. Hence the move to general OS.
As usual, of course, IMHO, YMMV.