1
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by pqyt -So can we at least agree that there's room for interpretation? I'll look into the peak problem because Case pointed out that the 1/sqrt(2) correction should not be applied to the peak and it was removed in 0.7.6.0.As for RMS - I just made a live comparison of readings while playing a track and it was like that:@wojak, would you please download one of the test files from https://www.soundonsound.com/techniques/sos-audio-test-files, preferably one with a dBFS number on the file name (e.g. 1_mono tone 1kHz -20dBFS 44k.wav or 19_Pink Noise stereo 20Hz_20kHz -23dBFS 44k.wav) and let us know what readings you get with other plugins?
- your component with +3 disabled showed the same values as VST TT Dynamic Range Meter and the same as VST dpMeter5 and the same as VST Span (that one with DBFS+3 set). If I changed Span to DBFS (without +3) it showed 3 more than all the others (inluding yours which was with +3 disabled). So it seems (again judging by eye) that your RMS set to 0 shows what other show and when set to +3 it shows different values than others.
So to me (as an amateur) it seems that Peaks now are OK and RMS might be too high by 3. Or in other word: to make all those 4 meters show the same values I have to set yours to 0 (+3 disabled) and Span to DBFS+3. Other two do not have those options to change but show the same values.
1_mono tone 1kHz -20dBFS 44k.wav:
- your component at 0: 20/20 (RMS/PEAK)
- your component at +3: 17/17
- vst TT Dynamic Range Meter: 20/20
- Span at DBFS: 23/20
- Span at DBFS+3: 20/20
- dpMeter: 23/20
- youlean loudness meter: 23/20
So it seems that RMS should be as @Case said - lower by 3 (or third option: -3).
Peak seem OK but one strange thing that your component also shows 17 as peak when +3 while all others show 20 no matter if +3 or not.