Using any audio source with HQPlayer - Spotify, Amazon, Apple Music, YouTube Music, Deezer, Soundcloud [2023]

Yes, that’s the case!

Rate changes are detected and adapted to, on the fly.

It is roughly as simple as it can be right now. Reason for the need to edit config.txt is that Holo Red and this RPi4 USB input cases need different configuration of the RPi4’s USB controller.

Once you have written the NAA OS image on microSD card, before booting it up, edit the config.txt on the boot partition. You can do this for example with Notepad on Windows. It is just a simple text file to edit.

There needs to be a comment marker ‘#’ at the beginning of either line depending on the use case. Having the line prefixed by ‘#’ makes the boot loader ignore it.

I believe editing the file is as simple as offering another copy of it.

No, not at least yet. On HQPlayer Desktop it is as simple as selecting the input from the list. But since Embedded supports having unlimited number of alternative inputs, local and remote, it is not that simple.

For this case, the specific values there depend on your system, since each NAA needs to have a unique name.

But at simplest you add something like:

<input address="naa-xxxxxxxx" device="USB Audio (RPi4)" ipv6="1" name="My RPi4 UAC" samplerate="0" type="network6"/>

I’m happy to report that with latest HQPlayer Desktop v5 on macOS, automatic input rate switching also works through BlackHole, for example with Qobuz client!

Tidal client seems to be equally broken in this respect on both Windows and macOS.

6 Likes

…my nerves - I’ve been trying for hours to make my NAA recognizable for the streamer - no chance.
I have added these lines to the Hqplayerd.xml.

<input address="naa-xxxxxxxx" device="USB Audio (RPi4)" ipv6="1" name="My RPi4 UAC" samplerate="0" type="network6"/>



I made these changes in the config.txt of the NAA.

The web interface recognizes the “new DAC” - but the streamer does not. My Windows laptop could not do anything with the USB input either: “Unknown application”.

What am I doing wrong? I’m sure it’s just a small thing…

Best regards
HH

For sure there is a typo: in the first screenshot should be “address” and not “adress”

Have you connected your audio chain as the following:

  1. streamer (USB output)
  2. (USB hub) TP-Link [streamer to TP-Link is connected with the cable provided by TP-Link hub]
  3. (USB C input) NAA (RPi 4) [output is ethernet cable to network switch]
  4. HQPlayer embedded
  5. Same NAA RPi4 as in step 3 as output to your DAC

Also you should check hqplayer embedded log tab (in the web interface) to see whether hqplayer has connected to your NAA.

note: The web interface shows the “new DAC” doesn’t mean hqplayer recognizes your NAA.

…back from the easter family vacation. And many thanks to Stefano for the tip. And yes, Hao-Lai, that’s exactly how I had did my setup. I think my mistake was much more trivial: I had forgotten to click the “Select” button on the input page of the web interface. :frowning:
Curious: The message “failed to connect” appeares - nevertheless “USB Audio gadjet” appeares on my DAC.
And it really works great! Even if it always jerks during auto rate switching for the first few bars - no matter… The streamer always runs the most of the time the redbook format anyway.

So it worked - and I’m very satisfied. Now I can control all my beloved radio stations, my CDs, my music files on the internal hard disk, on the NAS, roon and the Qobuz streaming via the streamer and the great Hqplayer.
Now I will make final comparisons with Qobuz streaming with Streamer, Roon and BubbleUPnP (so far the best performance with Hqplayer).
But now I can concentrate on the other tuning measures, such as cables and power supply.

Many thanks…
Best regards
HH

3 Likes

Does this thing work under Linux? I did not see any mention on product page…

Sorry for my ignorance, just wondering is there anyway to feed music from Foobar to HQPlayer? Thanks.

Yes, there is:

I don’t think however it knows how to stream DSD

There’s another plugin from 2013, rather clumzy…

No, there’s no Linux driver. It works with full proper automatic rate switching only on macOS so far (they have not yet fixed the Windows ASIO driver).

OTOH, on macOS automatic rate switching also works straight through the BlackHole loopback driver. So not sure how necessary this device is, unless one wants to use external sources with HQPlayer. And there it is quite nice since it has four optical inputs.

1 Like

Weirdly, I’m struggling to tame seemingly “simple” set up with Input / Output NAA

  1. NAA: RPi4 - in config set as peripheral
  2. HQP Embedded, addedd the following to the config:

<input name="USB Audio (RPi4)" device="hw:CARD=UAC2Gadget,DEV=0" samplerate="0" channels="2" format="auto" pack_sdm="1" period_time="100" sync_element="Capture Rate" sync_hctl="1" script="sudo hqplayer-start-uac-gadget.sh 'fe980000.usb'"/>

Now I am trying to connect to this NAA the following chain (which works perfectly when connected to HQP server directly): Blusound Node streamer → Toslink → miniDSP USBStreamer box → “USB B - USB C cable” → USB-C hub → USB C input - RPi4.

Selecting either RPi4 or USBStreamer 44/16 in drop down input menu, and clicking “Select” does not seem to pick up any stream.

I wonder where the possible break in the “line” can be?

This is pointing to a local RPi4 USB interface within the HQPlayer Embedded machine. Not to the remote NAA endpoint. So this is where it is going wrong. Instead it should be something like:

<input address="naa-xxxxxxxx" device="USB Audio (RPi4)" ipv6="1" name="My RPi4 UAC" samplerate="0" type="network6"/>
1 Like

A-ha! Many thanks, will try now.

Will I need to update NAA address every time ? If I recon correctly HQP see it under different time everytime I powercycle RPi4 ?

NAA address depends on the NAA hardware. It is not IP based, instead IP address can change as long as the NAA name remains the same. The auto-generated NAA name is kind of “hardware fingerprint” type, so it shouldn’t easily get changed for a particular piece of hardware.

So no, powercycling RPi4 won’t affect it. Nor software updates.

2 Likes

Mutec just released a new MC1.2+ and not sure it supports the auto sampling change?

Unless they specifically say that it does support, I would very much assume it doesn’t. The earlier one I have doesn’t - it runs everything through ASRC…

Two months later… small dream is a reality and I have my CD’s spinned via HQPlayer with all its fat bells and whistles.

I have put together a small write-up on how I have connected my CD Transport to HQPlayer Embedded server using the “input NAA” features. I insert the link here in case someone comes around this topic (most likely so) with the similar question…

(How to) IgorSki spins CDs (connects CD Transport) through HQPlayer Embedded - Audio Gear Talk / HQ Player - Roon Labs Community

4 Likes

Can automatic rate switching be achieved when running Spotify or Amazon Music on Mac OS using Black Hole?
(If Spotify were to offer lossless audio in the future…

If it can do automatic rate switching, I’m really looking forward to the Mac mini M4 at the end of the year. Hopefully, it can handle DSD512.

Spotify now (and future lossless is rumoured to be) 44.1kHz , so no auto sample rate switching required

Amazon Music app, you can try and connect your DAC to your Mac and you can see your DAC incoming sample rate will not change. Try it

Have you tried if Amazon Music gives out any hires from iOS?