1
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by wojak -
I have no new arguments and you still haven't convinced me. Maybe @misio can shed some light on the situation. He/She has been pushing me in the other direction. I don't care either way. But I can't follow 2 different expert opinions at the same time.
Consider me no expert - I just judge those readings by eye/ear and in comparison to other known (established?) meters. For ex. if I measured the files (with RG) and they say they have peak (true-peak) at -0,5 and your plugin and other "similar" plugins say that it is more or less -0,5 - I'm happy. There were two previous version of this plugin that said it was 2,5 (by eye) so it was different than RG and every other player plus those files did not clip (I suppose they should with peaks at 2,5). So I reported that your peaks were to high. Now they look OK to me.
As for RMS - I just made a live comparison of readings while playing a track and it was like that:
- 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.