We can absolutely agree on that.
Personally I still avoid using the term synergy just because the number of exceptions is so much smaller than the number of combinations that work together just well. I hope that my previous posting didn't come across too harsh.
Having said that, I'm not talking against the concept of finding and matching components for best results.
Absolutely, because it's only part of an electromechanical spring and is meaningless without knowing the properties of the rest of the system.
This fat bass / loose bass is nonsense without the context of the electromechanical load (and if you want to really precise then the mechanical properties of the room also need to be included).
Anyway, back to the OP. I did some "independent" room tests given some very severe limitations in my measurement instruments, however, The baseline is my system is set to a flat target, and I have implemented RC using my Android phone and a Dayton imm-6C mic. I'm using Spectroid app and compared the S23 mic and the Dayton. The first 2 images are the Samsung mic, the second 2 are the Dayton. Ignore the lower yellow trace, it's the red max level we're interested in
The sound was a random Spotify white noise track, so that might be one (large) source of error (to be investigated). Not drawing any conclusions from this yet, other than it confirms what I already knew and that is that the S23 mic is not the same as the Dayton mic. I have installed the cal file for the Dayton, but I'm not sure that Spectroid uses that information, so let's assume not; however both show a very unflat room response givne that the Ultra has been through RC to a flat curve several times too.
It was too late to run a proper RC test with the Dayton attached to an independent recording device to verify the white noise source against the Wiim RC test tone signal. etc et, that's for another day
Actually, I should have posted this in the Android beta RC thread so apologies for dumping it here - will tidy up tomorrow
Dayton: