Thanks for your update. Friends over. Server and HQPlayer will not talk to each other. Had friends over. System sounding great and working. Your update comes through and nothing works. Frustrating. Please give us the option of updating or not. Right now I’d rather use 1.2.
Can we go back.
I’d rather not update (after your next update and get the system running) until you are sure it works.
1.2 always worked.
I agree!
Has been a lots of bugs.
Roon 1.3 crashes all the time.
1.2 was so stable, I miss it.
Does not help you right now but the option to not update has always been there.
I’ve popped this into Software, because as Nick has noted, the option to not upgrade already exists. Just ignore the blue window until you would like to upgrade.
If you need specific assistance, set out details of your system and the steps which create the problem and I’ll shift this to Support for particular assistance.
Hi,
I was not home for a few days. Everything was working correctly then.
Came home. Opened iPad and touched ROON icon. It displayed update available and before I could count to 3 the iPad updated the iOS ROON app and both and both my Audio PC which basically just runs HQPlayer and my PC Server which runs Roonserver apparently updated as well. I don’t recall seeing anything like, "do you want to update now yes or no. There was no choice it just did it. ( and basically why wouldn’t I want to update? My system has never worked like this before. The updates seemed to work.)
Since then ROON and HQPlayer will not synchronize.
ROON iPad finds the music and displays correctly.
The problem is roon talking to HQPlayer. I’ll start HQPlayer on the pc. I’m using the NAA setting for the microRendu. I make sure the microRendu NAA app is running correctly.
On my monitor displaying HQPlayer it shows that ROON and HQPlayer are talking.
Then you look at the four bars where you select filters, dither, auto and auto.
When those 4 columns are in dark black then you know ROON and Hqplayer are connected. But when one selects a track on iPad to play one of two things happens. Either the iPad displays can’t find transplant and nothing happens. Then I close HQPlayer and restart. Usually this solves the problem. But the next time one selects a track on the iPad the none none auto auto fades from solid black to grey. The time display on both the iPad and HQPlayer Time keep counting the track time. But never any output. there is no output.
Rebooting the machine seems to have the same effect as above. With no output.
I’d be glad to give remote access so you can see for yourself.
I would sometimes encounter this in 1.2 and earlier 1.3. A reboot of the pc or closing and reopening HQPlayer would get it going again.
I’ve also checked to make microRendu reboot no luck.
It seems like HQPlayer and ROON have had a divorce and won’t talk to each other.
Shifting to Support for attention.
I think I have also seen the Core update without prompting after opening an iPad Control. That needs to be investigated also.
also: iOS devices, if user set them to, do auto-update apps (and there’s no way back!)
so… iOS’ Roon control should keep compatibility with older Core versions, should the user opt to stay on those
Hi,
After hours of switching connections, rebooting computers, restarting iPads, a curse once in awhile, and blood shot eyes because of lack of sleep.
I finally got music! How? I closed ROON and started up jRiver. Wow! It worked.
But not with my Lampi DAC. I connected my USB to my Legacy Processor/DAC.
Next I checked to see if I could get it to play via ROON. I set HQPlayer to Wasapi, it found the WaVelet instantly so I can play music via ROON, HQPlayer, and WaVelet. So some progress
I believe the problem is between HQPlayer NAA, microRendu, and ROON.
Specifically that HQPlayer cannot talk to the DAC in NAA mode. NAA cannot find DAC and and it’s driver. Once in a while it will find the Lampi driver, start to connect, and the filter, dither, sample rate, and output mode will display in dark black. Mine says none, none,auto,and auto.
It looks like everything is reafy to play. But when you go to your iPad and select a cut one of two things occurs. Sometimes the Roon iPad display will flash Can’t find the transport in yellowing lettering. Or the NONE, NONE, AUTO, and AUTO will fade to grey and a pop up window states, Can’t connect. Check settings. So you do, only to find HQPlayer and ROON cannot find the DAC combo driver that Lampi uses.
One can restart the PCs, remove Fidelizer, use WSY2K12 without optimization by AudiophileOptimizer. I have Both the play back PC and ROONserver PC, running vanilla. And this is no help at all. ROON, HQPlayer, the microRendu, and NAA refuse to work together since the latest ROON update.
Or I guess it’s remotely possible that my Lampi’s USB input is broke, but I somehow doubt it’s the problem.
Who knows?
Ok. Some more information.
I have my Lampi DAC playing beautifully with jRiver and jremote. It’s connected to USB out of my PC using Amenero kernel streaming.
Nothing I do can solve the miscommunication between microRendu, HQPlayer, NAA, and ROON.
At least this last experiment proves that it’s not my equipment suddenly going Cookoo.
Anyone having the same troubles?
The ROON programmers taking heed?
While the above setup works flawlessly, the sound quality is a far cry from my usual setup.
Hi again,
I now have ROON and the microRendu in ROON Ready mode playing.
This should narrow the problem some more.
NAA, HQPlayer, and ROON still seem to be the culprits. 
Hi Steven,
I changed the title as requested.
In my own setup (see avatar) I use localhost HQP to an NAA on an mR. I haven’t had a problem with 1.3.
I have had the same symptoms occur when the input to the DAC is changed from USB to another source before HQP is stopped (HQP continues to hold Roon in a pause state for about 6s after Play is paused in Roon), or when HQP is started while the DAC has a non USB input selected.
When that occurs the problem is resolved by closing HQP, switching the DAC to USB, power cycling the mR and restarting HQP.
I’m not saying this state of affairs is acceptable, only that on my system that fixes a similar glitch.
What versions of HQP and mR/NAA are you using ? If the above doesn’t fix things then reinstalling the NAA on the mR (remove the app, update, select it again, update) and reinstalling HQP are further steps I would try.
I thought of downloading the latest versions of HQPlayer, NAA, and microRendu.
Here are a few questions.
HQPlayer is a pain to update. I went to the site and it said to uninstall hqplayer. I go to Windows Uninstall and what do you know, HQPlayer is not listed there to uninstall. Strange. So I downloaded and installed it anyway. Rebooted PC.
Found NAA downloads but clicking on un zip did nothing. Is the NAA updated when HQPlayer is updated? No clue.
Did not uninstall microRendu but it was updated to latest version.
I was not using anything but the USB into my DAC. But I did reboot, I don’t know, 30 times? No luck.
As I said HQPlayer finds the DAC. Sometimes. HQPlayer NAA is activated. MicroRendu for HQPlayer is started and restarted. I go to my sonic orbiter and make sure it’s talking to and recognized by NAA in HQPlayer menu.
Usually if everything is working correctly HQPlayer will have dark black letters in the 4 columns. Mine say NONE. NONE. AUTO AUTO.
The amereno driver is dispolayed correctly in HQPlayer setup and NAA menus.
Use iPad to select music. One of two things happen.
A. On the iPad screen, Transport is missing not found or something to that affect.
Or
B. The dark black lettering will fade to grey in the display
NONE. NONE AUTO AUTO and the Amenero drive will vanish.
Sometimes rebooting or restarting HQPlayer will bring it back only to repeat the above process.
I do have MicroRendu ROON ready running and music will play this way. jRiver will play music but NAA, HQPlayer, ROON, microRendu are dead to each other.
I have spent many hours at this.
And I’ve had this system working flawlessly ever since I purchased and installed the microRendu.
Until the last ROON update.
Steve, just some info that my help:
HQPlayer is a pain to update. I went to the site and it said to uninstall hqplayer. I go to Windows Uninstall and what do you know, HQPlayer is not listed there to uninstall. Strange. So I downloaded and installed it anyway. Rebooted PC.
In the HQP directory there is an uninstall application.
Found NAA downloads but clicking on un zip did nothing. Is the NAA updated when HQPlayer is updated? No clue.
If you are using microrendu you do not need to run the HQP supplied NAA file
Did not uninstall microRendu but it was updated to latest version.
Not sure what you mean uninstall microrendu. Once you connect that device to your network and go into its settings and select NAA HQP should see it.
Let me try to understand your issue…so in HQP settings, Backend you can select NAA but under Device you do not see your DAC? In the microrendu settings under DAC, what does it say?
So you have two issues?
Hi Steve,
As per above, there is an uninstall in the HQP directory. Jussi recommends that HQP be completely uninstalled before the latest version is installed.
The NAA in the mR (or any NAA) is not automatically updated when HQP is updated. mR periodically updates the NAA when the SonicOrbiter software is updated. You can prompt the mR to uninstall and reinstall the NAA app through the Software Manager by deselecting NAA as an available app, updating, re-selecting NAA as an available app and re-updating.
Try powercycling the mR before going to the trouble of reinstalling the NAA as above.
Not sure what you rebooted. Powercycling the mR usually fixes HQP not finding the NAA for me.
5/6. In the situation I have experienced HQP cannot find the NAA at all and says so. In settings the NAA is selected as backend but no device is shown. That is the situation where rebooting the mR can resolve the problem.
Sometimes after rebooting HQP will find the NAA again but will not restart with the previous settings intact.
I understand the Amenero driver is the front end of the Lampi when connecting directly from the HQP machine to the Lampi. In that case I would expect to see it as a separate driver in the Backend menu, and not in the “NAA menu” (which I understand is the Device menu). Can you provide screenshots of your HQP settings for your usual configuration and where you see the Amenero driver ?
Hi,
Ok. I will uninstall HQPlayer and reinstall.
Good to know about NAA updates.
I’ve been working with microRendu since it was first brought out. Plenty of experience starting restarting microRendu and mysonicorbiter. Until the ROON update I would have done exactly that and microRendu, HQPlayer, ROON, and NAA worked well together. Never any issues like this. I believe I’ve used this combo since last Fall.
I will try to explain this one more time.
When one looks at the opening (frontend) HQPlayer screen there is a row with 4 cells going horizontally across the screen.
Cell one. Cell 2 Cell 3 Cell 4
Filter. Dither. Upsample. PCM SDM
Mine say:
None. None. Auto. Auto
If everything is working properly the words will be dark black. However if the backend menu cannot find the DAC the words turn grey.
On the backend menu, if everything is working then NAA will be selected and then the amenero combo which represents the Lampi DAC will show up if HQPLAYER or the NAA can find the DAC.
But on mine it will stay blank because HQPlayer cannot find the DAC. (Sometimes)
So one of two things will happen if music will not play.
Or
One can restart the iOS app, restart the MicroRendu, reboot the PC, etc to your hearts content and one or the other scenario is the result.
This never happened until the latest ROON update.
I have confirmed by Trial and error that:
The Lampi USB input works correctly in other situations. So not the Lampi.
MicroRendu in ROON Ready mode, ROON iOS, ROON Server, play music.
If I use my other DAC called the WaVelet ROON iOS, HQPlayer, all work and play music when the Wasapi option is chosen in the HQPlayer back end.
In other words every option I’ve tested works together and plays music except the examples above with featuring HQPlayer, NAA, and ROON iOS.
I consider myself well seasoned when it comes to working through the intricacies of HQPlayer, ROON, iOS, etc. I cut my teeth on jRiver, jremote, jPlay, Fidelizer, AudiophileOptimizer, WSY2K12v2, and most recently Project Lasso.
My USB into my Lampi includes TPLINK MC200cms, MicroRendu, LAN Rover, with plenty of linear power supplies, lps1s etc just for fun. Works beautifully.
Sorry I can’t display screen shots of all this. I spend 4 days a week being my parent’s caregiver as one has Parkinson’s and the othe Alzheimer’s.
I’m hoping there will be some updates while I’m gone and the issues will magically vanish.
Thanks for all your help. Good to know about HQPlayer uninstalls and updates.
Had never come across that info. Also HQPlayer terms frontend and backend to describe the menus.
Thanks Steven,
I think the only difference between the symptoms I have experienced and that you describe is that your Device menu in HQP refers to the mR NAA by reference to the Amenero front end of the DAC whereas mine has some generic name that I haven’t bothered to change (it being the only NAA in the system).
Under the Network Naming tool in HQP are you seeing any other IP address coming up for the mR NAA ? It may be that HQP has found the NAA but at a different IP address.
Otherwise I’m fresh out of ideas and will drop a flag for @support to take over and investigate more thoroughly. I hope they can get you back on the road asap.
He mentioned that he couldn’t find Hqp in task manager. It would be listed as Sygnalist so can be uninstalled there. Perhaps that will help.
Don Ivey
@Sgr,
I’ve read through your posts. There are a few tests I would do in your shoes to isolate the problem–maybe you’ve already done some of them, but I can’t be 100% sure, so here goes:
Plug the DAC directly into the machine running HQPlayer and try to play the file using HQPlayer (no Roon)
Same setup as #1, but play the file using Roon->HQPlayer
Plug the DAC into the microRendu and use HQPlayer to play a file to it using NAA (no Roon)
Same setup as #3, but play the file using Roon->HQPlayer->microRendu->DAC
Configure HQPlayer to speak to the built-in sound card on your PC (or something else). Play the file using Roon->HQPlayer
If ALL setups involving Roon do not work, that points towards something broken recently in Roon (that weirdly isn’t affecting more people–that will require some digging to figure out what makes your situation special). If some setups involving Roon work and others don’t, that points to something with HQPlayer/NAA.
I believe that the communication between ROON, HQPlayer, NAA, and the DAC is the problem.
MicroRendu works in ROON Ready.
DAC works with ROON Ready.
HQPlayer works with ROON Ready when selecting Wasapi and the Lampi driver which is called Combo _______ __________ (Sorry I don’t remember the exact words here.) in the backend HQPlayer setup menu.
Of course ROON IOS and ROON server are doing exactly as they should.
Yes with HQPlayer in NAA mode. There are two issues. They may be the same issue. But they manifest differently but the same result occurs.
Or
In the past this happens if I’ve left for the week and start the system but all it takes is to restart HQPlayer or reboot the pc. Then everything acts as it should.
So I’m very puzzled. Especially after several hours of trial and error with no positive results. Except finding the system works as it should except under the above conditions.
HQPlayer works with ROON Ready when selecting Wasapi and the Lampi driver which is called Combo _______ __________ (Sorry I don’t remember the exact words here.) in the backend HQPlayer setup menu.
Of course ROON IOS and ROON server are doing exactly as they should.
This test mostly proves that the audio is making it from roon->hqp OK, but haven’t isolated whether the real problem is with HQPlayer or NAA or communication between the two (it’s almost definitely not the DAC).
My tests #1 and #3 would tell us more, though. If they fail, then you know this is purely an HQPlayer/NAA problem, since it can happen without Roon in the equation. If they pass, it points to an HQPlayer/NAA problem that can only arise when Roon is used in combination.
I still think those are the next step.
That said, since Roon can speak to HQPlayer in some configurations but not others, with no changes on the Roon side between success/failure, I think any technical investigation is going to start from HQPlayer and work its way out to Roon.