Roman you are doing something wrong or maybe you have an old(er) version.
With no input oversampling at 4x, CPU set to HIGH, and everything set to default values the output reads about -110 to -115 dBFS. This confirms what GTR was saying.

Your whole analysis is based on an incorrect use of Voxengo SPAN. That in and of itself is sufficient to make your whole analysis UTTER RUBBISH!
Stop spreading misinformation and wasting people’s time!

There is no noisey environment. The plugin runs in the DAW and the only noise comes from the plugin itself. The DAW is completely quiet.

Trying to discard my analysis because of a supposedly noisy environment that doesn’t exist and a different setting in SPAN (which isn’t as

important in regards to the issue at hand as you claim it is) is a disgeniuous attempt to discredit my experience.

Everything I encountered I have described in detail and documented in the videos I linked earlier. This isn’t a matter of opinion, it’s a matter

of facts and evidence as everybody can see for themselves in those videos.

You’re not discussing the plugin’s bugs that are shown in the videos – the worst of which is probably the lingering high frequency tones it

emits. Instead you are ignoring them and you’re creating straw men (noisy environment, wrong usage of tools etc.) to deflect from the actual

problems and even claim they don’t exist.

Don’t do that. It’s a disingenuous way of arguing. If you don’t experience these bugs, that’s great. But I experience them and more importantly

I have demonstrated their existence in the videos.

Other people have run into different problems with the plugin that I did not encounter, such as the dll not loading.

Yes, changing the slope changes how the readout looks but even with a slope setting of 0 the noise registers far above -120dBFS.

More importantly, the noise is audible! That’s how I discovered it in the first place, using my pair of ears, a tool I do know how to use.

I’m getting a little suspicious of your intentions as I see you fighting tooth and nail to defend and belittle this plugin’s bugs even after watching the videos demonstrating the various problems I described.

With slope at 0 dB, as it should be, the noise will be below approximately -120dB, which makes it non-existent.

If you’re going to use a tool, use it correctly.

Forgot to mention a few system details (Artyom’s bug report below reminded me): Win 7 x64, Projects at 44.1kHz