1
3rd Party Plugins - (fb2k) / Re: Best way to equalize according to a curve
Last post by widemediaphotography -Other thing... Mathaudio plugin in my audio-pc works fine without intall VST plugin; Is it possible?
Hello pqyt
I have detected an anomaly in the latest version. If you enable Leds in Peak Meter mode (Image1) and mark Left and Right (Image2) it does it correctly, but if you disable Left and Right (Image3) only the Left channel is displayed. In the previous version it did it correctly.
But the Peaks seem OK to me (by eye), those also seemed OK from the beginning. Only two or three version from a few days ago seemed wrong and now it seems OK again with music (and weird with this one test file but only with +3 which should not change peaks as it is supposed to recalibrate RMS only).See the screenshots from the quick hack above. I never expected this to be more difficult than the curve representation of the spectrum...
I again propose to implement text peak values as it would make the comparison with other meters easier. Other meter usually show the max value of the track up to the present point (the highest value reached from the beginning of the track to "now") and not the actual momentary value.
OK. I fold. ;-)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.
@Case - I hate to bother you, but could you please post the latest binary of Helix to this thread? I try using the latest version from Rarewares (both 32 bit and 64 bit) and they both run really slow, and slow down my system...yet CPU utilization isn't near full when encoding using foobar2000.
There is something wrong about Lancer mod 2021-05-11 hosted on RareWares. It is unable to correctly encode WAV when its sampling rate is less or equal to 11025 Hz: SSE2 version outputs silence, SSE3 outputs heavily distorted sound.
I'm off to Spain for 2 weeks tomorrow so my mind is elsewhere!! I don't think I will get to look at this until I return so please feel free to remind me if I should appear to have forgotten about it.
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.
a) gudki.11khz.mono.mp3 and gudki.22khz.mono.mp3 are malformed files (24 293 bytes), apps refuse to open themThe file is outside specs, also called "freeformat". There are some decoders with freeformat support, but of course it makes no sense to use such formats anywhere. I think the best option is to disallow incorrect settings, what do you think?
Helix has a few checks to discourage settings that are deemed non-recommended. For instance, for 44.1 kHz files, it won't go below -B48 and will just barf "ENCODER INIT FAIL" at the user. When taking away those checks, Helix can, e.g., create "passable" 80 kbps 44.1 kHz CBR files with intensity stereo, but I so far refrained from relaxing those checks in fear that the encoder might explode in unexpected ways.
If you use Playback Statistics, you can create an auto-playlist. Click on Library menu > Playback Statistics > 'Show recently played' > (change the time frame if you like, see query syntax) > click '...' in search bar > Create Auto-Playlist. (Rename the playlist as you like)Many thanks - works! :-) Just one think (but this might be too much): the song gets logged after 1 minute approx, which means if the song is shorterned earlier - it will not get into the log. Is there maybe a place to change this timing (cannot find it in config...)
Or for JScript Panel 3, there is a Play Log script included.