I have just installed a Pi3 bridge into my system connected via USB to a Naim DAC-V1.
Everything plays fine from Tidal and standard 16bit files but when I try playing 24bit files I get an almighty hissy racket I have checked the display on the DAC which confirms that the file is 24 bit / 192 kHz and the buffer is showing constantly full so I think I can rule out network speed issues.
When I change the settings for the DAC to 16 bit it plays back normally. Any ideas?
Many thanks
Ian
@support info
Core PC i5 8GB RAM SSD disk Win10 Roon 1.3 build 196
Bridge Raspberry Pi 3B Roon Bridge 1.0 build 62
DAC Naim DAC-V1 (latest firmware) connected via USB
Hi @IanAusten ---- Thank you for the report and my apologies for the troubles here. May I kindly ask you for the following:
Can you please post some screenshots of the audio setting your are using for this end point (Pi3 - > USB - > Naim DAC) in Roon.
In your troubleshooting have you tried connecting the DAC directly to your core machine yet? If so did the device exhibit the same behavior upon playback?
Hi @IanAusten ----- Thank you for the follow up and taking the time to answer my questions for me. Both are appreciated!
Can you verify if you were to stream 24/192 to Pi3 + NAIM DAC-V1 end point via a different media player or software, say for example something like iTunes. Does the content playback correctly?
Hi @IanAusten ----- Thank you for the follow up! Can you please describe your network configuration / topology as well as providing insight into any networking hardware you may be implementing in your setup. I want to get an idea of how your devices are communicating and what tools are being used to make those connections possible.
Furthermore, have you done any testing yet with the Pi3 removed from the communication chain but still using the DAC as a network based end point?
Sorry for the tag in advance @Dan_Knight - would you have any suggestions on what I could try next? The USB gubbins in the Naim DAC are Audiophilleo if that helps…
Lets also check the USB logs for any clues. Play a 24bit file and replicate the broken audio. Once done, please paste results (or take a picture) of the following command:
Thanks for your help. I can confirm that firmware is the latest version on the DAC 1.16
Here are the USB logs as requested:
root@DietPi:~# dmesg | grep usb
[ 0.090597] usbcore: registered new interface driver usbfs
[ 0.090660] usbcore: registered new interface driver hub
[ 0.090736] usbcore: registered new device driver usb
[ 1.047449] usbcore: registered new interface driver smsc95xx
[ 1.474398] dwc_otg 3f980000.usb: DWC OTG Controller
[ 1.475775] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[ 1.477188] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
[ 1.481382] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.482761] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.484148] usb usb1: Product: DWC OTG Controller
[ 1.485514] usb usb1: Manufacturer: Linux 4.4.30-sc1+ dwc_otg_hcd
[ 1.486914] usb usb1: SerialNumber: 3f980000.usb
[ 1.491895] usbcore: registered new interface driver usb-storage
[ 1.510583] usbcore: registered new interface driver usbhid
[ 1.511987] usbhid: USB HID core driver
[ 1.853965] usb 1-1: new high-speed USB device number 2 using dwc_otg
[ 2.032169] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[ 2.033750] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2.317963] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[ 2.406211] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[ 2.409553] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2.451914] smsc95xx 1-1.1:1.0 eth0: register ‘smsc95xx’ at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:5a:03:2f
[ 2.528097] usb 1-1.5: new high-speed USB device number 4 using dwc_otg
[ 2.620853] usb 1-1.5: New USB device found, idVendor=279a, idProduct=0001
[ 2.622744] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.624530] usb 1-1.5: Product: Naim DAC-V1. Audiophilleo.com
[ 2.626244] usb 1-1.5: Manufacturer: Naim Audiophilleo
[ 2.627864] usb 1-1.5: SerialNumber: 00000
[ 2.633495] input: Naim Audiophilleo Naim DAC-V1. Audiophilleo.com as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.0/0003:279A:0001.0001/input/input0
[ 2.688505] hid-generic 0003:279A:0001.0001: input,hidraw0: USB HID v1.11 Keyboard [Naim Audiophilleo Naim DAC-V1. Audiophilleo.com] on usb-3f980000.usb-1.5/input0
[ 3.340934] usb 1-1.5: 2:1: cannot get freq at ep 0x5
[ 3.478253] usb 1-1.5: 2:2: cannot get freq at ep 0x5
[ 3.615012] usb 1-1.5: 2:3: cannot get freq at ep 0x5
[ 3.752034] usb 1-1.5: 2:4: cannot get freq at ep 0x5
[ 3.889000] usb 1-1.5: 2:5: cannot get freq at ep 0x5
[ 4.024957] usb 1-1.5: 2:6: cannot get freq at ep 0x5
[ 4.161963] usb 1-1.5: 2:7: cannot get freq at ep 0x5
[ 4.298003] usb 1-1.5: 2:8: cannot get freq at ep 0x5
[ 4.435006] usb 1-1.5: 2:9: cannot get freq at ep 0x5
[ 4.571020] usb 1-1.5: 2:10: cannot get freq at ep 0x5
[ 4.707028] usb 1-1.5: 2:11: cannot get freq at ep 0x5
[ 4.844075] usb 1-1.5: 2:12: cannot get freq at ep 0x5
[ 4.981074] usb 1-1.5: 2:13: cannot get freq at ep 0x5
[ 5.117087] usb 1-1.5: 2:14: cannot get freq at ep 0x5
[ 5.254121] usb 1-1.5: 2:15: cannot get freq at ep 0x5
[ 5.390152] usb 1-1.5: 2:16: cannot get freq at ep 0x5
[ 5.392124] usbcore: registered new interface driver snd-usb-audio
[ 542.065127] usb 1-1.5: 2:6: cannot get freq at ep 0x5
[ 542.068879] usb 1-1.5: 2:6: cannot get freq at ep 0x5
[ 695.897209] usb 1-1.5: 2:6: cannot get freq at ep 0x5
[ 695.900696] usb 1-1.5: 2:6: cannot get freq at ep 0x5
root@DietPi:~#
Let us know if problems persist with 24bit and broken output.
Also:
Do you have any other SBC’s (eg: Odroid C2) available to test the USB DAC with 24bit? It would be interesting to see if we get similar results, from other boards with your USB DAC.
Sorry to hear that, was hoping it would be something we could resolve for you.
It appears, either the DAC is incompatible with the current RPi Kernel, or, a possible issue on your DAC.
Unfortunately, the only way to exclude a hardware failure would be to test the DAC on another SBC (eg: Odroid C2 / Sparky).