I had peviously a Linksys 8-port managed switch and IGMP Snooping was enabled. I had no problems with it. But the switch died in december last year and I had an 1 Gbs umanged switch at hand - so I used it. My Problem is the Devialet which requires to manually set the speed to 100 Mbs - for some users. It’s a bug of my Devialet.
You may want to get a little 10/100 mbps switch to plug between the main switch and the Devialet, they are a few euros on Amazon.
Do you always let ChatGPT do the work for you?
I have never use ChatGpt or any other AI in my life. If I could get rid of the AI generated answer that appears in many of my Google searches I would.
6 Likes
Typically, I would remove comments such as you made, but since @Wade_Oram has replied, and it is patently obvious that his replies aren’t AI-generated, I will let it stand. In future, if you have any concerns about a post, please flag it first.
@Wade_Oram, type -ai after your search. As yet, I haven’t found a way to set this automatically, but I hope to create a custom search in Firefox.
7 Likes
@Wade_Oram - Thanks for all you great comments. Highly appreciated.
Torben
3 Likes
Roon works great for me too. It even works over a VPN without any issues, as well as a providing a stable ARC experience over 4G during a holiday recently.
If this frustrates some people, then so be it. I don’t think it is fair to say that Roon is buggy or unstable when it works great for a lot of users. Software is not something that just works for some and not for others. Given that the circumstances are the same it should and will behave the same. Let’s find out what these circumstances are instead of pointing at the software. I am more than willing to share my setup, if it helps anyone:
Intel NUC clone with ROCK installed and music on an internal SSD - R7800 router - Cat5e ethernet - Unifi managed switch - Wiim Pro Plus to a Naim amp. Next to that, 2 Sonos speakers connected to wifi. On the R7800 I run Wireguard VPN and run Roon Bridge in another location on a Raspberry Pi with a VPN client. This whole setup is rock solid.
1 Like
It looks like quite a few people have Roon working with managed switches/Unifi. Everything was working for me for over two years until about a few months back, and recommendation system started to break. Obvious blame went to my DNS/VLAN setup (all my Roon capable devices are on same VLAN). So I took my ROCK to my friends place who uses ISP provided default setup, and same music recommendations that my account was stuck at appeared. Additionally since the day before yesterday ROON ARC stopped working for me! So everything was working for me and things started to fall apart with no changes in my network setup. And only thing I can think of that affected ARC is software update day before yesterday.
Basically I have concluded that past success is no guarantee of future performance. And strange thing is some things work and others don’t. And I understand my subscription doesn’t cover cost of fixing bugs that only affects me. But bugs don’t fix themselves , and it’ll probably affect someone else later. So while my music experience will not be same without Roon, handicapped Roon is no fun either.
I wholeheartedly support this statement. I’ve had a VERY similar experience, have tried virtually everything including dumbing the wifi network I have running Roon to 3 devices (the router, a Macbook Pro as the Core and an 2024 iPad 10 as an endpoint). Every other streaming service on this setup works flawlessly. Roon fails nearly every time I use it. I just don’t understand how the load could possibly be this demanding…this is high speed wifi 6 on 3 devices on a 500GB connection. There’s NOTHING ELSE ON THIS NETWORK, including a dedicated fiber connection. Roons turnaround time on open tickets is abysmal and the answer is always “you need to consider running a hard line to the core” which I explain over and over again IS NOT POSSIBLE in the 200 year old farmhouse in which I live/work unless someone wants to pay for drilling through 2 food thick brick walls. When I can consistently get streamed 4K Ultra HD media with Atmos over wifi, to a $200 TV and a Roku, flawlessly, as well as upstream/downstream video, files, etc. for my business, flawlessly, and a music streaming service fails transferring a CD quality file from my Mac to my iPad over wifi (when VOX, Plex, Qobuz, etc all do it just fine) even if there’s a minor amount of DSP involved, I just don’t buy the excuses. The core software is heavily flawed.
Not a facetious comment but given what many users spend on equipment paying someone to do this would not be expensive, nor would buying the equipment to DIY be either. Long masonry drill bits are readily available for just this purpose. However, temporarily running a long piece of Cat5e as a test is the first step to see if it solves the issue with a wifi connected core.
1 Like
I have been up to a point where I did about the same, reduced Roon to just one windows PC with Roon as core, remote and playback all local with just an internet connection directly to my modem, so virtually no network at all and still the slowdowns happened randomly. Tried this with my mac mini and my brand new macbook pro as well and the same happened. Sooner or later it slows down up to a point that it takes ages before playback starts etc. Like I said, every other method of music playback and yes even 4k video streams work flawlessly, the only thing that has a problem is Roon. Now there will be more reactions tat “Roon works differently” but frankly I don’t care anymore, all I see is these slowdowns no matter what I try. Now you can still blame it on my isp modem but that’s the part I just have to live with. All I see is that literally everything works like a charm, except Roon.
1 Like
This is my setup and my (sucess) story:
Roon Core running on Intel NUC i7 7th Gen on Debian Linux (+ HQPlayer Embedded). Gigabit Ethernet link to managed switch.
Digital Transport 1 (RAAT): Raspberry Pi3B + Allo DigiOne with RoPieee. SPDIF Coax to RME ADI-2 DAC FS. Gigabit Ethernet link to managed switch.
Digital Transport 2 (RAAT/NAA): Raspberry Pi4 with RoPieee. USB to RME ADI-2 FAC FS (same device as Digital Transport 1). Gigabit Ethernet link to managed switch.
Digital Transport 3 (RAAT): Raspberry Pi3 + HifiBerry Digi+ with RoPieee. SPDIF Optical to AVR Pioneer. Gigabit Ethernet to Wi-Fi bridge. With this digital transport, I always use 4x upsample (176,4/192 kHz) because the AVR’s DAC has issues when faces a change at the sample rate base. So to avoid chages, I upsample to 4x.
Network DAC (RAAT): Allo Sparky + Kali reclocker + Allo Piano DAC with DietPi. Analog output to 90s Sony Stereo. Wi-Fi to AP and Wi-Fi PtP to Roon Core’s building (ca. 500 m apart).
I am aware that some folks can find themselves with issues while running Roon, but here I expose a (not so simple) scenario that works.
The network also includes an IPTV STB (Multicast traffic) sharing the Wi-Fi bridge with Digital Transport 3 and it works, but this is another story and does not belong to this forum.
Edit: I forgot a couple of Wi-Fi endpoints: an iPhone and an iPad. Both Wi-Fi devices, with 1 wireless hop at main building and 2 wireless hops at the second building.
P.S.: I apologize for the so telegraphic style but I thouth that, in this case, the data was more important than the prose.
Couple of points here:
- I’m not modifying a 200 year old house that doesn’t belong to me to make a fancy music streaming service work.
- The streaming service should work, and people should not need to heavily invest in network infrastructure for it to work. If Roon’s use case is for whole house installs with cabling that’s fine, but that is limited to a very small market. A product like this that doesn’t AT ALL take fixed point installation difficulties into account, especially with as advanced as wireless networking technology has become, is poorly implemented.
The problem I suspect is that Roon can’t deal with any sort of wifi buffering, even if it is ostensibly peer to peer and it’s a design flaw (or a feature if you ask Roon support) in that the render engine prioritizes some things over others ex of the capabilities of the endpoints or core processing capabilities. My suspicion (and I could very well be wrong) is that Roon’s processing engine hasn’t kept up with the capabilities of modern hardware that CAN deal with buffering more effectively because the processing speed is to the point of nearly real time. That would likely dictate a re-design of Roon’s core rendering and DSP systems and they are satisfied with laboring on based on the current platform because the “dedicated audiophiles” that buy Roon servers etc will happily hard wire everything. Instead, we are left with “traffic jams” as the core can’t spit out stuff fast enough for the endpoints to receive when it sees anything related to wifi buffering, even if there’s no other traffic. Again, just a suspicion.
Fair enough, just trying to help. I do not disagree with your 2nd point.
I appreciate you trying to help. I think most of us that have had these issues with Roon are a little gun shy about the “well just test it with a hard line so you can eliminate the issue”. The problem with that is if it were feasible to do so, most of us would have already done that and have avoided the whole customer service thread thing. I am nearly 100% certain that running ethernet to the Roonserver and/or endpoints would solve the issue. I could, if I really wanted to, put a NUC/Rock or Nucleus One at the router with a great deal of effort and I have received permission to do so from the owner, but why should I have to do that when I have a perfectly functional MacBook Pro? That also doesn’t guarantee that the wireless endpoints aren’t going to have issues and that’s another $00-$600 in hardware plus all the time to set it up again, etc. And then I can’t use Roon on the road with DSP (which I can do if I bring my laptop with me) although that’s probably moot as I’m getting rid of Roon now anyways.
1 Like
This is how I set mine up day one. Never had an issue or made a change since. 
It just works.
i probably missed it in one of the replies, but to clarify, it’s really only the core/server that should be wired to the network. The endpoints perform just fine if wireless.
1 Like
That’s not always the case. At my other house in CA, I have a Roon core wired to the network and have fails at wifi endpoints. It’s Roon that’s failing, again no other service does. And I think our point is that the core shouldn’t need to be wired. Wifi technology has advanced significantly.
ah that’s a bummer. Most of the anecdotal evidence I’ve read was that a wired core solved most every problem. (My experience rings true, anyway.)
Question: was it EVERY wireless endpoint? or just some? Did it matter what kind of streamer, etc…? Do you have wireless repeaters/routers throughout the house? Always looking for clues/evidence/specifics.