Another Roon Heavy Handed Policy

I guess another possibility is you have some sort of virus or trojan that is eating up resources. That could explain why it is on both your home and work systems, since there's a good chance they've had some way to communicate with each other (via the network, USB sticks, etc.). It could also explain why the system seems to be overloaded even if you have a super small set of music loaded into Roon, or why the issue seems to be intermittent instead of constant. :(

I was actually thinking this also. People think Macs never get viruses but in actuality they actually get more because of the sense of invulnerability that Apple promotes and many times leaves system exposed. It sure sounds like something going on.... Roon is not a resource hog, at all. It uses a minute amount of resources on my system. Honestly HQPlayer uses a ton more but even with both running the resources are not being pushed.
 
We are running a NAS (Synology 1812+). The laptop has the latest version of Mac OS.

My hunch is that Roon constantly wants to update the library and our library is large. My guess is that it’s getting stuck somewhere. But that being said, my home setup is completely different and still has the same issues. It’s why I want to try something a little more powerful.


Sent from my iPhone using Tapatalk Pro

A couple of suggestions:
1. Make sure that your NAS drive (shares) is mounted to the Mac.
2. Disable the sleep mode of your NAS
 
Jack is correct. We use Roon a lot in the store because many of our products require it. We also help customers with Roon Nucleus’ and the like.


However, for us in the store and me at home (I have Roon running for my NAIM music server which I use in the family room) and it’s buggy in both places, buggy as hell. I’ve been taking videos and will soon start a channel and post them. It’s constantly crashing and it hangs ALL. THE. TIME.

I had the same issue too. It was hanging all the time. My problem was in the router, or actually the combination of my router and accesspoint. I gave them both the same IP range: 192.168.178.2. All my stuff worked, except roon. It sometimes worked for a few seconds and then stops playing. It was luck to get a minute of music out of Roon. Then I was thinking: maybe those 2 routers are in conflict and changed one of them to 192.168.178.3. And to my surprise, all my stuff kept going and Roon was fixed. Just Right in time, the tryout period was almost over and took the subscription.
 
I had the same issue too. It was hanging all the time. My problem was in the router, or actually the combination of my router and accesspoint. I gave them both the same IP range: 192.168.178.2. All my stuff worked, except roon. It sometimes worked for a few seconds and then stops playing. It was luck to get a minute of music out of Roon. Then I was thinking: maybe those 2 routers are in conflict and changed one of them to 192.168.178.3. And to my surprise, all my stuff kept going and Roon was fixed. Just Right in time, the tryout period was almost over and took the subscription.

Makes sense. You can't use the same IP on multiple devices.
 
I had the same issue too. It was hanging all the time. My problem was in the router, or actually the combination of my router and accesspoint. I gave them both the same IP range: 192.168.178.2. All my stuff worked, except roon. It sometimes worked for a few seconds and then stops playing. It was luck to get a minute of music out of Roon. Then I was thinking: maybe those 2 routers are in conflict and changed one of them to 192.168.178.3. And to my surprise, all my stuff kept going and Roon was fixed. Just Right in time, the tryout period was almost over and took the subscription.

Your comment reminds me of one very important thing to check:
make sure that your NAS is assigned a static IP address in your network!

If the NAS uses a dynamic IP address, when the IP changes Roon cannot find the NAS drive (or the music stored in it) and will stop playing.
 
It's stated here that the NAD M33 is yet to be certified but the M32 already has been - for years.

The basic M32 (or M12 preamp for that matter) has no streaming ability unless the BluOS module is added. So, presumably it's the module that is Roon Ready and certified. What's to stop the owner of an M33 (when they become available and assuming no certification) from adding a BluOS module to his M33? The device would have 2 streamer modules (one built-in) but that's surely no problem as they'd each be identified by the software and Roon could respond to the BluOS module and ignore the built-in streamer.

I ask because I'm planning to get the M33 but already have the BluOS module that I could remove from my M32 / M12. Peter
 
I was actually thinking this also. People think Macs never get viruses but in actuality they actually get more because of the sense of invulnerability that Apple promotes and many times leaves system exposed. It sure sounds like something going on.... Roon is not a resource hog, at all. It uses a minute amount of resources on my system. Honestly HQPlayer uses a ton more but even with both running the resources are not being pushed.

I've been using a headless Mac Mini for Roon Core since Q4, 2016 and for the most part, it's been flawless. I've got 3495 albums and 43,204 tracks. I think I've had that bouncing Roon icon "failure to launch" upon startup failure mode maybe 3 times, when you need to go into the Terminal mode and reboot from there. Using a quad-core Ivy Bridge i7 with Mac OS Mojave and 16 GB RAM. All my music is on an external 4TB Thunderbolt LaCie Rugged Drive. Other than that, it's been flawless. Mac Mini is powered by a Shunyata Venom V14D Digital PC and the Cryoparts power strip its plugged into is powered by a Shunyata Venom NR-V12 PC. I'm connecting to my downstream network bridge via fiber.
 
I've been using a headless Mac Mini for Roon Core since Q4, 2016 and for the most part, it's been flawless. I've got 3495 albums and 43,204 tracks. I think I've had that bouncing Roon icon "failure to launch" upon startup failure mode maybe 3 times, when you need to go into the Terminal mode and reboot from there. Using a quad-core Ivy Bridge i7 with Mac OS Mojave and 16 GB RAM. All my music is on an external 4TB Thunderbolt LaCie Rugged Drive. Other than that, it's been flawless. Mac Mini is powered by a Shunyata Venom V14D Digital PC and the Cryoparts power strip its plugged into is powered by a Shunyata Venom NR-V12 PC. I'm connecting to my downstream network bridge via fiber.

Yup, even though I am not a fan I do believe that Apple is not the issue either. I will say I have heard more people having issues when using Apple's but I do not necessarily blame that on Apple. I do believe that there are more issues simply because of users who are drawn towards Mac, with exceptions of course, tend to be less comfortable with computers. However I do blame Apple for actively minimizing the threats towards their computers leading to a false sense of security. Apples are fully capable of running Roon, issue free, and many Apple users have Roon working flawlessly for them.

With all that said using an Apple does not explain Mike's issues, as many other Apple users do not have issues.
 
Your comment reminds me of one very important thing to check:
make sure that your NAS is assigned a static IP address in your network!

If the NAS uses a dynamic IP address, when the IP changes Roon cannot find the NAS drive (or the music stored in it) and will stop playing.

You really make a good point here. Since a few years I invested time in getting my home network all static, and it was far more reliable. Every device that you use has its own mac address.My network is organized that every single mac address gets its own IP. For instance: my pc gets 192.168,178,216 my smartphone: 192.168,178,228, my printer: 192.168.189.221

Every single device has its own mac address and every single mac address I assigned manually its own IP. Thats about routers:

One more thing: Yesterday I changed my accesspoint behind the TV,
I went to an audio specialist and wanted to listen to the silent angel bonn n8. Within a few minutes I decided to buy one. The shop owner was surprised, he never ever had a listener who liked to compare this silent angel bonn, while he sold 500 of these things! After listening I was convinced and got one. At home I found out what a switch is: nothing to do with IPs etcetera, it only works for Roon,

So my conclusion is this: a router with a static IP gives a stable Roon connection. put a switch after it, one made for audio of course, and everything works stable, with an amazing sound due to the audio switch.
 
It's stated here that the NAD M33 is yet to be certified but the M32 already has been - for years.

The basic M32 (or M12 preamp for that matter) has no streaming ability unless the BluOS module is added. So, presumably it's the module that is Roon Ready and certified. What's to stop the owner of an M33 (when they become available and assuming no certification) from adding a BluOS module to his M33? The device would have 2 streamer modules (one built-in) but that's surely no problem as they'd each be identified by the software and Roon could respond to the BluOS module and ignore the built-in streamer.

I ask because I'm planning to get the M33 but already have the BluOS module that I could remove from my M32 / M12. Peter

I asked NAD about these matters and received this reply:

Vishnu M. (BluOS)

Sep 23, 2020, 9:34 PM EDT

Hello Peter,

Thank you for getting back in touch.

NAD Electronics is very aware of the situation and have spoken with ROON about their certification process regarding NAD BluOS Enabled products with a detailed front panel display.

NAD is confident the NAD M10 and C658 will be certified before then and no foreseeable hurdles with the NAD M33 or newer products entering the certification process and will continue a great relationship with ROON Labs. Due to the nature of the certification we cannot provide an ETA at this point, but rest assured this is being worked on.

In regards to your second question, the M33 runs BluOS as its main firmware so adding an MDC BluOS module to the M33 is not possible.

We add MDC BluOS to older players to enable BluOS for these devices.

Also please note that at this point no NAD or Bluesound devices are Roon certified. They are Roon endpoints. The certification is in progress.



I'm not sure what I make of the last paragrapg. Roon Ready vs Roon Certified? As long as they work with Roon (and vice versa), I'm not sure if I need to worry about the wording. Or should I before buying the M32? Peter
 
I am not sure Roon is being straight forward regarding it being free to get certified. I remember talking to a manufacturer and they mentioned Roon was charging a pretty hefty fee which put them off enough to not want to get certified.

I don’t disagree that they should only support certified gear. However, charging a large fee to be certified restricts not only their own growth it hurts the end customer as well. This would explain why their adoption of new vendors is slow. They have one of the few decent experiences out there for streaming music. One would think they should have been able to secure more vendors to join by now. The last thing high end audio manufacturers want to do is to write and support software.
 
I remember talking to a manufacturer and they mentioned Roon was charging a pretty hefty fee which put them off enough to not want to get certified.

Roon Labs do no charge a fee to certify devices.

In addition to Roon Ready work on Lumin, I also help a few manufacturers as part of my job. If Roon Labs charged us or the manufacturers I help, I would have known.
 
Roon Labs do no charge a fee to get certified.

In addition to Roon Ready work on Lumin, I also help a few manufacturers as part of my job. If Roon Labs charged us or the manufacturers I help, I would have known.

Interesting, thanks Peter that’s good insight. Are there no charges whatsoever to get certified from beginning of the process to end?

Wonder what those other guys were referring to.


Sent from my iPhone using Tapatalk
 
Back
Top