Native DSD on Brooklyn DAC+?

Michael_Grant · July 15, 2018, 4:47pm

Brand spanking new Brooklyn DAC+ and Roon Rock install. It’s a network stream setup using an @allo.com USBridge in the chain. My problem is that the Roon sees the Brooklyn but doesn’t provide a ‘Native’ DSD playback option. My understanding is that the Brooklyn supports native DSD playback and that other Ethernet-USB Roon-Ready streamers - such as SOTM-200 - enable native DSD playback. So problem seems to be the Allo USBridge but despite installing latest DIetPi 6.11 it hasn’t resolved the issue. I’m trying to get @allo.com to respond to this issue but have yet to see any response. Considering returning my USBridge to replace with whatever device other recommend as best DSD option in this setup. Can anyone comment here on the resolving this issue AND how they have set up their Brooklyn DAC+ for optimal SQ with Roon?

Thanks!

Rugby · July 15, 2018, 11:05pm

Allo will need to patch Diet Pi with the drivers that will allow it to work natively with the Brooklyn DAC+. Each DAC requires its own driver patch in Linux. If you decide to go with a different Ethernet/USB device, I recommend that you verify it has been patched for the Brooklyn DAC+ specifically; take a look at the MicroRendu/UltraRendu devices.

Another option is that you could always try a cheap little windows box that just runs RoonBridge and has the Brooklyn DAC+ ASIO drivers loaded.

Michael_Grant · July 17, 2018, 1:33am

@Rugby @rahulkc_s Allo replied elsewhere suggesting the following instructions for adding the Brooklyn DAC+ to the USBridge: https://github.com/sparky-sbc/sparky-test/tree/master/dsd-designs

I tried both install options and neither caused my Brooklyn to be recognized for Native DSD playback. Sharing this here for anyone else who might be having this issue.

I’m giving @allo.com another day or two to resolve this and then I will just request an RMA/Refund so I can get an SMS-200 which claims DAC+ support for native DSD.

Also: @RoonFAQ Why does Roon list the Brooklyn DAC+ as ‘Unidentified’. Why I go to the section to ID based on Mytek as a vendor it ONLY lists Manhattan and a very old dac of Mytek’s. Neither the first Brooklyn nor the Brooklyn DAC+ are listed. Why?

Dick_Vliek · July 17, 2018, 1:39am

I can confirm that the SMS-200 will enable you to stream native dsd to the brooklyn dac+ (although in my case the SMS-200 needed a complete reinstall of their software before it worked).

Michael_Grant · July 17, 2018, 1:45am

Thank you @Dick_Vliek That seems like a small price to pay if it works properly. I’m also unclear if any driver installs that @rahulkc_s is asking for will persist with DietPi updates. Regardless, the driver they asked me to install doesn’t solve the problem so it’s a moot point.

Dick_Vliek · July 17, 2018, 1:52am

Can’t help you there, i’m not a linux expert. But I do use the USBridge to feed my Chord 2Qute DAC and it is a very good device given the price. No native DSD, but DSD over DoP is fine (I hardly use DSD).

rahulkc_s · July 17, 2018, 2:40am

share me the rsults of below commands

lsusb
cat /proc/asound/card1/stream0

Michael_Grant · July 17, 2018, 3:26pm

Bus 004 Device 010: ID 25ce:0025
Bus 004 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 004 Device 002: ID 0424:2412 Standard Microsystems Corp.
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@USBridge-Office:~# cat /proc/asound/card1/stream0
Mytek Digital Brooklyn DAC+ at usb-aotg_hcd.1-1.1.4, high speed : USB Audio

Playback:
Status: Stop
Interface 2
Altset 1
Format: S32_LE
Channels: 2
Endpoint: 1 OUT (ASYNC)
Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000
Data packet interval: 125 us
Interface 2
Altset 2
Format: SPECIAL
Channels: 2
Endpoint: 1 OUT (ASYNC)
Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000
Data packet interval: 125 us

Capture:
Status: Stop
Interface 1
Altset 1
Format: S32_LE
Channels: 4
Endpoint: 1 IN (ASYNC)
Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000
Data packet interval: 125 us
Interface 1
Altset 2
Format: S32_LE
Channels: 8
Endpoint: 1 IN (ASYNC)
Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000
Data packet interval: 125 us
Interface 1
Altset 3
Format: S32_LE
Channels: 8
Endpoint: 1 IN (ASYNC)
Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000
Data packet interval: 125 us
Interface 1
Altset 4
Format: SPECIAL
Channels: 2
Endpoint: 1 IN (ASYNC)
Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000
Data packet interval: 125 us

rahulkc_s · July 17, 2018, 4:10pm

Thank you for sahring the details.
Driver updated with correct ID and uploaded on same link.
repeat the steps once again.

rahulkc_s · July 24, 2018, 12:43pm

Thank you for your update. that Brooklyn Mytek DAC+ DSD native working.
Yes we will include the update on coming version dietpi updates.

A_G · July 28, 2018, 11:09pm

Hi Dick, could you confirm if Roon thinks it is talking to the Brooklyn DAC+ despite the SOtM SMS-200-Ultra? So in otherwords the SMS-200 is ‘invisable’ Thanks Andy

Dick_Vliek · July 28, 2018, 11:44pm

No, the brooklyn dac+ is an unidentified device in Roon. Signalpath looks like this:

But the SOTM software on the SMS-200 (eunhasu) has this:

Btw I have the SMS-200 not the SMS-200ultra.

A_G · July 29, 2018, 12:07am

Hi Dick, thank you for taking the time to post - i’ll make an assumption that MQA will reach the Brooklyn OK

As an aside - I don’t think it makes any setup difference SMS-200 v SMS-200Ultra.

I am thinking about a Roon Nucleus, that would sit in my home office and plug directly into the router, with the SOtM SMS & Brooklyn in another room - I don’t want to use the Nucleus plugged directly into the Brooklyn.

Thanks
Andy

Dick_Vliek · July 29, 2018, 12:29am

MQA will indeed reach the Brooklyn just fine.

A_G · July 29, 2018, 12:45am

Thanks again, much appreciated the image/info

TAEWOONG_YANG · October 4, 2018, 1:10pm

I am using Brooklyn DAC + and do not support NATIVE DSD.
I installed ROCK on Intel NUC.
Brooklyn FW 1.22

Michael_Grant · October 4, 2018, 2:23pm

I had this same issue with my DAC+ and it required a software driver be installed. I got the driver from the @rahulkc_s @allo.com support people. I do think that Allo should include this driver in whatever Dietpi install is built for their platform to avoid confusion for new DAC+ owners. Hopefully you can get a response from the Allo folks here with the same driver info.

Michael_Grant · October 4, 2018, 2:28pm

@TAEWOONG_YANG Found what Allo had given me. Try this:

https://github.com/sparky-sbc/sparky-test/tree/master/dsd-designs

TAEWOONG_YANG · October 4, 2018, 2:41pm

@Michael_Grant Thank you for reply
But I not using dietpi.

Yuri_Petusko · October 4, 2018, 4:04pm

You don’t have anything in between your NUC and Brooklyn dac besides router, like sms-200 for example?