HQPlayer Linux Desktop and HQplayer embedded

[Sunny_Player]

3 minutes ago, Miska said:

T+A has not yet updated networkaudiod in their built-in NAA. This is totally normal, they may eventually update it. They are already aware of the new v5.

 

So there is currently no benefit for me in using NAA 5.0 as the t+a uses 4.1.1? 

[Miska]

5 minutes ago, Sunny_Player said:

So there is currently no benefit for me in using NAA 5.0 as the t+a uses 4.1.1? 

 

Yes, only the NAA that you use matters. If you are using the T+A built-in NAA (connecting over network), then that is the one being used.

 

[Sunny_Player]

3 minutes ago, Miska said:

 

Yes, only the NAA that you use matters. If you are using the T+A built-in NAA (connecting over network), then that is the one being used.

 

Thank you. Is T+A in a position to provide NAA 5.0 by way of a firmware upgrade? 

[Miska]

12 minutes ago, Sunny_Player said:

Is T+A in a position to provide NAA 5.0 by way of a firmware upgrade? 

 

Yes, that's the case. It is up to them to do it. Please give them some time, they will likely want to ensure that everything works as intended in their product.

 

[Markus8]

16 hours ago, bogi said:

General for PCM input. Regardless on digital transport method, once the PCM data enter DAC chip, the processing is the same.

Oh wow. I thought "Default" means 32-Bit and also remember @Miska saying for a T.I. 1792 DAC a setting of 24 Bit would be suggested? I just to PCM from input to output - if this makes a difference?

[bogi]

HQPlayer queries device capabilities and sets the default value accordingly. With delta sigma DACs you don't need to care about DAC bits, since there is no need for any restriction. Of course, you can also set an explicit value according to audio interface and DAC bit depth.

[Miska]

21 minutes ago, Markus8 said:

Oh wow. I thought "Default" means 32-Bit and also remember @Miska saying for a T.I. 1792 DAC a setting of 24 Bit would be suggested? I just to PCM from input to output - if this makes a difference?

 

Some chips can take 32-bit, some chips 24-bit. Older delta-sigma chips can handle only 24-bit.

 

If you have a DDC on your path and your output is S/PDIF or AES/EBU, these are always max 24-bit. So in these cases, set DAC Bits to 24. Or less, if your DAC uses less (there are many old 16, 18 and 20 bit DAC chips). Since these interfaces are unidirectional, it is not possible to detect what the other end supports.

 

USB interfaces are usually 32-bit for efficiency reasons, because doing 3-byte 24-bit formats on anything resembling a microprocessor is hugely inefficient. Drivers are usually also the same for same reason, because DMA transfers need to be at least 32-bit aligned.

 

If your output is on Linux, for example to Holo Audio, then even though the XMOS interface is 32-bit, HQPlayer can detect that the DAC supports at most 24-bit. On Windows with ASIO for example it cannot. But many DACs that have a 24-bit chip interface still use XMOS and don't report the correct resolution on Linux. So with these it is best to check what HQPlayer says it outputs.

 

PCM1792 is 24-bit part, and so is DSD1793 used by iFi. While the PCM1795 is 32-bit part.

 

[Gato]

21 minutes ago, Miska said:

 

Some chips can take 32-bit, some chips 24-bit. Older delta-sigma chips can handle only 24-bit.

 

If you have a DDC on your path and your output is S/PDIF or AES/EBU, these are always max 24-bit. So in these cases, set DAC Bits to 24. Or less, if your DAC uses less (there are many old 16, 18 and 20 bit DAC chips). Since these interfaces are unidirectional, it is not possible to detect what the other end supports.

 

USB interfaces are usually 32-bit for efficiency reasons, because doing 3-byte 24-bit formats on anything resembling a microprocessor is hugely inefficient. Drivers are usually also the same for same reason, because DMA transfers need to be at least 32-bit aligned.

 

If your output is on Linux, for example to Holo Audio, then even though the XMOS interface is 32-bit, HQPlayer can detect that the DAC supports at most 24-bit. On Windows with ASIO for example it cannot. But many DACs that have a 24-bit chip interface still use XMOS and don't report the correct resolution on Linux. So with these it is best to check what HQPlayer says it outputs.

 

PCM1792 is 24-bit part, and so is DSD1793 used by iFi. While the PCM1795 is 32-bit part.

 

