...I thought the whole point of Roon was that it “just works” with all devices and all services without the end user having to dick around?
Lots of folk don’t get ROON or feel it’s worth the dosh, so no you’re not alone.Am I the only one who just does not get Roon, I really can't see the point and cost. I had the free trial and decided it's pointless and expensive. Is there anyone else out there?
OK, you must be correct, and all the other users who have this issue also stupid....
To quote another poster on roons forum for some balance. https://community.roonlabs.com/t/roon-1-7-build-667-no-automatic-file-rescan-anymore/124916/31
fifolifo
4h
I don’t know what’s worse. That this particular problem with build 667, released 35 days ago, hasn’t been fixed yet or that despite everyone who runs Roon on a NAS with a root music folder experiencing the same exact issue that support is still asking for screenshots like it’s some type of mystifying inconsistent phenomenon.
Perhaps it’s the irony that the whole point behind this maintenance release seems tailor made to address a problem such as this one as the bug and the affected group is so readily apparent.
“…they allow for more flexibility in the future for how we distribute releases to users, so we can test bug fixes with affected users before they go live to the wider Roon community.”
Personally, the thing that annoys me the most is that I’m very careful with software updates and read every release note and the release notes for build 667 seemed to imply that the affected changes were with how it interacted with Roon’s end and not how it worked locally.
“We have a maintenance release going live, with some infrastructure changes related to our updating system.
The changes in Build 667 should be largely invisible…”
If you had added some additional information in the release notes about changes to how local file directories were handled or released it as version 1.8, I would have never updated and waited for the next release. And I would be enjoying and listening to music right now instead of writing my first rant post since running Roon trouble free for nearly three years.
Am I the only one who just does not get Roon, I really can't see the point and cost. I had the free trial and decided it's pointless and expensive. Is there anyone else out there?
“Regarding the latest important changes to how Roon interacts with Roon Ready devices, thanks to the Aqua Acoustic Quality proprietary code (firmware) developed in-house for the LinQ, Cristian and his team were able to implement a custom Roon Endpoint that does not require the certification program.”
https://www.monoandstereo.com/2020/09/aqua-acoustic-quality-and-roon.html
Why would Aqua not want to adhere to the official Roon certification program? Apparently Roon doesn’t charge manufacturers and their customers would surely prefer if their devices were officially certified?
It should “just work” on anything they advertise it as working on. A Nucleus, a Roon Rock, a suitably specced NAS or Windows device or Apple device, whatever. It’s not good enough to tell people to “just get a Rock” when they encounter problems on other machines, nor for that matter is it good enough to suggest that classical music is effectively unsupported whenever a user has a problem with a search.It does "just work" on a NUC Rock.
Not so, all other apps work; PLEX, Asset UPNP etc etc. Just roon doesn't. IF QNAP had such an issue they would roll-out an updated within 24 hours.From what I understand, the majority of the Qnap issues began after a software update issued by Qnap. Not the 1.7(667) release of the Roon software.
Am I the only one who just does not get Roon, I really can't see the point and cost. I had the free trial and decided it's pointless and expensive. Is there anyone else out there?