I understood but as HQPlayer has a Roon interface I‘m interested how it works. Just for curiosity and you are right, a bit off topic here 
Best DrCWO
1 Like
Just a physical remote, no different to the IR ones you bought and will test. Great for controlling HQPlayer volume, when feeding Apple Music Hires etc into HQPlayer.
My main interest to have a wireless remote connected to NAA OS, not to HQPlayer server (in another room).
However I just learned Microsoft Surface Dial is using bluetooth, not ideal for NAA OS.
@DrCWO is now working on supporting this wireless remote, which supports Linux driver and comes with USB dongle (not Bluetooth):
Programmable keys could be cool for play/pause/stop but I’m more interested in the dial for volume control
2 Likes
I see people asking on AS Forum about a dock to power RPi5.
I have no idea if this will work since I don’t have RPi5, but here is Amazon link for the dock I am using with 5V x 1.5A outputs (both Type A and Type C output)
The “15 IN 1” model.
https://www.amazon.com/dp/B0BJP77NFJ?ref=ppx_yo2ov_dt_b_product_details&th=1
1 Like
If you want to control HQPlayer using this protocol, it is open with reference source code available from my website.
So far, I’ve tested couple of remotes with Client running on Windows 11 on Microsoft Surface tablet, and those seem to be working fine.
Would you please be so kind to drop me the link.
After a quick search I did not find it 
Best DrCWO
At the end of the page here:
If you need further information, just drop me an email!
1 Like
I’m sure there’s a long list of remotes working with Win 11 tablets - including Microsoft Surface Dial. Should be easy to get working.
But NAA OS is the solution we need one day ! 
something plug and play
The same should work also on Linux running HQPlayer Client or HQPlayer Desktop… Since these remotes are regular HID devices, like a keyboards and mice.
NAA is not HQPlayer controller, it is audio endpoint (and I’m not planning to change that)… You control HQPlayer for example with HQPlayer Client…
Volume control, play/pause/etc/ all working via hqp5-control. Now off to tie a few favourite Filter/Dither combos to their own little buttons… 
1 Like
Disappointing , the Client solution breaks the headless experience, which is the best HQP experience, if required for volume control.
But anyway I loaded Ubuntu Desktop on my Pi4 to try it
I can get Client to autostart, without any UI interaction
Client is running in the foreground automatically after boot.
But my keyboard volume up and volume down, just changes the Pi’s volume, not Client app.
Any tips ?
Why do you say that?using Client on iPad do give the headless experience, isn’t it
We already discussed this months ago.
To adjust volume quickly, that is not a fast experience. If iPad is locked, you need to unlock, hope the app is open, if not open it
Too much latency.
I am looking for a remote experience that is fast like a remote control should be for volume…
Otherwise it is a poor user experience for something critical like volume…
Anyway I’m sure I am close with my Pi4 + Client autostart working - just need a tip from Jussi how a keyboard can adjust the volume. Before I buy a USB IR remote to further test.
@RBM has a couple things working nicely but a bit of tweaking involved. But I won’t rule it out.
1 Like
You need some way to control HQPlayer anyway? To do all the playback etc?
Your desktop environment may be stealing those keypresses. But you can also try to use alternative button presses. Up/down buttons for example adjust volume too. Left/right buttons switch tracks. Please see the manual for list.
Starting HQPlayer OS is from web browser on tablet and that is all
Starting HQPlayer can be a one-off during listening
Volume changes can happen every 3 minutes in a listening session. iPad could have screen locked and web browser or app closed when you need to change volume.
Two very different practicalities
Yes I tired and created custom key combos which still just change Pi volume
If I get USB IR i can’t really expect anything different if keyboard can’t work, so doesn’t seem to be a working solution
This is stock Ubuntu Desktop Jammy 22.04 LTS on Pi4
I wonder how such can be recognized by something else than HQPlayer Client as volume changes, since those key presses like arrow up are not related to volume changes by default.
I just tested one USB HID RF remote on my Linux Mint Cinnamon laptop, and unassigning the media keys (from keyboard settings) to the OS hooks makes those work directly with HQPlayer. Cinnamon desktop also allows me to assign those keys to commands, so I can very easily make it call hqp5-control to perform those commands as well. So two different ways.
So you can make these things works even without having Client running, as long as you are logged into the desktop.
Hello, community,
I would like to run my streamer via HQpLayer. My setup: HQPlayer embedded 5.5.0 and a NAA 5.0.0 via RPi4.
I have now bought the T-Link USB 3.0 7-port hub and a decent USB Type-C 3.0 cable (a data and charging cable).
I connected the streamer to the T-Link via its USB out. I connected the NAA (via the USB-C) input via the 3.0 USB output of the T-Link - the NAA runs as Jussi had already described.
But unfortunately the streamer does not recognize its new DAC.
I have now gone through all the variants via the web interface input - I have also set the streamer’s digital output fix to 48khz. Unfortunately, it’s no use - the new DAC (“NAA” or “HQPlayer”) is not recognized by the streamer.
What else is missing in the setup - what am I doing wrong? Does this setup work at all?
Do I have to add anything to the Config.txt of the NAA 5.0.0?
Best regards
HH
Yes, you need to edit two last lines of config.txt on NAA OS image. Comment out the dwc2 host mode line, and uncomment the peripheral mode line.
Your streamer should be connected to host side of the USB hub and RPi4 to one of the blue device side ports (yellow ones don’t pass data).
Have you added this input NAA as input line to your hqplayerd.xml? When you select this newly added input item from /input page of HQPlayer Embedded web interface, it should appear as a DAC on your streamer.
Hello, Jussi,
thank you very much for the information. If this works, it will be the killer application for HQPlayer. This would mean that all devices in the streamer (radio, possibly CD player, Qobuz streaming, Roon and playing music files from hard disk and NAS server) can be played via the great HQPlayer - with control via the streamer. Is that correct?
How does the automatic rate switching work in my/this setup?
Will you include this feature in one of your upcoming updates with simple clicks? Then I would wait… If not, what would be the exact steps for a Linux idiot like me: Is there a step by step guide for changing the config.txt of the NAA? I think that would also help a lot of audiophiles out there who love HQPlayer but can’t get along with Linux.
Are these general or specific settings? Can you provide a config.txt that can be easily swapped? Does something like that work?
Same question about adding the NAA as an input line to hqplayerd.xml. Is there a step by step guide for this as well? Are these general or specific settings?
Maybe someone has some ideas or links where this theme has already been covered? I would be pleased…
Best regards
HH