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

That refers to Intel Bay Trail audio interface.

Yes, this is normal. It is part of the onboard audio.

These are included in the default networkaudiod configuration.

If you changed the configuration file, did you remember to restart the networkaudiod service?

Edit: OK, I think I know what is the issue. I’ll make an updated build for the networkaudiod package.

1 Like

Now there are updated networkaudiod packages. Please download and install over the earlier one, then restart networkaudiod.

1 Like

I’m now testing next generation UP for the same purpose, with x7-E3950 that can also do more processing in-box with HQPlayer embedded (if necessary):

P.S. While listening Saturday night music:

2 Likes

I mean imo there is a gap in the market. if someone can make a hqplayer “m scaler” . That sh1t would be huge.

Technically making such is not a problem. Then next question is how much processing power it should have. That’s not so straightforward, because HQPlayer can scale to various different scenarios. From very simple and light things to very complex and heavy ones. So from that perspective much more flexible and scaleable than M Scaler.

But another way to look at it is that there are various NAA output devices on the market. But no NAA input device products. The UP devices and RPi4 discussed here are the closest ones, and actually rather easy to take into use.

1 Like

Same issue new build

Same error

I even removed networkaudiod to install fresh with same error

Hi @Chunhao_Lee , have you tried this on your Up Gateway ?

Well… in the past 2 weeks I was fully immersed in Atmos and Auro-3D music :sweat_smile:
I’ll do the regression test for new NAA OS on Up board next week. :wink:

1 Like

OK, another attempt to fix the package such way that it is easy to get going. Can you please try again with the new attempt? Please also reboot after installing the package.

Since I have only one UP-Board available where to test and it is not “clean install”, but instead has been development platform, it is not easy to ensure it works also on a pristine system.

1 Like

Ok got it working! Since you had success with Win10 source I started with Qobuz Destop app and chose Exclusive Mode for ‘Playback inactive’.

Unfortunately still have the static issue with my Qobuz playlist which alternates sample rate each track.

If you play 5 seconds of each track and then skip to next, can you get through the first ~30 tracks without issues?

Playlist here: Open Qobuz

Here is networkaudiod log. Left is 44.1k to 48k pass (no issue) and right is 44.1k to 48k fail (static). So unfortunately nothing in the naa logs to show issue.

I was using HQPlayer with my test playlist from Windows 10, since I didn’t have any other exclusive mode playback software installed. At the other end HQPlayer Desktop on Ubuntu playing to DSD512 output.

Noted but were you playing tracks that changed sample rate each track?

To kind of magnify the issue

I have two Upboard Gateways on completely different systems in different locations and both have same issue.

Yes, that’s what I did.

I found one issue on NAA backend when you ask it to start for example at 44100 and source is initially at 96000, then it ends up playing at wrong speed. It should work setting sampling rate to 0. But it doesn’t now, I’m fixing this.

1 Like

Let me know when this is updated and I’ll test it out.

Can you also share both your uac2 input lines - for both UP networkaudiod and also your server hqplayerd.xml

Just in case this is contributing to my issue.

I’ll copy your lines and retest

I’ve now managed to go through your playlist without issues. I’ve uploaded networkaudiod 4.3.0 that contains fair amount of changes. I have also made changes to NAA backend on HQPlayer, so you may need to wait for next release. But you can already try with the new networkaudiod if it works. Primarily I wanted to get it working with “audio:default/0” URI which didn’t work without changes to HQPlayer.

I’ve tested with HQPlayer Desktop, just selected the NAA UAC2 as input device. This is the resulting line from settings.xml:

<input address="upboard" channel_offset="0" device="USB Audio Class 2" format="auto" ipv6="1" pack_sdm="0" period_time="0" samplerate="0" short_buffer="0" type="network6"/>
1 Like

So default/0 works but hqplayerd log shows:

Audio transport: rate=0 channels=2 format=pcm buffer=0 (normal)
NAA input requested rate 0 not available using 768000 instead
NAA input set sampling rate: 768000 (768000)

But the auto rate changing actually works fine - so that’s good.

I think I was the one that discovered you have to set sample rate to 44100 in Embedded (matching how it works with Desktop) so this is a milestone ! :smiley:

However I still get the static.

When the static issue comes, for the first brief moment (maybe under half a second) I hear the track playing perfectly fine and then the volume goes really quiet + then I hear the track playing quietly with the FM radio type static

But the interesting part is it briefly plays fine which makes me think the track is feeding correctly into hqplayer.

But if you can’t reproduce it then there’s nothing else that can be done until we wait for someone else to try

@Chunhao_Lee reproduced my issue previously so maybe he can retry later if he has spare time or someone else can.

Maybe your development system has something different to mine (like how networkaudiod was failing to work for me for a few builds but was working fine for you). So we need someone else to try.

I don’t get static, but just garbled output with quiet music. Easiest way to reproduce with Qobuz player was to switch output devices while playback was proceeding. For some reason the problem appeared more if I started Qobuz playback with output going to some other device and then on the fly switched to HQPlayer. While if I start HQPlayer input by hitting play in Qobuz application it didn’t happen. I found out this accidentally, because restarting NAA makes the USB device disappear and Qobuz automatically switches to some other output device. And then I just switched back when I got NAA restarted.

But now with some changes things work. But please try again with next HQPlayer release. As I made some changes to the NAA backend as well.

I used fixed 44.1x512 output rate, since the E30 I used for testing doesn’t work correctly with 48x512. Also less unnecessary stop-start hassle for the DAC and thus faster rate switches.

This is also something I fixed on HQPlayer and NAA.

1 Like

This is it!

It’s kind of like on old FM radio when u didnt get correct frequency, you hear music and static/noise

Will do

I set output to fixed rate also for this reason

I just picked up the POE+HAT and using with RPi4.

I like it !

I adjusted dtparam for fan setting1 to start at 45 deg C and setting2 to start at 62deg C.

Streaming 2 channel DSD512 for a couple hours, temperature stays mid 50’s so fan is running at it’s lowest speed and not audible unless ear is close.

Nice to have just a Cat 6 cable running to Pi4 and DSD512 coming out the other side via USB

I’m using DietPi atm - haven’t tried NAA OS

Did you get a case for yours @Chunhao_Lee ? Mine is currently like yours in the photo - ‘open’ :grin:

dtparam=i2c_arm=on
dtparam=poe_fan_temp0=45000
dtparam=poe_fan_temp1=62000
dtparam=poe_fan_temp2=70000
dtparam=poe_fan_temp3=80000
2 Likes

It’s a bit difficult to find the suitable one…

1 Like