Please try to restart your Roon Server by closing the Roon app in the taskbar or rebooting your Roon Server machine.
· No, the issue remains the same
Please try to restart your network setup by unplugging, waiting 30 seconds and then replugging in your networking gear.
· No, the issue remains the same
Please select how you've connected your Roon Server to the internet
· Roon Server is connected by *Ethernet*
Have you checked your firewall settings to ensure that Roon is allowed through?
· Roon still won't connect even after checking this aspect
Have you verified that Roon Server is on the same subnet as your Remotes?
· My Remotes and Server are on the same subnet and I still can't connect
Sometimes the issues can be resolved with a reinstall of your Roon Remote app. Let's try to perform a reinstall and see if it helps.
· I've reinstalled the Roon Remote but it did not help
What is the operating system of your Roon Server host machine?
· *Linux Server* (Ubuntu, Fedora, ArcLinux...)
Select any of the following components that are present in your local network setup
· None of the above
Describe the issue
How do i use HQPlayer via Roon? AudioLinux on server machine and endpoint; 'windows' on controller laptop. Roon server & Roon Bridge 'active' as embedded devices. HQPlayer embedded NOT active and not installed on laptop controller yet (only downloaded), please ask for any info you would also like before any instructions can be given? Many Thanks!
Describe your network setup
How do i use HQPlayer via Roon? AudioLinux on server machine and endpoint; 'windows' on controller laptop. Roon server & Roon Bridge 'active' as embedded devices. HQPlayer embedded NOT active and not installed on laptop controller yet (only downloaded), please ask for any info you would also like before any instructions can be given? Many Thanks!
Here are the official instructions how to setup HQPlayer in Roon:
Roon Bridge is not relevant for this setup. Once Roon sends audio to HQPlayer, it is in HQPlayer’s domain and not related to Roon anymore. So the audio output is owned by HQPlayer and configured in HQPlayer.
This: “Roon Bridge is not relevant for this setup. Once Roon sends audio to HQPlayer, it is in HQPlayer’s domain and not related to Roon anymore. So the audio output is owned by HQPlayer and configured in HQPlayer” …should be in the official instructions! It is a vital bit of info. that is of great importance may stop HQPlayer from working if anyone does not somehow realise this (by magic)?
Steps 2/3 are only one small part of a bigger picture and even the ‘notes’ don’t explain everything properly!
Also:
Do i need the full HQPlayer install or just the client (without server part) on windows laptop controller?
Disable roon bridge in audiolinux & roon?
Activate HQPlayer NAA in audiolinux?
Do I keep ROON SERVER activated in Audiolinux OR swap this for HQPlayer user/root?
Do i need to press down the “Allow network control” button in HQPlayer toolbar? And does the client have this facility or is it necessary to install full package (client/server) on windows laptop controller?
What’s the full story as the official ROON instructions don’t appear to embellish these kind of issues in any great detail?
Just so that I don’t end up trying every conceivable connotation!
Thank you!
Roon Bridge and NAA are the respective software for Roon and HQP network endpoints. You do not need either of them unless you are sending an output over Ethernet or WiFi to an endpoint. If your DAC or streamer is directly connected to the server by USB (for example) then you do not need either Roon Bridge or NAA. If you are using HQP to send audio to an endpoint then you don’t use Roon Bridge, just NAA.
Client only.
Select the HQPlayer zone from Roon/Settings/Audio which is created on setup.
Run NAA in the endpoint, either as a separate program or using one of the bootable images. See the Signalyst site for NAA downloads at https://signalystcom/bins/naa/
Swap Roon Bridge on any network endpoint for NAA. Server should be running both Roon Server and full HQPlayer (if running both on the same machine).
Yes, on HQPlayer Desktop.
I don’t think client has it. You don’t need to install the full program on the controller, just the client.
I do have an endpoint as well!
Both server and endpoint have audiolinux O/S (Ver.3)
Piero (‘AL’ owner/developer) says that I can’t have BOTH ROON server & HQPlayer desktop server (embedded) running at the same time, must be one or the other? This would lead to conflicts?
My system is 3 machines:
windows laptop controller
ROON server on ‘AL’
Endpoint (ROON Bridge) on ‘AL’
and …this is working!
Now want to try HQPlayer with ROON?
NOTE: there is NO interface for HQPlayer desktop (server) embedded in ‘AL’ as far as I am aware? So, there won’t be an "Allow network control” button!
This is incorrect. It is quite common to run both Roon and HQP on the one server. I’ve been running Roon Server and HQP Embedded on the same server for years. The ‘localhost’ option when setting up HQP in Roon is specifically intended for running Roon and HQP on the one computer.
He may have meant that you can’t run Roon Bridge and NAA simultaneously on the same endpoint.
There are two HQPlayer products; Desktop or Embedded. They are separately licensed and people usually do not pay for both.
When you say ‘HQPlayer desktop (server) embedded’ are you referring to HQPlayer Desktop or HQPlayer Embedded?
Desktop has a user interface with a network control switch which you turn on if you intend to control it from another computer. Embedded does not have its own user interface, you configure it with a client program on a control device. Embedded does not have a network control switch because it is always network controlled.
This may mean that you haven’t set up the HQPlayer zone in Roon correctly as per the instructions linked above. If you are running HQP and Roon on the same server then use the ‘localhost’ option so they can talk to each other. If not then you need to enter the IP address of the computer running HQP.
Of course you can have both running on the same or different machine. In the official instructions the last bullet point is important and common source of problems, but other than that, there’s nothing special in having both running side by side.
yes he meant: you can’t run Roon Bridge and NAA simultaneously on the same endpoint.
I have 3 computers:
windows controller remote laptop (roon client)
‘AL’ /ROON server/HQPlayer ‘root’
‘AL’ /HQPlayer ‘NAA’
so, local host is no good!
I know desktop and embedded are seperate products, I have embedded in ‘AL’.
Embedded DOES HAVE its own interface actually; it’s in the sound menu on ‘AL’ Ver.3 LQXT ‘headed’ version. It does have the control switch as well! But i wanted to connect remotely from laptop controller using: IPADDRESS://8088, but it refuses to connect?
Yes i did set up the zone correctly as per instructions! Not using one PC, but 3! so local host is useless! Yes, I know I need the IP address of the HQP PC! However, it doesn’t work?
anyway Piero asked me to change the static IPADDRESS (option 11 system menu) from DHCP, so I did (192.168.1.147), and rebooted once! Now it won;t boot AT ALL, I just get a blank/black screen before it even reaches the bios selection screen, just hangs and nothing happens?
As an aside, I had all kinds of odd OS issues when running AudioLinux, particularly along with HQPlayer Embedded. If you have the option, move to another Linux OS. Life will get much simpler and the music will be enjoyed more frequently.
Embedded always allows network control, it doesn’t have such switch like Desktop version has. Because it would be rather pointless without network control…
You can also check if HQPlayer Client can find the server.
If web interface directs you straight to the /config page instead of front page, then output device selection or something similar is wrong, and HQPlayer is asking you to check the settings. If you cannot reach the web interface, then maybe the service is not running at all, or fails to start for some reason.
But when it comes to OS things, I can only comment on the ones that I support… Other OS solutions are supported by their respective vendors.
On the contrary, since your Roon core and HQP are running on the same computer, being the second one mentioned above, that is precisely the circumstance where localhost permits Roon and HQP to communicate.
HQP Embedded definitely does not have a user interface or the network control switch. It sounds like you have downloaded and installed HQP Desktop. You can check using the ‘About’ menu item. You can use either, but referring to both is just confusing.