HQplayer embedded on raspberry pi 4

Yes, it’s running on RPi4. I mainly want to switch down the road since it’s limited to 512.

The dropouts are very random. Sometimes there is one like 10 seconds into every song. Other times there’s one every few songs or just rarely. I’m using a wifi extender with a LAN port because my main network is pretty busy (smart lights, alexa’s, sonos, etc). Last time I checked the CPU is at like 18% with CUDA offload on Windows 11 Ultra Performance Mode. It does not make a difference if the Computer is connected by wifi or ethernet

So your HQPlayer is running on Windows, not on RPi4?

The topic is about running HQPlayer on RPi4, not just a NAA…

If you are using a wifi extender for your Rpi4 Naa, maybe try removing that and have the Pi4 wired to your lan switch which hopefully your Windows Hqplayer computer is wired to as well.

1 Like

Sorry I got off way off topic about RPi NAA

As a NAA, RPi4 can manage up to DSD1024 on wired ethernet. As long as 802.3x Flow Control is correctly active on the network.

Ok, I’ll have to find out if it’s enabled by default on Xfinity Gatway.

Hi All
I can see my HQPlayer embedded (pi4) on the network and have the IP address can not open on a browser

Does anyone know what my next step would be ?

Thanks Jussii, most useful.
I think I will wait for the RPi5 due out latter this month. At this time there is of course no imdeded image availble from Syng. Maybe latter this year.
Given that I am already doing some convolution folters in Room, then I can see a user case for the extra memory.

Doesn’t work http://ip-address:8088 ?

No that does not work

I can connect with HQPDcontrol V4 do not know how to use this to set up HQplayer on the network

What if you try with another browser … Chrome, Firefox ?

Usually “http://hqplayer.local:8088/” should work. Some browsers complain that it is insecure since there’s no TLS (https). And some try to blindly switch to “https” instead which will fail.

But usually you need to specifically prefix with “http://”, otherwise all modern browsers will assume “https://” instead.

ok if this is not working is there anything I can do?

HQPDcontrol connects

I can view Roon Optimized Core and Ropieee

You have some other OS than HQPlayer OS on your Pi4? If so, and you are not using my original package either (Debian), it could have a different port or setup for the web interface.

I know nothing about Ropieee, is that your OS?

Can you describe your setup?
Where are running on:

  • Roon
  • RoPieee (rpi4)
  • HQPlayer embedded (rpi4, another one, different from Ropiee)

RoPieee can run NAA only … there is no way to run HQPe and RoPieee on the same rpi

Roon Rock on NUC

Ropieee on Pi3 and pi4

HQplayer on Pi 4 8gb

NAS Drive