I have verified that my Nodes are at the most current update.
Can you please try to perform a factory reset of your affected players?
Thank you @noris,
I did a factory reset on both Nodes. The problem still persists on both.
Do you have any more recommendations for troubleshooting?
Sorry to hear that the factory reset hasn’t helped! I would like to see if your Roon logs contain further clues, can you please let me know the exact local time + date + track you hear the static occurring? Afterwards I can activate diagnostics and see if your logs contain further clues, thanks!
February 3, 2021
7:52pm Central Time - Don’t Keep Me Wonderin’ (Qobuz library)
7:58pm Central Time - the Pusher (Local library)
Do I need to send you the logs?
I just went through this drill, except my Node 2i is on wifi. After fending off tons of “can’t use wifi on Bluesound” posts, I found two workarounds. (For reasons too long to go through, it’s not practical for me to hardwire right now so that advice was not helpful.)
I got a Raspberry pi which is a WAY cleaner endpoint on wifi than the Node.
If I use the BluOs and select Roon as the output on THAT software first, rather than starting to play music on Roon and selecting the Node as the endpoint, the signal cleans right up and I don’t get sputter or other junk. This makes no sense to me, but it is what it is.
I believe you indicated that playing thru BluOS was better, which may be the same thing I discovered.
BTW, it seems that everyone on Roon forums blames Bluesound, and the Bluesound house techs I talked to blamed Roon. Lots of buck passing and finger pointing.
FWIW, here’s a link to a very long troubleshooting discussion that may have a useful nugget or two for you.
Thank you for your reply. I had actually read through a number of these threads, including yours, before I posted. Unfortunately nothing seems to fix it.
I have tried opening the BluOs app, then selecting Roon (from BluOs app) prior to opening Roon’s app, per your recommendation. This had no change for me. Am I understanding you correctly on the steps to take?
Yes, you are correct, I can play any music from the BluOs app (NOT incorporating Roon) and it’ll play flawlessly. It’s unfortunate because I do like the Node’s sound. I think as a stand alone product without Roon it’s a good value.
My concern as well is, if this issue Does get fixed, how long will it last? Do I need to hold my breath after every firmware or software upgrade? There is a long list of threads with Bluesound compatibility issues. I haven’t and don’t have any issues with either of my Bluesound players besides trying to incorporate Roon.
@dcw96161 how are you using the Raspberry pi as a workaround? Are you using it as an endpoint and then running it into the Bluesound input? I don’t have any experience with them.
Thanks again for your help.
I did want to also note, that prior to my post, I did have the Node 2i and the Roon Rock connected through a managed switch. After reading through other posts I changed my networking layout. I do still have a managed switch in my network but the Roon Rock and the 2 Nodes are now connected to an unmanaged switch that is directly connected to the router.
I’m not sure if this helps with your troubleshooting.
Were you able to access the time stamped logs?
What I found was that if, starting on the BluOS app, I chose whatever music I wanted, then selected Roon as the output, all was good. Again, pointing BluOS to Roon, rather than pointing Roon to Node. Selecting music on Roon, and then selecting the Node as the end point gets me incessant signal stutter. Nanosecond hiccups every 3 to 5 seconds. So I don’t “bypass” Roon at all, it’s just a matter of changing the sequence of button pushing. I discovered that mostly by accident. It doesn’t make sense, and just reminds me of old video games like Myst and Riven. I have yet to hear any explanation for this but I’m not holding my breath.
As for the Raspberry pi, I did not want to go down that road. But I posted on that Roon forum as well, here, and got a lot of help from fellow Rooners. It turned out to be pretty simple. Since I play through an integrated amp with its own DAC, I did not have to purchase or attach a HAT/DAC for the Rpi. Although I may at some point for fun, now that I’ve gotten this far. It was about $50 in parts from Amazon (a Rpi and case), and an hour’s worth of assembly time, and another hour or so getting the software loaded properly, and I was in business. Software loading took a bit longer than it should because I missed an important instruction point. There are lots of resource links in the Roon/Raspberry Pi forum, and it winds up being pretty straight forward.
So these are two workarounds, but they’re just that. And the Rpi workaround isn’t a great solution anyhow, as it takes the Node out of the loop completely and renders it superfluous, making it a $500 paperweight. And again, my problem is different that yours as my Node is NOT on ethernet. (So you will be spared the Rooner mass pile-on telling you not to use Node on wifi.)
But I’ll work with these half-measures until I can get the Node hard wired. Or not. Apparently judging from your experience, that’s not a panacea.
In your situation, maybe you could try running the signal from a Rpi USB port into the Node then out to Roon, thereby bypassing the Node’s apparently wonky network interface? I have no clue whether that would do anything, but so much of the Bluesound criticism in this forum is focused on the Node’s network interface, and this would remove that from the equation completely because its signal would be coming in from the Rpi USB port, not an internet source.
Hi @dcw96161 ,
I don’t get the same results as you do for your workaround. Here is what I did:
Open BluOs, choose music from my library, play, then select Roon from the left within BluOs. When I do this sequence, whatever was in my queue in Roon will then play. All of these steps are performed without opening Roon. Problem persists. I tried clearing out my queue in Roon, close Roon and then doing the above steps within BluOs again.
Nothing plays, so then I open Roon and play anything. Problem persists.
Did you notice a sound quality difference using the Raspberry pi? Am I correct that its just a network interface thats taking the signal from Roon and sending it to the DAC?
I did notice SQ improvement, but ONLY insofar as the incessant signal stutter stopped. Since my DAC is part of my integrated amp (Cambridge Audio CXA61) and both the Node and Rpi feed into that, the DAC in the Node is irrelevant (or, more accurately, superseded by the DAC in the IA), and I don’t need a DAC for the Rpi.
Yes. I believe you are correct that the Rpi is just a cleaner signal conduit from Rock to DAC. I may add a HAT/DAC to it just to experiment, but that’s unrelated.
I like that the Rpi is portable and versatile, so I may also play around and move it about from zone to zone. But, again, that’s unrelated.
Our problems seem to be to be related but different. Related in the sense that the problems with network access in the Node seems to be a larger issue than just Ethernet vs wifi. Everyone here kept telling me to hardwire the Node, but the—so far—successful workaround in button-pushing sequencing between the Node and Roon, and your challenges even though you ARE hardwired, suggest strongly that the issue is not that simple.
I found a fix (wonky though it may be) despite being on wifi, and you are having similar problems despite being on Ethernet, and my workaround is NOT working for you.
The one thing I would add is that maybe your implementation of the workaround is incomplete. ISTM when you select Roon as the output in BluOS, the Roon queue should clear and accept the new input signal from BluOS rather than pick up and continuing whatever was in the Roon queue. But I may be misunderstanding that part of your post.
Hi @mendres ,
Thanks for letting me know those timestamps! Yes, can I please request that you use these instructions to send me a copy of your Roon Core logs? Thanks!
@noris the logs have been sent.
Hi @noris ,
This afternoon I was able to resolve the issue, for the time being at least.
This caught my eye from @Robert_Frohn-Tefehne
I went in my BluOs app and removed all shared drives. This cleared up the audio immediately for me. This was the only change I made since last week. Also, moments prior to removing the shared drives I had static/sputtering through Roon. Now gone!
Does the issue lie within Bluesound’s mapping of shared drives?
I have 2 Bluesound Nodes. I found that if you do a factory reset on one and finish the setup process before you do a factory reset on the 2nd Bluesound, the network shares aren’t cleared out. If you were to perform a factory reset on both, wait until they are both showing that they are ready to be set up, would this clear the network shares in BluOs? If you only had one Bluesound device on your network and performed a factory reset, would that clear the shared drives? I’m unable to test this at the moment.
Could this be why the factory reset works for some but not all? If the shared drives don’t get cleared the problem remains?
Another note I’m now realizing. When Roon worked with Bluesound, prior to this issue, they were both connected to the same shared drive on a Synology NAS. Sometime before I started noticing the issue, I made a change. I attached an external hard drive directly to my NUC Rock and removed the mapping to the NAS. I left the Nodes, through BluOs, connected to the Synology NAS. Could there be an issue of having them look at separate drives?
@dcw96161 does any of this correlate to your situation?
@noris does this correlate with diagnostic findings?
Hi @mendres ,
Thank you for looking into this further!
It could be that not using the shares also reduces the load on the Bluesound device, allowing it more resources to operate properly and prevent the static from occurring. This is an interesting observation that I have forwarded to the team!
Has the static still been absent since removing those shares?
Hi @noris ,
I have not had any static since the removal of the shared drives to my Bluesound Nodes.
Another note, the shared drive, that the nodes were looking at, have approximately 1,000 albums.
I resynced the shared drive back to the Bluesound Nodes as of yesterday afternoon. One day in, still no static through Roon. I will let you know if the issue comes back.
I stumbled upon this thread
as I had created this one:
I think there is a problem with Roon and what they are doing in communicating to the bluesound devices.
Roon is asking/forcing a sync on the bluesound file share
bluesound is attempting to do a sync on a file share - even if its set incorrectly
this is being requested by roon
as the bluesound plays music fine - even with the incorrect fileshare setting
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.