If you want nitpicky feedback, I think you’re missing a bold on the core (2nd para) on the how it works page:
"Roon consists of a single core and as many controls and outputs as you need. "
I’ve got a suggestion for you for the website - which would be to make it even clearer what ‘RoonReady’ devices are, and what ones are available, and what are undergoing certification (if possible). Also expand on tested devices available.
I say this based on offering advice about Roon (in general, but particularly on ‘endpoints’) on other forums, where there tends to be a lot of confusion. OK, it doesn’t help that you’re on the cusp of RoonBridge and Linux, but still……
I think for those of us that follow Roon’s development it’s a lot clearer, but coming to Roon ‘fresh’ its not quite as obvious. I tried to approach your website in the eyes of a new user today, and have to say it wasn’t clear to me what I should be looking for if I want a RoonReady device ‘endpoint’ or ‘server’. Of the brands you have listed, a lot have a very subtle asterisk for ‘undergoing certification’, but there’s no product details - only a brand, and it takes you to their main website (same for the Roon Tested). For the brands that have certified products, they click through to the product details, but this might not have been obvious if you clicked on uncertified brands first. I then found your product matrix hidden in the knowledge base, but I dare say it might be too hidden.
It might help to also explain the whole ‘squeezebox’ support situation, and how to get it working on various devices a bit more too. There appears to be lots of confusion about people ‘running Roon’ on Pi’s, squeezeboxes, etc.
And the situation with RoonServer devices could do with some more info. Yes, I know there aren’t any, but maybe this could do with some more info if possible, as people often don’t want a computer in their audio chain and I think if they knew a product was even on the distant horizon that could replace it, it would help.
The majority of the Roon ecosystem seems to be much better understood (and definitely helped by the new website), but the ‘endpoint’ / hardware ‘server’ aspect seems to cause a lot of confusion, and some of that is no doubt to the fact that things have evolved quite a bit and are on the cusp of change, but there’s a lot of historic info out there. A general comment I’ve heard a few times is that the forums are good, but there’s such a bewildering array of topics and information spanning from launch to date, that it makes it hard to get info and figure things out.
Again, this isn’t feedback from me per-se, it’s compiled after interacting with new (possible future) Roon users elsewhere….
2 Likes
Great feedback from Steve.
And to support his point, I’d like to point your attention to this interesting dialogue. Continuing the discussion from Roon and the Auralic Aries:
“Thank you Steve. It’s an easy answer, I understand, but I’m a new user of Roon…
I read that page (and some others) before installing the software and it says: “A Roon system starts with a core” and “The core can be your Mac or Windows PC, or a server from one of our hardware partners.”
Being Auralic one of the partners, I thought that the Aries could be a core so that I needed only Roon on the ipad (control apps) to send the music to the dac.
In another way, is the Aries a core and I’ve missed something in the Roon’s setting on the ipad or is the Aries an output and I need also a pc – the core – with Roon?”
This was a case where a newbie reasonably concluded that his Aurelic Aries might just be the “server” that ran a core for him. After all, it is “RoonReady”.
I’d have never caught this myself. Too close to the subject matter. Might be beneficial to have some truly fresh eyes look at the knowledge base, and when they get confused or aren’t clear, find out why.
Thanks Steve - just trying to help….
I dare say for a lot of prospective new users, the KB would be a step too far anyway - personally I think it needs to be clear and as simple as possible on the main website. If someone does venture into the KB however (via ‘support’ dropdown) it doesn’t say you’re in a knowledge base, and there’s no obvious mention of things like RoonReady or hardware devices, ‘endpoints’ or ‘servers’ or even references to core, output and control introduced so nicely on the main website… Unless I’m missing something.
I’ve personally puzzled over that idea myself. And I’m not sure I agree. Though I’m not sure I disagree either. Fact is, I’m just not sure. Here’s why…
If my wife had to install Roon - much less figure out what components she needed - using the documentation that’s out there now, it would NEVER happen. That’s the bad news. The good news is that she’d never try. She does not have a digital library that she manages herself. It’s beyond her knowledge set. So she gets yours truly to worry about that for her. In other words, people without a core set of digital, PC/Mac skills are not the target audience. They can’t manage a digital library. How could they be expected to set up Roon?
That’s why I’m not sure. I suspect that having the knowledge to manage a digital library is the filter Roon needs. It keeps the people that can’t understand it from even being interested. I think.
Certainly happy to shown that I’m not thinking clearly on this. As I said, I’m not sure…
1 Like
The idea is that clicking on each partner would bring up a partner page, which has more information about the partner, including which products we have tested and which are Roon Ready.
We just haven’t deployed those pages yet 