I appreciate your previous responses very much, and I did some further digging back through my discussions with iFi and think I figured out what I had misread, which I’d like to humbly clarify if I may.
First, I agree that iFi falsely intimated in their press materials for the ZS that it was MQA “compatible”, which gave many of their less technologically-invested consumers the impression that it was capable of MQA decoding, especially since it was a new addition to their “Zen” series, and was released around the time that they refreshed many of their devices (including the Zen DAC v2 and Hip DAC v2) with the upgraded 16 core XMOS capable of a complete unfold. At launch, what the ZS was actually capable of doing was either performing an initial unfold for rendering DACs (MQB), or passing through unprocessed MQA streams to DACs with full decoders for MQA or MQA Studio playback.
Then in early December, iFi released a firmware update that suddenly stopped performing the first unfold to pass on via Tidal Connect, and this caused a serious meltdown amongst their consumers—the row was intense over at Head-Fi. Although iFi was not being transparent about the explanation for this (they merely said that they were working on a fix), what actually happened was that MQA corporate rescinded their certification to perform the initial unfold. Unlike the Tidal app, Tidal Connect does not perform the first unfold, and suddenly users with render-only DACs were unable to process MQB Tidal Connect streams. This didn’t portend an issue for me, because my Topping DAC is a full decoder and MQA passthrough wasn’t affected—I was able to achieve MQA Studio playback from the beginning, fortunately.
Because of that, I was at first unclear about what the fuss was all about, and I attempted to come to ifi’s defense on that thread, amidst an outrageous troll fest—which in fairness primarily came from those who either completely misunderstood how MQA works, or were unaware of the differences between Tidal Connect and the Tidal app. IFi kept saying they were actively working on a fix amidst a whirlwind of inaccurate conjecture and accusations flying around, but admittedly they were being very vague about what caused the problem. It was only after quite a bit of back and forth and some vitriol directed my way that Sebastien Chiu PM’d me and explained the licensing obstacles that had emerged, and that they had lost their first unfold certification.
Upon re-reading his response yesterday, what he actually told me was that their workaround-in-process was to attempt to get rendering certification from MQA in lieu of the first unfold licensing that they lost, which apparently grants licensure for all steps of the unfolding process, and has nothing to do with the hardware capability of the device—it’s purely a legal/contractual definition. I have no idea why obtaining that was simpler than just appealing for reinstatement of the first unfold license, but apparently it has to do with the device category the ZS occupies. Obviously they eventually found a successful solution, because they fairly quickly released a new firmware that reinstated the first unfold, and added a new MQA Passthrough tab for Tidal Connect-only to the ZS GUI.
Anyway, it was the rendering certification language that caused my confusion yesterday, and I just wanted to correct any claims I made that were misleading.