I've checked a number of these reviews now with the Powercube measurements when I had a minute or two, and I'm pointing it out here again since this is not a Class D amp. The other I commented on was a Hypex. I thought it was perhaps an issue with the Powercube interacting with the Class D output stage, but it's not that since this is a rail switcher. The Powercube testing is reactive and capacitive loads is great, along with adding a 2 ohm burst capability, but the results do not make sense in many of the reviews which show near perfect cubes. The same is true here. There was a Purifi which did it too, and a handful more Hypex as well.
As far as I can tell, no one has noticed this issue yet. Having complex load result is fabulous, but not if the results are wrong or suspect. The test protocol that Audio Precision uses and which the Powercube uses for the two tests above are hypothetically identical (despite the named standard differing, the protocol is the same), both using 20ms 1kHz tonebursts. The reported power results, however, are (again) not the same. Instead of the ~1200W that APx reports at 4R, Powercube is reporting a perfect cube and 1958W at 4R. Crown's spec sheets have gotten laughably bad, but they also report 1200W of "Minimum guaranteed power, 1kHz" whatever that means. Burst? Continuous? Who knows. But at 2 ohms, they claim 1600W, not 4,000(!). I can't imagine if there was also realistic scenario under any sort of actual real benchmark they would have missed that trick of claiming an amp with a 8,000W dynamic power. (The whole pro amp industry has gotten just about as sketchy as the car amp industry, with many having borderline meaningless spec sheets.)
All of these weird results with "perfect" cubes, numbers that don't match up to spec sheets, disparate results between systems, leads me to believe there is something amiss with the Powercube results. Audio Precision is much higher volume, trusted, and less likely to have gotten this wrong. Whether a stimulus protocol error or a graphing error or a measuring error (or PEBKAC error, but seems unlikely), I have no idea, but there has to be some sort of bug going on that Audiograph needs to iron out. Sometimes the results seem valid and the two systems mostly match up, other times not so much. That shouldn't be.