So, for a T+A DAC 200 USB connected, the right setting for "DAC bits" is 0=default ?

[Miska]

58 minutes ago, Gato said:

So, for a T+A DAC 200 USB connected, the right setting for "DAC bits" is 0=default ?

 

Yes, it is 32-bit part since the PCM side (AFAIK) uses quad PCM1795.

 

[mikicasellas]

 

Hello ,

 

@Miska

 

Want to share my intentions and kindly ask All if you could throw your similar experience or possible suggestions , THANK YOU in advance !

 

Expecting my AppleMini M2 / 16 Gb / 8 cores / 10 GPU cores ,  to arrive any day now to replace my beloved old Mini -late 2012- .

 

Nowadays , I use the old one as the HQPD remote for my audio server, which consists in the following  :

 

SERVER :

- HDPLEX H5 Fanless Case

- ASUS ROG MAXIMUS HERO XIII Z590

- Intel i7-10700K

- TAIKO DC-ATX ( 24pin ATX to MoBo & 2 x 8pin to CPU )

- Apacer 2666 Industrial ( 8GB )

- Optane 58GB ( HQPOs -- ROON )

- Startech NIC PCIE card with Audio Note Cap replacing original

- JCAT XE USB PCIE ( POWERED BY SOLA 5V )

 

These are my -so far- choices of change . other choices are very Welcome

Adding a STREAMER ( +- 1500 - 2000 * ) selling TAIKO DC-ATX & JCAT XE USB PCIE

Adding a STREAMER ( +- 1500 - 2000 * ) selling JCAT XE USB PCIE

Replacing the actual server with MacMini M2 

 

Thanks to All !

 

 

[Miska]

27 minutes ago, mikicasellas said:

These are my -so far- choices of change . other choices are very Welcome

Adding a STREAMER ( +- 1500 - 2000 * ) selling TAIKO DC-ATX & JCAT XE USB PCIE

Adding a STREAMER ( +- 1500 - 2000 * ) selling JCAT XE USB PCIE

Replacing the actual server with MacMini M2 

 

Your current server is fairly powerful. So first question is what is your goal in terms of HQPlayer output formats and algorithms? Because that has a big impact on how much power you need.

 

Mac Mini with Apple silicon can do DSD256 output just fine with number of settings. Your current server can probably to DSD512 with quite many settings.

 

I don't have any experience with the Denafrips streamers, so I cannot comment much about those. But Holo Red works well.

 

[sledwards]

@Miska

 

I see you released 5.5.1 for Embedded, but I do not see the new version in the Jammy folder.

[Miska]

22 minutes ago, sledwards said:

@Miska

 

I see you released 5.5.1 for Embedded, but I do not see the new version in the Jammy folder.

 

Sometimes browsers cache the index, so if some update doesn't appear, please refresh the page on browser.

 

 

[hifi25nl]

I see that package name has changed. I guess that the "intel" package is using avx2?

Why "intel"?

[Miska]

1 minute ago, hifi25nl said:

I see that package name has changed. I guess that the "intel" package is using avx2?

Why "intel"?

 

The one that was "avx2" previously, now doesn't have any extra strings with the build number. It is the one that is most typically used on both Intel and AMD CPUs.

 

The one that previously didn't have any extra strings is now called "intel". The "intel" one works from SSE4.2 upwards, but the performance is not great on newer AMD CPUs. It has support for AVX-2 and AVX-512 as well, but AVX-512 doesn't always improve performance due to clock rate limiting in CPU.

 

[hifi25nl]

OK, thanks.

 

[jkelly]

Can I get a hand on updating hqplayerd to 5.5.1-14?

I am on raspi-lite bookworm. I am logged in as pi.

These are the commands I thought I could use:

 

systemctl stop hqplayerd.service
sudo dpkg -r hqplayerd
wget https://www.signalyst.eu/bins/hqplayerd/bookworm/hqplayerd_5.5.1-14_arm64.deb
sudo dpkg -i hqplayerd_5.5.1-14_arm64.deb

 

When I get to the dpkg -i I get an error message:

"adduser: Warning: The home dir /var/lib/hqplayer/home you specified already exists.

The system user `hqplayer' already exists. Exiting.

usermod: no changes"

 

Can you tell me next steps?

[dericchan1]

11 minutes ago, jkelly said:

Can I get a hand on updating hqplayerd to 5.5.1-14?

I am on raspi-lite bookworm. I am logged in as pi.

These are the commands I thought I could use:

 

systemctl stop hqplayerd.service
sudo dpkg -r hqplayerd
wget https://www.signalyst.eu/bins/hqplayerd/bookworm/hqplayerd_5.5.1-14_arm64.deb
sudo dpkg -i hqplayerd_5.5.1-14_arm64.deb

 

When I get to the dpkg -i I get an error message:

"adduser: Warning: The home dir /var/lib/hqplayer/home you specified already exists.

The system user `hqplayer' already exists. Exiting.

usermod: no changes"

 

Can you tell me next steps?

Perhaps you can simply purge hqplayerd and reinstall?

 

sudo apt —purge remove hqplayerd 

[cpcat]

45 minutes ago, jkelly said:

Can I get a hand on updating hqplayerd to 5.5.1-14?

I am on raspi-lite bookworm. I am logged in as pi.

These are the commands I thought I could use:

 

systemctl stop hqplayerd.service
sudo dpkg -r hqplayerd
wget https://www.signalyst.eu/bins/hqplayerd/bookworm/hqplayerd_5.5.1-14_arm64.deb
sudo dpkg -i hqplayerd_5.5.1-14_arm64.deb

 

When I get to the dpkg -i I get an error message:

"adduser: Warning: The home dir /var/lib/hqplayer/home you specified already exists.

The system user `hqplayer' already exists. Exiting.

usermod: no changes"

 

Can you tell me next steps?

I always get that message when I update.

Go to the web UI under “about “ tab and see if you are on the latest version.  You should probably systemctl restart hqplayerd first, since you stopped it.

[mikicasellas]

15 hours ago, Miska said:

Your current server is fairly powerful. So first question is what is your goal in terms of HQPlayer output formats and algorithms? Because that has a big impact on how much power you need.

Hi Miska, thank you !

 

I guess because my Audio Server is passive cooled it only goes until DSD256 with limited filters and cause I don't have a way to measure temperature , so for now im using PCM....Do you think i10-10700k will be powerful than the MM M2 ?

15 hours ago, Miska said:

Your current server can probably to DSD512 with quite many settings.

No can do

 

...

[bogi]

2 hours ago, Miska said:

 

The one that was "avx2" previously, now doesn't have any extra strings with the build number. It is the one that is most typically used on both Intel and AMD CPUs.

 

The one that previously didn't have any extra strings is now called "intel". The "intel" one works from SSE4.2 upwards, but the performance is not great on newer AMD CPUs. It has support for AVX-2 and AVX-512 as well, but AVX-512 doesn't always improve performance due to clock rate limiting in CPU.

 

 

I see no such distinction for HQPlayer Desktop. I hope AVX512 will continue to be supported on Desktop platform.

[Outlaw]

With the latest Jammy intel build is there any benefits for a older CPU like my 8086K or is it more intended for newer Cpu.Thanks.

[AudioDoctor]

@Miska on the page for the new Embedded 5.5.1 it says this, did you really put ROCM support back in?

 

 

[Miska]

8 hours ago, jkelly said:

Can I get a hand on updating hqplayerd to 5.5.1-14?

I am on raspi-lite bookworm. I am logged in as pi.

These are the commands I thought I could use:

 

systemctl stop hqplayerd.service
sudo dpkg -r hqplayerd
wget https://www.signalyst.eu/bins/hqplayerd/bookworm/hqplayerd_5.5.1-14_arm64.deb
sudo dpkg -i hqplayerd_5.5.1-14_arm64.deb

 

When I get to the dpkg -i I get an error message:

"adduser: Warning: The home dir /var/lib/hqplayer/home you specified already exists.

The system user `hqplayer' already exists. Exiting.

usermod: no changes"

 

Can you tell me next steps?

 

You are fine at that point, just restart the service with "sudo systemctl restart hqplayerd" and you are done.

 

[Miska]

3 hours ago, AudioDoctor said:

@Miska on the page for the new Embedded 5.5.1 it says this, did you really put ROCM support back in?

 

 

Ahh, no, it has been forgotten there. I'll ask Aapo to remove it. Thank you for the heads up!