USB output is here

Answered

Comments

121 comments

  • KB

    I want to add on my post above and just discovered that on the phone app playing Adele it’s skipping between HR and MQA but when I just use the Node it’s MQA clean 

    0
  • Greg Pugh

    Same as others, when USB is selected, volume level is not fixed and is adjustable via the slider in the app as well as by my iphone volume buttons. 

    0
  • Eric Lai

    My KEF LS50 Wireless Mark I are working properly with my Node. I am using a Supra USB 2.0 Type A to Type B cable to connect them. My Node can detect my KEF automatically.

    0
  • Greg Pugh

    Tony, I don’t have a DDC and I don’t know why you’re giving me a lecture on the internal DAC.

    I thought I was very clear that I had plugged the USB output into my DAC and that I was still getting non-fixed volume, as many others in this thread have said.

    This is reminiscent of the SPDIF debacle. You seem very quick to blame users when they report bugs in new software, then end up backtracking when your engineers fix the problem they told you about all along.

    0
  • Greg Pugh

    John, if it's any comfort, I'm hearing you and have the same problem

    0
  • edward

    Being Arch-Linux the NODE uses ALSA sound architecture. Easy test would be to attach your device to 'any-other' Linux product via USB and see if the volume controls work or not. 

    Ropieee [the ARM based OS for Roon] would be a good example/benchmark for what can and can not be done with Arch-Linux...as it is Arch-Linux as well. 

    I have several DDC devices and DACs....the volume control is not functional on any device I connected to the NODE via USB.  However "ALL" of them are able to have the volume adjusted on any-other Linux device....including Arch-Linux.

    Easy to get defensive with so much negative noise in the air concerning issues. Best to step back, avoid the noise and look at the facts. This is not a per-user issue, its a global issue that can be easily fixed.

    I'm hoping that once all the noise has settled this easy fix can be done and over with....

    0
  • Victor Levis

    If this is just a software update, how does a USB port out magically appear?

    0
  • edward

    Its not magic.

    The USB port was always able to output audio....ALSA the sound engine/architecture was not configured to use USB as an audio output device.

    Actually out-the-box, if you have Arch-Linux 'or any Linux' as a base OS and install the ALSA sound module it sees and uses/lists all of the audio devices. ALSA comes with many utilities such as EQ for example, but once its installed it works out-the-box.

    0
  • Paul Francis

    Is the USB output on the node asynchronous?

    0
  • Ian Ball

    I am having no issues with my DAC (Topping D70s) but hearing from friends with certain DACs (Benchmark, Cambridge) are getting the BluOS message "Audio Output Error" trying to play thru USB. Settings in BluOS appear correct. Any ideas?

    0
  • Valerio

    In the past, Bluesound announced that the Node 2i would have not received the update for USB audio output.

    Is this still the case?

    0
  • Valerio

    @John Atkin then they would loose a customer...

    0
  • Greg Pugh

    @Chris Brook

    Thanks for verifying the problem with yet another DAC. I hope that you'll submit a bug report in the app so that the engineers can take care of it, since the party line on this forum seems to be ALL IS WELL

    0
  • KB

    Well my issues with regards to connecting my Zen Dac V2 seems to have resolved its self - Currently I can get stable MQA from Tidal to my external Dac with excellent results - My ears convince me that the Zen Dac v2 is superior to the Node dac - so much so I’ve swapped the Zen Dac out for the signature zen Dac V2 for the hell of it…

    0
  • Paul Francis

    @Oli T

    I have the same dac and see the same behaviour, when the buffer jumps constantly it is unusable, my work around is to leave the USB buffer to fill up to about 50% and then select a service and play a 16/44 track, the USB buffer then fills up to 75% and then falls back to 25% it stays this way and is fine apart from the odd faint pop/click.

    Switching to a 24/96 track the USB buffer sits at 50% +/- 10% but pop/click sound is more often. This tends to happen with devices that don't support asynchronous USB transfer.

    0
  • Richard Gingell

    I have a similar DAC, Audiolab 82000DQ, audio plays but I get  frequent pops and glitches as to make it unusable for me at the moment so gone back to the coax output.

    My dac works perfectly when feeding from raspberry pi or PC etc. via usb. 

    0
  • Mick Day

    I have now decided to return my Node N130 as the main features that I want to use via the USB output is Roon.  I have now built a Raspberry Pi based roon-bridge which gives me perfect playback from Qobuz and Tidal directly through my USB DAC.

    0
  • Greg Pugh

    Agree John, I'm looking at other options now. I want something that works reliably, that doesn't have weekly updates allegedly adding new features but breaking old ones, and that has tech support that doesn't tell me that everything is the fault of my equipment, which works fine with everything else.

    0
  • edward

    Hey all, heard back from tech support. Apparently since my DAC has an ESS Saber DAC, volume control from all digital inputs is through the DAC chip, which effectively tells the Node not to fix the volume. They didn't explain why they are able to have a "fixed volume" selection for Coax but not USB, but according to support my problem is "Solved." So there.

    According to its logs, its operating system is Arch-Linux and it uses ALSA sound architecture just like Ropiee and others.  

    It has fixed volume on all of my Dacs so its not a dac chip issue, I have Sabre too and others. 

     

    0
  • John Atkin

    It's disappointing Greg, as at a basic level it's a super piece of kit. The 'customer support' suggestion that I should do a factory reset just to solve Quboz loading slow was the final straw really.

    0
  • edward

    On the bright-side.

    The BlueSound Node has a lot of outputs now, all easily switched from the user interface. Plus, it has several useful inputs [TV, Optical and Analog].....and it still sounds pretty damn good. For me its a keeper!

    3 Digital Outputs - USB, Coax, Toslink

    2 Analog Outputs - RCA stereo + 1 sub

    1 Headphone Output

    1 Bluetooth Input/Output

    1 Airplay 2 Input/lOutput

    1 Analog Input

    0
  • Felix

    I also hope Bluesound adds Roon Bridge software component to the device, so it can be configured and provisioned as such. I currently have the NODE connected to Chord Qutest DAC over USB, and it works, but Roon thinks the NODE is the endpoint rather than the Qutest, and thus presents the device setup parameters for the NODE instead of the Qutest DAC.

    0
  • Greg Pugh

    @faizal

    I have the same problem, and according to posts here and my response from support, apparently Bluesound considers our DACs to be DDCs instead for some reason, and this is the fault of our equipment.

    No word on why they can't add a toggle for fixed volume like they do on SPDIF, but there you have it.

    0
  • Mark

    I've tried the USB output with two amps and 3 different DACs and still get popping and other artifacts every time.  Even without the volume issue, which I was willing to work around, the USB out is unusable.    Perhaps it is an issue with the ROON integration.

    However, the head in the sand approach by Bluesound customer service is eroding my previous enthusiasm for this company.  

    0
  • Seppi Evans
    Hi-Res

    USB DAC - ROON

    If you are using ROON and MQA with an external DAC, sending digital audio through the USB port of NODE (N130) may cause audio dropouts.

    USB DAC audio output for NODE (N130) with ROON is still classified as a beta release and is under development. Therefore, if you encounter audio dropouts, use USB DAC implementation natively without ROON until the feature is rolled out completely.

    Source

    https://support1.bluesound.com/hc/en-us/articles/4417440985879-How-to-enable-USB-Audio-Out-on-NODE-N130-

     

    0
  • Mark

    @ Seppi Evans.  I don't use MQA but thanks for the info!  Will do!

    0
  • Enricoclaudio

    You can use external DAC with Roon but you have to use Coax output. I have zero dropouts using Coax from NODE into my Topping E50 DAC. You have setup the NODE as "Renderer Only" in Roon for it to work. 

    0
  • Melvin

    I wish I saw this thread before purchasing the latest Node. No where else did I read USB-out disables subwoofer out. This is a huge disappointment for me and perhaps a deal breaker (I may send it back). This quote was the only reference I saw prior to purchase BTW:

    "Note: When the USB port is enabled, other audio outputs (Analog/COAX/Optical) are disabled."

    Why isn't Subwoofer out mentioned? Bluesound could have worded it by saying ALL other audio outputs are disabled. 

    0
  • Felix

    Indeed, Seppi Evans, using Roon and MQA (Tidal) with my Chord Qutest over USB results in frequent crackles and pops. Using MQA content via Bluesound app and Tidal - flawless. 

    0
  • Richard Gingell

    Just to clarify my previous post below, i do not use Roon so the problem is not just Roon related.

     

    "I have a similar DAC, Audiolab 82000DQ, audio plays but I get  frequent pops and glitches as to make it unusable for me at the moment so gone back to the coax output.

    My dac works perfectly when feeding from raspberry pi or PC etc. via usb."

     

     

    0

Please sign in to leave a comment.