26-Nov-2016, 18:10
Interesting! I've had the exact same error once and also heard it happening. The amp literally stopped outputting music for a split second only my sub continued.
Took a picture of the error on the screen, exactly the same as you report, but haven't bothered yet to report it. It happened on the second or third day and I had it running continuously (playing music or a burn-in disc at low volume when away) since first power on. Removed power cord and reinserted it and it hasn't happened since, just checked no errors logged. Don't really think this reinserting the power cable solved it other than fully resetting the device. I blamed it on it being new and/or a calibration error.
My D is connected to a P3 PowerPlant to output an exact and steady 230V so I doubt it's really an external over voltage issue.
Took a picture of the error on the screen, exactly the same as you report, but haven't bothered yet to report it. It happened on the second or third day and I had it running continuously (playing music or a burn-in disc at low volume when away) since first power on. Removed power cord and reinserted it and it hasn't happened since, just checked no errors logged. Don't really think this reinserting the power cable solved it other than fully resetting the device. I blamed it on it being new and/or a calibration error.
My D is connected to a P3 PowerPlant to output an exact and steady 230V so I doubt it's really an external over voltage issue.
PS Audio P3, Shunyata ΞTRON Alpha Digital and HC/Furutech power cables, Paul Hynes SR7EHD-MR4, DIY Roon Server & Roon Endpoint running AudioLinux Headless, Phasure Lush^2 USB cable, Audioquest Diamond RJ/E ethernet, Uptone Audio etherREGEN, Mutec MC-3+ USB, Shunyata ΞTRON Anaconda Digital XLR AES/EBU, Devialet Expert 250 Pro CI, Nordost Tyr Reference LS cables, Von Schweikert VR-5 SE Anniversary Edition, Anti-Mode Dual Core 2.0, JL Audio Fathom F112. More detail here.
The Netherlands
The Netherlands
