First, we are not looking for accuracy in low frequencies in this discussion. Second, 32K points gives you near 1 Hz resolution already.
But these are not the main issue. The issue is that you seem to be saying, "look at how low the noise floor is" but such a statement cannot be made without looking at impact of FFT gain. Your 128K FFT divides the noise buckets by four, resulting in low numbers on the graph when in reality that doesn't happen.
Hi Amir, visually yes, but in the computation of THD+Noise, no. Too small FFT length
AND only few averages, will show variations in noise calculation and therefore THD+N, between measurements. So increasing the FFT shall not decrease the noise floor when computing the SINAD, unless the initial FTT size was too low, ie making the computation less precise. Same goes with increase of averages, by the way, but less so.
Couple of examples to illustrate. Like
@restorer-john, I used an old Denon preamplifier (PRA-S10 in my case) with its MM phono input. All measurements below were done at 48kHz sampling rate input of the ADC, output being 50mV and input 2V (gain 32.05dB).
Let's start with 2M FFT - 32 averages:
SINAD = 82.6dB
Same but 256k FFT - 32 averages:
SINAD = 82.6dB
Same but 128k - 32 averages:
SINAD = 82.6dB
Same but 64k FFT - 32 averages:
SINAD = 82.6dB
Every time we've seen the noise floor increasing visually, but the calculated noise, and the resulting THD+N, remained the same at -82.6dB.
Now same again with 32k FFT - 32 averages:
SINAD = 81.1dB (best score when measuring at this FFT size).
Only here, the calculated noise floor is increased, and that's because of the lower resolution, not because there's more noise.
As a matter of facts, reducing the averages to 4 instead of 32, but keeping the 32k FFT size, I see variations from this:
SINAD = 79.4dB
to that:
SINAD = 82.7dB
So the combination of (too) small size FFT and low number of averages shows significant variations in the results because of the lower resolution. So the SINAD will vary significantly depending on the moment of the capture. The operator can perform multiple captures and keep the best one, but alternative option is to increase FFT size and averages.
Indeed, with a 1M FFT size, and only 4 averages, the results are more precise with much less variation between two screen captures:
Example 1, 1M FFT size - 4 averages:
Example 2, 1M FFT size - 4 averages:
It is only 0.5dB difference between best and worst capture, as opposed to 3.3dB with 32k FFT.
All of that is the reason why, as per my own rule, I always go for an FFT size which is the next higher length than 2 times the sampling rate (128k FFT for 48kHz sampling rate, for instance), and 32 averages. It only takes a few seconds to compute and I don't bother waiting for the best or worst measurement.
Cheers