These functions are available on HQPlayer OS web interface.
However, on regular Linux distributions these functions are not available, as hqplayerd service is running under unprivileged user id for security reasons.
On a regular Linux distribution you can typically install Cockpit if you need remote web management features.
Why do you switch the clock source? I have it always set to the digital input I use and never switch away.
You can switch inputs through a HQPlayer control application (a more complete one). For example from HQPlayer Client. But of course with Embedded it also works through the web interface.
The reason is simple: otherwise, the source doesn’t change – in this case, it won’t switch to the external digital source and plays nothing.
In other words, unless I set the clock source to “Internal,” I cannot use the external digital sources attatched to the RME sound card.
It is of course possible that the newer AIO Pro is somewhat different in behavior than the older AIO I have (two pieces). Or something else slightly different. Most of the time I run Desktop locally on Windows with direct ASIO input and output goes to a NAA. You could try such and see if it makes any difference in your case.
Below is what you wrote to me on Oct. 29, 2024.
Excuse me for pasting part of the private communication here.
"I sent question to RME, asking how much different the new card is from the older one, but no reply so far. The current driver doesn’t seem to have support for the new “Pro” model, only for the original one, and that’s why it doesn’t appear on the device list.
So at the moment we can assume that the card won’t work on Linux, only on Windows. Unless RME can shed some more light into differences between the two versions of the card."
So, the new version still seems inconvenient compared to the older version…
I would still try out the way I outlined above, to see if it works the same for you or different. If it works, then there is more investigation to do why something goes wrong in your NAA+Embedded setup. If it doesn’t, then we can conclude the hardware behaves somewhat different in the end, or the particular driver version we are using has some differences.
This could help locating the whereabouts the issue is.
@jussi_laako
So, I tried the Desktop, but the external input basically didn’t work at all, with the exception of a playback once…
I can’t even reproduce the situation, so I’m not sure what made it work for that one occasion.
It just fails to play because the transport is empty. But why do you have a NAA running there at the same time? You have set the input through ASIO driver and output through a remote NAA?
Remember to set a correct channel offset here. Offset 0 is the analog input (channels 0 & 1)!
You can refer to your HQPlayer Embedded configuration for the offsets for example. IIRC, the channel layout is also described in the AIO manual. You can also find the channel names from HQPlayer log file now that the ASIO driver is selected as input device.
Are there detailed instructions on how to get HQPlayer 6 embedded running on Unbutu with a RTX5090? I spent five hours trying to get it installed with the help of Google AI last night and kept running into errors. At one point i got the the screen with the blue border and when I hit ok I thought I was in the clear, but no.
Thank you.
So, after setting it to offset 2, it did work ONCE.
I mean, after switching to roon, I cannot return to the external digital input.
This persists after rebooting HQP Desktop or even the entire Windows 11 system.
You should be able to load the input URI to the playlist. In the latter screenshot, transport is empty and playback cannot be started because there’s nothing to play.
The overall procedure is explained for example in the quickstart guide:
However, it fails after running roon and attempting to switch back to the external input.
Desktop even shuts down unexpectedly.
Below is the log file after that happens: