Solstice380 Posted February 15, 2019 Share Posted February 15, 2019 Glad to hear that you got things sorted out! Unfortunately, there are still many with issues that they have not been corrected. Check this thread: I’ve had issues with HQPlayer NAA since 4.22, which is what the US distributor put on it after it decided to corrupt its own card. Notified Crux Audio right away and never got a reply. Others with Squeezlite, etc., have had issues - some resolved, others not. We’ve experienced issues with the activity light. I’ve had verified card burns (2) not even start the 200. I’ve also had versions in 4.5.x series that wouldn’t open the HQP NAA. I can’t agree that the support has been terrific. 89reksal 1 https://audiophilestyle.com/profile/21384-solstice380/?tab=field_core_pfield_3 Link to comment
Solstice380 Posted February 15, 2019 Share Posted February 15, 2019 4 hours ago, ronfint said: Have you tried contacting May Park directly? My bad that I haven’t gone direct to May. I will do so. Thanks for prodding me to do it. Is it just may @sotm.com? https://audiophilestyle.com/profile/21384-solstice380/?tab=field_core_pfield_3 Link to comment
Solstice380 Posted February 16, 2019 Share Posted February 16, 2019 2 hours ago, tedwoods said: NAA has been flawless for me in 4.56 , through the Amanero/Lampi or Xmos/Holo Spring. That’s good to hear. It may be something specific to my dCS DAC as this issue started for me with 4.22. I had hoped one of the recent updates would clear it up. This morning I tried the forced upgrade to 4.5.6 from by burned 4.5.6 card as 5-pot-pan did without success on the pops and ticks. All other function seemed to be OK. Good response, HQP NAA functional right away, just occasional light activity not full blast blinking when not playing. But still the pops and ticks. I do need to contact them for some help. Thanks to all for the help and info! https://audiophilestyle.com/profile/21384-solstice380/?tab=field_core_pfield_3 Link to comment
Solstice380 Posted April 16, 2020 Share Posted April 16, 2020 On 4/14/2020 at 6:51 PM, jp11801 said: Any thoughts from from people with experience would be greatly appreciated. Hi @jp11801. It sounds like it won't get past the POST to power on and start the OS, so some bit of internal hardware is either disconnected or has failed. Or a wild possibility may be the power supply you are using is going bad and not providing the minimum voltage necessary. Have you contacted SOtM? https://audiophilestyle.com/profile/21384-solstice380/?tab=field_core_pfield_3 Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now