Roon / HQPlayer Integration

[orgel]

Is it a must that the HQplayer is in the same computer as the roon core so it is only added as localhost? For adding other network HQplayer are they meant only for NAA?

 

HQPlayer does not need to run on the same computer as Roon Core. In HQP, be sure you have the "Allow control from network" button in the toolbar highlighted. (It's the one that looks like a globe.) Once that's done, you should be able to add that installation of HQP to Roon as a Network Device by entering the (local) IP address of the computer running HQP.

 

--David

[hols]

Thanks, David. It is working now. Actually I have clicked the allow control from network button but was misled by the shade which I thought it is meant to be disabled.

[firedog]

Clicking the allow network control button also worked for the problem I mentioned above. I must have unclicked it by accident.

 

Thanks

[ted_b]

Clicking the allow network control button also worked for the problem I mentioned above. I must have unclicked it by accident.

 

Thanks

 

Is your Roon server/core on another machine from HQP or are you saying you needed to allow network control even with Roon/HQP local, for the problem to go away? I've had a couple of instances now, with my new HQP build, where HQP loses the NAA (no device drivers shown) while Roonserver is running (local) and unused. Seems to have stopped when I quit Roonserver (using drag and drop for the time being while testing new build so Roonserver is right now not a need).

[Dr Tone]

Can you play to HQP using ASIO or something similar? I was thinking I'd like to keep Roonbridge on my HTPC for the network transport portion but still play from Roonbridge through a local install of HQP on my HTPC.

[Forehaven]

I installed Windows 10 via Bootcamp on my Mini. I wanted to try using Win and it's ASIO driver. But I've been using Screenshare via MBP to control Mini. But with Windows loaded, there's no way to control Windows using my MBP?

Also, Windows will find Roon if I read correctly, but I need to buy another license for HQP on this partition?

If anyone knows a link with how to proceed, that'd be great. Thanks for any help!

[Dr Tone]

I installed Windows 10 via Bootcamp on my Mini. I wanted to try using Win and it's ASIO driver. But I've been using Screenshare via MBP to control Mini. But with Windows loaded, there's no way to control Windows using my MBP?

Also, Windows will find Roon if I read correctly, but I need to buy another license for HQP on this partition?

If anyone knows a link with how to proceed, that'd be great. Thanks for any help!

 

If Windows 10 Professional or Enterprise you need to enable RDP on the Windows 10 box and install the RDP client from Microsoft available in the OSX App store.

[Forehaven]

If Windows 10 Professional or Enterprise you need to enable RDP on the Windows 10 box and install the RDP client from Microsoft available in the OSX App store.

 

No, I bought the Home version. Do I need to upgrade to have this option?

[ted_b]

Yes, Win 10 Home does not support remote desktop.

[Forehaven]

Ugh...of course. Thanks Ted. I'll upgrade and see if I can do this. I may need to hit you up for some online help again ;p

[firedog]

Is your Roon server/core on another machine from HQP or are you saying you needed to allow network control even with Roon/HQP local, for the problem to go away? I've had a couple of instances now, with my new HQP build, where HQP loses the NAA (no device drivers shown) while Roonserver is running (local) and unused. Seems to have stopped when I quit Roonserver (using drag and drop for the time being while testing new build so Roonserver is right now not a need).

 

Just getting back to this, as it turns out the "allow network control" isn't the issue.

 

I'm simply losing connection to the NAA at random intervals - sometimes after one minute, sometimes after a few hours. I'm getting the "lost control of endpoint" message in Roon, and the only way I seem to be able to restore the connection is by rebooting the NAA, which is a time consuming and annoying process in my setup (as that requires me to also shut down the Mytek and the amp).

 

I'm not seeing any pattern or cause to the loss of connection to the NAA. It may be somehow connected to no signal coming from Roon, but today it happened between songs while playing an album. It's become enough of an issue that I've stopped using the NAA device for now.

 

In answer to your question, my RoonServer core and HQP desktop are on the same server.

 

Before the Roon 1.2 update I had an absolutely rock stable connection - with all the same hardware.

 

Hopefully this will get figured out soon, as I just ordered a microRendu, and would much prefer using it as an NAA, and not just as a Roon endpoint.

 

Thanks for your help.

[lmitche]

Ugh...of course. Thanks Ted. I'll upgrade and see if I can do this. I may need to hit you up for some online help again ;p

Try VNC or Team viewer before upgrading, they are free and make lighter use of processor and memory resources.

[hifial]

Try VNC or Team viewer before upgrading, they are free and make lighter use of processor and memory resources.

 

+1

 

Plus there is Splashtop.

[ericuco]

Just noticed that if you select "Time Remain" in HQP then the timer in Roon does not work nor does it report the correct track. Not really a problem or a bug just an observation.

 

When I ran HQP only, I would generally use "Time Remain" option so I knew how time as left on the album being played.

[mink70]

Hi, currently enjoying HQPlayer upsampling to 2xDSD on my new 13" MacBook Air i5 8 gigs RAM with great results. Wondering whether adding Roon core ouputting to HQP on the same machine will be too much for the CPU. Any advice?

[zorntel]

Hi, currently enjoying HQPlayer upsampling to 2xDSD on my new 13" MacBook Air i5 8 gigs RAM with great results. Wondering whether adding Roon core ouputting to HQP on the same machine will be too much for the CPU. Any advice?

 

What percent of CPU is HQplayer using in activity monitor when you are upsampling to DSD128? The main thing is that Roon likes its database to be on a SSD (music files can be elsewhere)...which your Air will have...so it shouldn't be a problem assuming you are not maxing out your CPU (20%) doing the upsampling. At one point I was upsampling to DSD128 with HQplayer and roon with a macmini 2012 with a 2.3 i7 SSD and it handled it easily.

 

Now I do roon on a separate machine because I sometimes use the same roon machine to run two different machines doing HQplayer upsampling (to DSD256) at the same time...thus I'm running two different music systems simultaneously playing different music from the same roon library. That all works great too.The macmini 2012 continues to run the roon core. Using roon is a definite improvement for file handling with HQplayer.

 

You might also ask this question over at the roon community.

 

Robert

[R1200CL]

Since installing 1.2, if I pause playback in Roon for more than a few minutes, Roon loses connection with HQP and HQP loses the connection to the NAA (the NAA stops showing up in the "device" box in HQP settings).

 

Roon itself is still connected to the network, as is the NAA.(I can see both in browser/network interfaces).

The DAC still shows it is connected to the NAA device, but there isn't a connection for playback. As I said, the NAA stops showing up as a "device" in HQP. This didn't happen before 1.2.

 

Just rebooting Roon or HQP - or both - doesn't help.

The only workaround is to reboot the NAA device itself.

 

I'm running RoonServer and HQP Desktop on Win10, and the NAA is an SMS-100 (Sonic Orbiter OS).

 

The software is all up to date.

 

Anyone else experience something like this?

 

BTW, also submitted this at Roon forum.

 

Do you still have this problem ?

 

I have the same, and I suspect it is NAA SW that can't re-establish connection.

Miska has so far not given any explaination why a reboot seems to be the only solution.

I've asked if he or others can test / simulate powerloss or network loss in order to confirm that the NAA SW does not recover if a short (non detectable) error occor.

 

I don't even know if some sort of hw error causes this, but at least if several does the same tests, like power off and on their NAA, we can at least know if all or only some get the same result/error.

 

If I understand Miska correctly, he stats connection should re-establish itself.

 

My posts are in another thread I think.

[R1200CL]

Firedog:

http://www.computeraudiophile.com/f26-sonore-sponsored/sonicorbiter-naa-output-mode-27274/index6.html#post585847

[firedog]

Do you still have this problem ?

 

I have the same, and I suspect it is NAA SW that can't re-establish connection.

Miska has so far not given any explaination why a reboot seems to be the only solution.

I've asked if he or others can test / simulate powerloss or network loss in order to confirm that the NAA SW does not recover if a short (non detectable) error occor.

 

I don't even know if some sort of hw error causes this, but at least if several does the same tests, like power off and on their NAA, we can at least know if all or only some get the same result/error.

 

If I understand Miska correctly, he stats connection should re-establish itself.

 

My posts are in another thread I think.

No, in the new versions of software I don't have the problem.

[paulpaul]

I am using a Windows 10 PC as NAA 3.4.2. I also found the NAA application just quit without a sign. I have to start NAA manually again or reboot the PC. It happened when I switched songs frequently.

[Miska]

I am using a Windows 10 PC as NAA 3.4.2. I also found the NAA application just quit without a sign. I have to start NAA manually again or reboot the PC. It happened when I switched songs frequently.

 

You could start it from command prompt, then you would have window left open if it terminates and possibly some message hinting towards the cause. Also HQPlayer log could tell something.

[paulpaul]

You could start it from command prompt, then you would have window left open if it terminates and possibly some message hinting towards the cause. Also HQPlayer log could tell something.

 

Thanks Miska. It is not a big issue by now. It only happens once for a few hours. I will open the log and find the hints. Merry Christmas!

[Foggie]

I'm trying to understand the volume "icon" in ROON. I'm using a headless wkst running ROON server and HQP and a mini as the NAA.

 

While in the ROON controller playing music, the volume icon on bottom right of ROON used to show the default "speaker". If you clicked the speaker, ROON would say volume is fixed. I notice now that it has a "-3" and when I click the speaker I get the following.

 

I looked at the audio settings in ROON and they appear normal (not much to set anyway). Not sure what changed

 

Any ideas what this means?

 

[tboooe]

I'm trying to understand the volume "icon" in ROON. I'm using a headless wkst running ROON server and HQP and a mini as the NAA.

 

While in the ROON controller playing music, the volume icon on bottom right of ROON used to show the default "speaker". If you clicked the speaker, ROON would say volume is fixed. I notice now that it has a "-3" and when I click the speaker I get the following.

 

I looked at the audio settings in ROON and they appear normal (not much to set anyway). Not sure what changed

 

Any ideas what this means?

[ATTACH=CONFIG]32275[/ATTACH]

 

[ATTACH=CONFIG]32276[/ATTACH]

That -3db is coming from HQP. Check your settings there.

[Foggie]

That -3db is coming from HQP. Check your settings there.

 

That's what I figured and the -3 is is a setting in HQP (default) but nothing has changed that I know of. It wasn't like that previously and you weren't able to chg the volume from the speaker icon as it would state "volume is fixed"

 

Not sure what setting would enable/disable that

 

 

Sent from my iPhone using Computer Audiophile