HQP NAA - Raspberry Pi

I don’t think the bandwidth should be problem anymore with recent kernels – I successfully streamed DSD256 via DoP (which should use about the same bandwidth as DSD512 native) with a Pi3 (running DietPi) and a Mojo.

Finding a DAC that does native DSD512 with Linux is a different question though. :slight_smile:

Thank you René. I was thinking 6MB/s was too much for RPI3 shared bandwidth. Good news if you succeed. If i’ve understood you correctly:
DoP DSD256 required bandwidth = DSD512 native required bandwidth ?

I’m using T+A DAC8 DSD and i hope Amanero and T+A will fix current Linux USB driver and DAC FW limitation soon. I agree with you this is the main point to enable native DSD512 streaming > Linux device.

If you are using NAA, then DoP vs native doesn’t make difference in bandwidth consumption. DoP is handled at the NAA side, so there’s no wasted bandwidth to send DoP stuff over the network.

I’m currently running DietPi v148 and NAA (networkaudiod) 3.4.2-33 on RPI3.
Everything perfect, very robust !

How to update NAA to the last version 3.5.1 ?
Any NAA 3.5.1 changelog available ?

Thank you

1 Like

Hi volpone

What is the highest resolution you run with the HQP NAA DietPi?
Is it possible to rund DSD512 without hickups?

Hi @Christoph,
I don’t know because i’m using T+A DAC8 DSD.
Native DSD not enabled due to Amanero Linux USB drivers issue (Amanero FW).

So i’m limited on using DoP: DSD128. No hickups at all obviously.
But for DSD512 i’m afraid RPI3 ethernet bandwith to be too “short”, i hope to try it when Amanero issue will be fixed (if so).

I’ve asked directly on the DietPi support forum: http://dietpi.com/phpbb/viewtopic.php?f=11&t=1832

wget https://github.com/Fourdee/DietPi/raw/856637f99e6d3043d43b820b26be67dfd7159eb5/dietpi/dietpi-software -O /DietPi/dietpi/dietpi-software

dietpi-software reinstall 124

Upgrade done without issue.
Thank you @Fourdee and DietPi !

root@DietPi:~# apt-cache policy networkaudiod
  Installed: 3.5.1-35
  Candidate: 3.5.1-35
  Version table:
 *** 3.5.1-35 0

Any news on DSD512 from a DietPi?

@Dan_Knight Dan will be the best to answer that :smiley:

Hi, I’ve been using the Raspberry Pi 2 image from the signalyst website which is NAA version 3.42. I see that the latest is 3.51. Can someone provide instructions to update to the latest version? I see above instructions for dietpi. Is that the basis for my image? How do I log in to get a command prompt?

Will the new version allow me to do DSD256 in non-DoP mode on an Auralic Vega?

Thank you!

Hi @RBM,
Sorry to be back on this old topic.
I’m feeding my DSD DAC from ALLO USBridge. Due to AMANERO FW limitation i’m only using DoP (DSD128).

According to NetData Ethernet bitrate is 11000 -13000 kilobits/s (1.6 MB/s max).
In my understanding DoP encapsulation is X2 bandwith VS native DSD. So using native DSD128 would be 0.8 MB/s, isnt’it ?

0ther USBridge users are reporting 46000 -50000 kilobits/s (6.3 MB/s) max) on DSD512 native.

Could you confirm or correct my understanding about DoP / Native DSD bitrate ?

I don’t see any RPi NAA build on the HQP site… am I missing something - thought this was mentioned so posts back. @jussi_laako

Will the NAA option in DietPi work for this? @Dan_Knight

NAA available from DietPi is perfect. No issue, very stable.
Using it since few months both on Sparky SBC (ALLO USBridge) and on stock RPI.
DSD512 bandwith handling is another story, i’ve not tested > DSD128 (DoP)

Interesting - I had been running a core on DietPi X86 on Debian AMD64 with an i5-6500 and even up sampling to DSD512 to a Ropieee based RPi with no issues - just to see if it worked.

Maybe that would be thinner than a windows based NAA on the same hardware. But running Ropieee with RAAT passing DSD512 (LAN connected) works fine and is my main rigs setup to an OPPO Sonica DAC.

Interesting ! But in case AMANERO FW issue fixed i would like to use USBridge (vs RPI) and i’m not sure it is OK due to Sparky HW or SW possible limitation … However seems other users succeed: https://www.computeraudiophile.com/forums/topic/32132-allo-sparky-usbridge/?page=45&tab=comments#comment-786123

I have a Sparky too…but its destined for VOLT deployment when I can get the failed Kali and Piano 2.1 replaced…geeze must get onto that - Been down for a few months now :frowning:

My bad !
Sorry, answers were already on this thread:

So DoP X2 bandwidth consomption is on USB, not on Ethernet !
Seems ROONBRIDGE act as HQP NAA. DoP handled at the endpoint side.

What gives you that impression? DoP is just native DSD with a PCM-cloak. The overhead must be minimal?


But adding 8bits to each ”packet” is not doubling the bandwidth? Most DACs that consume PCM also require/desire 24bits package sizes and the software/driver pads 8 useless bits in those cases too?