I started playing with the JA11 and the KTmicro payload configuration tool and noticed several features not exposed by the FiiO Control app that may (?) skew the measurements:
After you 'REFRESH' the devices list, select "JadeAudio JA11" in the the drop-down list, 'OPEN' the communication with JA11, and 'SYNC' the JA11 onboard settings to the utility tool, the first screen you see is the 'VOLUME' (gain) control:
View attachment 425850
The 'DAC' gain can be set between 'Mute', -18dB, up to +3dB (default 0dB) by steps of 1.5dB. The 'ADC' gain can be chosen from 0, - 6, 8,14, 20, 26, 32, and 44dB (in that order, default is 14dB). Note that the default screen, before "opening" the communication with JA11 shows separate 'DACL' and 'DACR' gain setting: some KTmicro chips must have this capability.
The second screen is the 'EQ' configuration. The ADC and DAC have each a set of 5x PEQs.
Here is the config. screen for the ADC:
View attachment 425853
And here is the config. screen for the DAC:
View attachment 425854
I haven't figured out what's going on exactly between the KTmicro utility and FiiO Control Web App... They can run concurrently, having both access to JA11 in real time, but they don't seem to command the same thing, and are messing each other... For example, The KTmicro tool has Peak (P), Low-Pass (LP), High-Pass (HP), and Low-Shelf (LS) on each filter, plus High-Shelf (HS) on filter #1 only. The FiiO Control WebApp (or Android App) has Peak (P), Low-Shelf (LS), and High-Shelf (HS) on each of the 5x filters, but no Low-Pass (LP) or High-Pass (HP). It's possible that the KTMicro chip only understands biquad coefficients, so what filter types are available would be app-specific...
The 'DRC' (Dynamic Range Compressor) screen is unique to the KTmicro utility. It has a noise gate and a limiter, and they are not set to "zero"
Settings for the noise gate are (I'm definitely not an expert...): 'THlow' (low threshold?), 'THhigh (high treshold?), 'noiseT' (?), 'GateVol' (noise gate gain?), 'AT' (Attack in ms), 'RT' (realease in ms).
View attachment 425855
Settings for the limiter are: 'point' (the point at which it starts limiting volume), 'AT' (attack in ms), 'RT' (release in ms), and a 'SOFT' transition setting.
View attachment 425857
I suspect the noise gate and limiter would definitely impact measurements and may explain the inconsistencies seen between different firmware and or JA11 vs. JM12 w/ FiiO FW.
The next two screens are about the USB configuration:
View attachment 425858
...and the registers settings:
View attachment 425862
This utility tool is interactive: if you select 'EN' (enable) on each screen, you can hear in real time the effect of whatever change you make. But I think it's a production-type tool: you cannot save the new settings directly to the JA11, Instead, you 'SAVE' them against a base FW (a .bin file you select) and the tool create an updated payload based on the base FW and the updated settings. It generate a new FW with the same name and a 'NEW' at the end. From there, you'll have to flash this new FW with either the FiiO utility or another tool included with this KTmicro utility...
There is also a 'DOWNLOAD' command, although the name appears misleading: what it does is to "download" the settings from an existing FW (.bin file). I imagine it is for the OEM audio engineers: they can start from the latest .bin they saved and continue playing with these settings offline if they wish (no need to have JA11 connected).
I also started to look at some random KTmicro-based dongles & cables. For example, this very modest $3.25 KZ USB-C upgrade cable (KT0210 chip?):
View attachment 425868
The KTmicro utility shows independent L/V gain (to compensate IEMs imbalance?):
View attachment 425869
It also shows an interesting ADC (mic.) EQ with two very high Q Low-Pass & Peak filters:
View attachment 425870
Some kind of mic. response compensation?
The default DAC EQ is weird:
View attachment 425871
Two very high Q Peak filters at 12.33 kHz, another one at 12.34 kHz, and one more at 26.98 kHz ??? WT...
Unlike JA11, the noise gate is not used:
View attachment 425872
And the limiter is set at -0.5dB instead of -3dB on the JA11:
View attachment 425873
I haven't checked whether I can generate a usable payload for this KZ cable based upon the JA11 firmware. If it's a different chip with a different base FW, I assume it will brick the KZ cable...
Main takeaway after this loooooong post: as we see more and more of these DSP-enabled chips, some of them surprisingly feature-rich (e.g. the above $3.25 KZ "cable"... Can we call this a cable?), I think we'll have to be cautious when drawing conclusions based on the measurements... without knowing what's happening under the hood.