Crackling on N130 Node using Roon with USB out
Answered
I am having this exact issue using Denafrips Ares II to the point it is unlistenable. Just purchased a couple days ago. No issues with native app or using coax SPDIF out. There are a ton of posts about this. Apparently, the released the new NODE last year, and only enabled USB output in December, so effectively, it's a beta. I hope the Roon integration gets sorted, as I am very disappointed that my first "Roon Ready" device actually isn't.
Also, HDMI eARC volume control doesn't work with USB out, but does with coax out.
-
I'm afraid I reacted too quickly. Indeed, the first few tracks were fine and then the crackling came back. So indeed back to coax:-(
0 -
Hi Peter,
Please send us a support ticket using the BluOS app, this way we can review your diagnostic logs.
In BluOS app, BluOS >> Help >> Send Support Request.0 -
@Mark T
I have done as requested. I do believe though that many other people have also logged the fault yet after 9 months there is still no resolution.
0 -
I had a response to my support ticket which just outlines the same useless solutions that have already been posted here that don't and never have resolved the issue.
The first step was to manually activate the USB port....yeah ok...
The second step was to setup Roon for MQA playback. I'm not using MQA or Tidal....
Bluesound and Roon need to sort themselves here on this one0 -
I have two Node3 devices connected to external DACs, Chord Qutest and ifi Zen DAC using USB cables. Both have the same cracking and dropout when using Roon. No problem with Tidal connect and Spotify connect. Agree that BS and Roon should sort this out.
0 -
Another disappointed Node N130 owner here. After a long wait for the resolution, looking to move forward to another transport (like the Holo Audio Red which looks and apparently sounds amazing).
Bluesound folks are eager to blame the DACs here but the only constant in the systems that suffer from this behavior is the Bluesound implementation of RAAT. No DAC consistenly has this issue as use of another transport fixes it. Roon is not the issue either as it only suffers from this issue when used with Node. There is no way to avoid the conclusion that this issue is squarely on Bluesound to fix, which has not happened yet. Blaming the DAC manufacturers for not sending back this and that looks weird when it doesn't bother any other digital source out there.
0 -
OK well since I am the last person to leave a spicy comment here, why don't I follow up by pointing out that apparently this issue has been resolved in the N130 firmware version BLUOS 3.20.52: "ROON improvements when using External DACs". Oddly it seems none of the threads on this forum were update with this information when that happened. My complaint above happened *after* the fix was already out, so I also should have checked the release notes prior to complaining.
Good thing I am a serious procrastinator and in the 4 months since writing my previous comment got nowhere near deciding which streamer to by, and am still using the N130.
I have been listening to Roon through the N130's USB out for number of days now and have not experienced a single issue with it. It has been absolutely flawless.
Wanted to dop by and leave a comment to make sure anyone else Googling this topic realizes it's not an issue anymore.
2 -
Glad to hear they finally fixed it, but it's far too little too late for me. Based on how they handled this, I won't ever buy another Bluesound product, nor will I recommend them to anyone. They shrugged off the problem for a very long time and refused to allow me to return my node to them 10 days past the 30 day mark, when I realized that this was not going to get fixed any time soon and the Node I bought was totally unusable in my system.
0 -
I agree this has taken far to long to sort out. Selling a product with the promise of doing something and then not delivering in a reasonable time frame is just not acceptable. I like many have moved on and sold my node at a loss but I also love the bluos system so now have an NAD M33.
0
Please sign in to leave a comment.
Comments
39 comments