I've doing a lot of trial-and-error with the 2i2-Monitor1-ADCiso combination. It has confirmed that even with the ADCiso as input that setting the input to a "sweet spot" produces the best results. I say "a" sweet spot because at least in my testing there can be more than one depending on the goal. I tested more than one ADCiso switch setting for 0 dBFS. Some of my results are similar to other measured results I've seen for Stepped-THD vs Level for the 2i2 as well as other audio interfaces. The HD components are low, but within their range they are somewhat erratic. Selecting an REW output dB at random produced somewhat "random" results. Finding the "sweet spot" for the ADCiso was in this manner was not very reliable. Different output levels resulted in varied HD component values. H2 up with H3 down and vice-versa as one example. HD components low with high noise and vice-versa. I found this totally unsatisfactory. Seemed like probing in the dark.
I tried another way. The Stepped-THD vs Level provides a good way to view relative distortion products as well as their absolute values for the signal supplied. The relative relationship was my focus. I ran the S-THD vs Level with a 1dB step. After examining it for relative H2/H3 I chose one where they met at a fairly low level, but not with high THD-Noise, in the upper range of dBFS. Next I ran the single-tone THD with the REW output at that dBFS point. The single tone HD components closely matched those at that level on the Stepped-THD graph. All of them, HD1-HD9 and noise. Then I did the same for a number of other dBFS points on the Stepped-THD with the same results, single-tone results matching HD components very closely. The problem was that there was often a large difference in results between level points. That is, the various relative levels of harmonics from one were still very different than another. That's fine if one is only interested in learning about the audio interface itself. But for my use the interface is only a tool, but I want to use it at its optimum (sweet point) if at all possible. This is meant to minimize its influence in subsequent device measurements, either amplifiers or raw speaker drivers. The problem I saw was that the 1dB step in the Stepped-THD was too choppy. The step was too big, better levels might exist between the steps.
Next I took advice given by Rja4000 and made more tests, first the default, then with coherent averaging. The latter proved to be very useful.
So I ran a Stepped-THD of 2i2-Monitor1-ADCiso with 0.1dB step with coherent averaging (eight average per step). On my old Gen 4 laptop this took quite a few hours, but REW did complete it. This provided much finer detail for choosing dBFS points for the single-tone test. This is in essence a balancing act. As will be seen in graphs below the relative HD components vary sometimes dramatically. The important thing is to choose a point that emphasizes (or minimizes) the distortion product(s) to examine.
Keep in mind that this is using the Scarlett 2i2 for output, certainly a limiting factor, yet with surprising results.
This is the 0.1dB Stepped-THD:
This is a very busy graph. I suspect that the big steps are glitches in the long test run. To examine it I first disabled all but HD2-HD3 as those are more important to me. Later I decided that I should include up to HD9. After a couple or single-tone tests I expanded the graph range to make viewing easier, making dBFS points easier to choose within the range that tests had shown best results. This is a partial screen capture so that the cursor position I chose is included.
I had initially chosen -24.5dBFS due to the low value and intersection of H2 and H3, but -21.0dBFS seemed best overall. Later I moved to -20.3dBFS. Those graphs will be included further down. I may re-export the files with comments above the graph to make it easier to read them.
This is -20.03dBFS (no coherent averaging):
-20.03dBFS with coherent averaging:
Overlay of the two:
It's not easy to see, but the HD components are nearly identical.
As a final note I ran some tests with the ADCiso switches set for 10V 0dBFS, but results were not quite as good. This was before I used the technique described above. I may test other switch settings, but it's very time consuming.
Next will be moving to tests of the V3 Mono again using the ADCiso in that loop. The focus of all the above is to find the "sweet spot". Then when testing an amplifier the Monitor1 will allow me to set the amp probe feedback through the Monitor1 so that the input to the ADCiso is precisely (or as close as possible) to the desired sweet spot.
Edit: I should point out that the dBFS values were all those of the 2i2 output at was easier to keep track of the tests that way. For tests of the V3 Mono I will need to determine the ADCiso input dBFS at those REW output values.
One more note. This is an ADCiso A grade.