@nquery USB dongle is supposed to isolate the components of each machine. The way I learned, it does not matter what cards or adaptors you have in each machine that you move USB dongle to. Or maybe I am wrong.
1 Like
Thatās right, in other words using the usb dongle the computer fingerprint is ignored and the usb dongle key is used
2 Likes
Oh you are using a dongle. Maybe itās not the key per se but HQPOS is not recognizing the USB port and/or dongle itself. If you put the dongle in after HQPOS has booted up do you see a system message recognizing the device?
USB key is automatic and does not write anything in the log. I just upgraded my old machine to 5.7 removed the key added the license and it is all there. Removed the key and automatically detected, without any trace in the log. I guess bootable image is missing USB dongle support. Anyone here is using HQPlayer bootable image with USB dongle?
UPDATE: I removed 5.7 bootable image and installed ubuntu 22.04, USB key works now. unless @jussi_laako says otherwise, HQP bootable image does not support USB dongle
Iāve gave up on the pi 5 5.7.0 for now and went to pi 4 5.7.0 and it does work for Roon but not usb hard drive. Still doesnāt see content nor can I scan the drive. Went back to 5.6.3 and everything is working.
Yes the HQPlayer OS image supports dongle as well. But if you have the white-red dongle model, then it can operate in two modes. HID (default) or raw USB mode. On Ubuntu and Fedora, that dongle model is supported in HID mode. On HQPlayer OS and Debian that dongle is supported in USB mode. This mode can be switched with a Windows utility.
Reason for this mess is that the dongle manufacturer unfortunately doesnāt (yet) support the dongle in HID mode on arm64 platforms (RPi). Likewise, they donāt support USB mode on macOS, only HID mode. And on Windows USB mode requires installing a driver. Of course they failed to document this too, causing me some grey hairs. So the platforms where both x64 and arm64 are supported, the dongle is used in USB mode. And on platforms where only x64 is supported, the dongle is used in HID mode.
Thereās another dongle model (plain black) which doesnāt have this restriction, but it is slower (and doesnāt work on macOS).
The order form now asks for the desired platforms, so we can ship something that is best fit for the give use case.
Windows / macOS support doesnāt matter as much right now. But Iād like to support everything equally to avoid future restrictions / limitations.
1 Like
Sold my 4060ti and upgraded to 4070 Super.
Itās a huge improvement.
Can do Super 512+fs light + DAC Correction!
The transients are so good, more punch 
Can do also (without DAC correction)
1x/Nx Sinc-M ASDMECv7-ul DSD 1024x48
Iām staying here for long run! Itās the best performance for my ITX, plus got a bigger 850w PSU as recommended by Jussi
Now more time listening than upgrading 
3 Likes
isnt it amazing @Moy how much can be squeezed out of a āsmallā box. Iām happy we managed to convince you not to go with external GPU some time ago. 
happy listening.
1 Like
Many thanks also to @nquery that helped me understand that my cpu needed more power to use its full capacity, then I migrated my i9 and learned that Deskmeet case was not optimized to keep cool. Got the Sugo 16 case and upgraded a better Noctua tower fan then a faster GPU! I highly recommend the msi brand, works great and itās reasonably quiet 
4 Likes
Really intriguing setup 
Any chance you could share a list of all the parts you used? Looking at the assembled unit, it looks quite a project with all those snaking cables and stacked fansā¦
1 Like
Surely!
Case Sugo 16
Motherboard (Any ITX)
CPU Cooler Noctua NH-U12S
Extra fan for Noctua NH-U12S
Extra fan for back panel
PSU (SFX type- 850w for 4070 super)
PSU Bracket (to place it sideways allowing a better Noctua Cooler tower with 2 fans to fit)
GPU 4070 Super MSI (quiet)
Tips
Ensemble fans and PSU power cables on motherboard before mounting it on case.
Connect PSU bracket first then connect cables, then screw bracket sideways and make sure is all the way back.
Note make sure to have soft and flexible PSU cables as they need to get a bit squishy.
Iām using a i9000 4th cpu core and the fastest memory it can handle 3200 on my case.
Fast SSD and have dual boot to test Windows Desktop HQplayer and Ubuntu embedded HQplayer. But now usually stay at Ubuntu and windows for gaming (second GPU purpose)
2 Likes
@jussi_laako
What happened to the 20kHz filter on embedded 5.7.0?
You can still manage it through HQPlayer Client or HQPDControl V4
1 Like
Nothing? What do you mean? No changes on that front.
I couldnāt find it on the web browser configuration page.
But now I understand how to use it.
Just an updateā¦ I acquired a 3090 so I popped a SSD into my system and moved from embedded OS to Debian. A fairly seamless transition. So far the 3090 is just killing it. The whole system just seems bored now.
One thing I did find outā¦ Nvidia hates RT kernels. Oh my goshā¦ what a pain. I gave up after trying a couple workarounds. I use NAA so just not worth the time to try and get this working.
Is there a benefit to using the HQPlayer kernel? Iām unable to find docs on how to get that going with the 3090.
Yes, thatās the case. And when using NAA for output it doesnāt matter at allā¦
My Debian kernel builds are pretty outdated at the moment. Only Ubuntu kernels are up to date. But in either case it works by just installing my custom kernel. DKMS automatically takes care of the Nvidia driver modules. So it is very straightforward and seamless. But your main benefit from my custom kernels is when you use locally connected DAC. And you are using a NAA. So for maximum benefits, you could use NAA OS or my custom kernel on your NAA side.
When you use NAA for output, HQPlayer server is just a data processor - so all focus should be on computing performance - audio / realtime performance is up to the NAA endpoint. (of course HQPlayer server is also realtime processing, but it is not nearly as latency critical as the actual hardware output side)
1 Like
Yup, already do this on a Pi 4. Might switch to a Red.
Ubuntu Server 22.04 Pro 5.15 realtime kernel works fine with official nVidia driver 550 for linux. 
My 7950 server has multiple configurations (including Jussiās low-latency 6.6 kernel) for finding the best combo for HQPe. So far I stay with Ubuntu Proās 5.15 RT kernel with some latency-reduction boot parameters. Very smooth, not that bright, not that sharp, can listen as high as ~80dBC whole day long without fatigue.
1 Like
$ uname -r
6.1.0-23-amd64
$ nvidia-smi
Sun Aug 18 17:26:52 2024
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 560.28.03 Driver Version: 560.28.03 CUDA Version: 12.6 |
|-----------------------------------------+------------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+========================+======================|
| 0 NVIDIA GeForce RTX 3090 On | 00000000:01:00.0 Off | N/A |
| 0% 32C P8 21W / 420W | 400MiB / 24576MiB | 0% Default |
| | | N/A |
+-----------------------------------------+------------------------+----------------------+
+-----------------------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=========================================================================================|
| 0 N/A N/A 976 C /usr/bin/hqplayerd 390MiB |
+-----------------------------------------------------------------------------------------+
Not sure the newer versions provide any benefit but this is what I was fighting and realized there is no benefit to me.