Very complex and likely problematic setup to do instead of just having two RPi4 NAAs for example.
And sort of defeats the purpose of NAA which is to have slim bare metal low power / low noise device to serve simple I/O task…
Very complex and likely problematic setup to do instead of just having two RPi4 NAAs for example.
And sort of defeats the purpose of NAA which is to have slim bare metal low power / low noise device to serve simple I/O task…
Agree about the complexity but I’m familiar with the tech.
And since I already have hardware lying around I’m not sure of spending extra for a couple of RPis.
On my previous question regarding getting the stream from Tidal running in a different machine than HQP, what would be your recommendation for connecting with auto rate switching?
Hi!
Want to test how to connect Tidal on a WiiM Pro to HQplayer Desktop or Embedded → NAA ->DAC
So if using WiiM Pro running Tidal from Wim Pro App
Connect WiiM Optical out to:
This device:
https://a.co/d/g0tc9YP
And the USB to NAA (input-NAA)
On Hqplayer settings.xml add
<input address="input-NAA" device="USB Audio (RPi4)"
ipv6="1" name="NAA USB Audio" samplerate="0"
short_buffer="0" type="network6"/>
then HQPlayer playing to the second NAA connected to the DAC ?
It’s not going to work. This device converts USB audio to SPDIF, not the other way around.
In my case it works really fine. One issue I have is with HQ Player Desktop on a mac. When I stop the playback on the input NAA, music stops but it doesn’t seem to stop (pause) the HQ Player. I can hear chopped bits of song separated by long fragments of silence going out of my speakers for about a minute or two until buffer gets exhausted but even then the time counter in HQ Player increases. It goes up about a second per minute.
Tried this on Ubuntu and problem doesn’t exist.
I’ve noticed the same
Depends on what your HQPlayer is running on?
Excuse me, but I cannot quite follow what is the difference / setup in this case.
What happens when you stop the source depends on how the source is connected and what the source (OS) does in such case. Some systems keep clocks running and playing silence, while some others stop the clocks, etc. So there is no generic answer that would apply to all cases.
Setup is the same, only difference is the machine hosting the HQ Player Desktop.
Ifi Zen Stream → USB → NAA (RPi4) → Macbook with HQ Player Desktop → NAA (RPi4) → USB → SRC DX → Dual COAX → Chord Qutest
On above setup it keeps outputting sound after stopping the music. Exactly the same setup but with another machine running Ubuntu istead of mac. No Problem at all.
It’s not a big deal, I just mute my preamp after stopping the music. The problem is I often forget that it has been muted when I come back for another listen Unfortunately my Ubuntu PC can’t handle LNS15 sinc-medium@768khz with adaptive rate set to “when needed” (I prefer to keep it this way because Qutest is pretty slow at changing between rate families).
That’s strange if the HQPlayer version is the same. Since it’s all same software, and not even OS things like CoreAudio involved…
Any possible difference between settings?
And it indeed makes sense because Chord DACs anyway run out of single clock. So switching between clocks only affects the CPU load.
Thank you, Jussi.
I finally managed to get the second Pi CM4 work nicely as input NAA to feed Spotify from my Surface Pro to my HQPE machine.
Actually, at first, I did not know where to insert the input address session in hqplayerd.html! Also did not know where to select the input in HQPe machine so that the input NAA appear in my Surface Pro!
My chain for Spotify now is:
Surface Pro —USB— Tofu Pi CM4 (input NAA) —LAN— HQPlayer embedded 12700K —LAN— TOFU Pi CM4 (output NAA) —USB— Holo Spring 3 DAC.
Is there any way for me to get the Pi4 NAA connect via WIFI instead of LAN?
I’m using NAA OS 4.6.0 for the input NAA
How about this device:
Toslink input to USB output for streaming
Connect WiiM Pro SPDIF output to → https://a.co/d/3CTjFBJ ->SPDIF Input and https://a.co/d/3CTjFBJ USB output to NAA (audio input source)
The review from Amazon
So Tidal on Windows/Mac on machine (A) and HQPlayer on Windows on machine (B)
Ubuntu shows version 5.3.2.1 while OSX is 5.3.2 (both latest downloaded from the website). The only difference in settings is FFT filter length. 512 on Ubuntu vs 256 on OSX. I’ll try setting that to the same value tonight and test if that helps. Does it actually have much influence on CPU load (I also have convolution filters loaded in the matrix)?
I have one more question. Is there any documentation for hqp5-control cli? I can’t find any and I wonder if there’s any flag that allows importing and activating xml settings? Something like:
hqp5-control.app/Contents/MacOS/hqp5-control localhost --import-settings settings_x.xml
I have included the needed components (wpa_supplicant) in the image, but this is totally unofficial. So if someone wants to try WiFi, then they need to figure out how to setup the wpa_supplicant + systemd-networkd combination.
There are some instructions across the internet:
https://wiki.somlabs.com/index.php/Connecting_to_WiFi_network_using_systemd_and_wpa-supplicant
https://wiki.archlinux.org/title/Systemd-networkd
Yes, likely works if you are fine manually switching between different source rates. If you are connecting just a CD-spinner or Spotify as source it is pretty straightforward since these are always fixed 44.1k.
I have for example RPi4 + this:
https://www.hifiberry.com/shop/boards/hifiberry-digi-io/
In this nice steel case:
https://www.hifiberry.com/shop/cases/steel-case-for-hifiberry-digi-pi-4/
This works very well as manually switched rate input NAA.
Many thanks for sharing. Look amazing. Will check if shipping to HK and cost.
Is this correct:
iPhone playing Tidal source connected to shown cable.
Input NAA:
I’m testing using a miniPC as NAA (naa-e519bbe) with cable shown connected to the previous iPhone
On desktop Hqplayer settings.xml I added the input with the NAA "naa-e519bbe:
<?xml version="1.0" encoding="utf-8"?>
<xml>
<engine adaptive_rate="1" auto_family="0" cd_drive="" channels="2" cuda="0" direct_sdm="1" dsd_6db="0" fft_size="512" gain_comp="-3" idle_time="0" multicore="auto" pdm_conv="8" pdm_filt="0" quick_pause="0" sdm_conversion="2" sdm_integrator="5" short_buffer="0" type="network6" volume_limit="-3" volume_min="-60">
<defaults bitrate="11289600" dither="5" filter="40" filter1x="37" mode="1" modulator="13" oversampling="50" oversampling1x="23" samplerate="192000"/>
<coreaudio/>
<network address="naa-0c9aa262" any_dsd="0" dac_bits="32" device="hw:CARD=Product8,DEV=0" dualwire="0" ipv6="1" pack_sdm="0" period_time="250"/>
<input buffer_time="0" channel_offset="0" dev_name="" device="54" dualwire="0" format="auto" pack_sdm="1" samplerate="0" short_buffer="0" type="coreaudio"/>
</engine>
<log enabled="1"/>
<interface full_screen="0" verbose_fs="0"/>
<input address="naa-e519bb4e" device="USB Audio (RPi4)" ipv6="1" name="NAA USB Audio" samplerate="0" short_buffer="0" type="network6"/>
</xml>
Looking at my desktop settings I can’t find the new NAA as the input source
But my output source is ok
Do you need to use a Rpi4 running NAA for this matter instead?
FFT filter length affects load only if you have set the filter to “FFT”. Otherwise it doesn’t matter.
Convolution for example matters, so it could also make some difference between the two cases. I suspect there is some setting that is different that causes different behaviour between these two systems. Otherwise it is hard to imagine what could be the cause.
Not really, it just prints short help when run without arguments.
Yes, there is sort of such feature. But it is disabled at the moment because it is not implemented on HQPlayer Embedded. It is on my TODO-list, but it becomes rather more complicated for Embedded to implement. So not done yet.
No, you need to connect to the type-A connector on the Apple USB3 dongle. And then to type-B connector at the NAA side. That NAA you have there probably doesn’t have any device side (type-B) USB ports. Only host side ports (type-A).
For the iPhone/iPad source to work, it needs to be the USB host, and the NAA needs to be the USB device.
For RPi4 to work as input NAA, you’d use USB3 type-A to type-C cable, so it must have the blue type-A connector and be proper USB3 cable. And then in the NAA OS config.txt you need to switch the RPi4 type-C port mode from host to device (which is called “peripheral” there).