TBProAudio releases dpMeter3 - Free Digital Precision Meter Plugin including Loudness

[TheMaartian]

Originally Posted by batcat

The meaning of the word blurry is subjective, so it might be just me.
But when I compare the text of dpmeter 2 and 3 side by side, I much prefer the text of dpm 2.
It looks sharper, darker and less dull on my screen compared to the latest version of dpm3.
Please suggest a good quick image upload page so I can post a side by side comparsion image.
Edit: here is a link to the image
https://i.postimg.cc/28q8Y7T5/DPMeter-comparison.jpg

IMGUR is great. I have a free account, and haven't had any need to upgrade.

https://imgur.com/

[TBProAudio]

Originally Posted by batcat

The meaning of the word blurry is subjective, so it might be just me.
But when I compare the text of dpmeter 2 and 3 side by side, I much prefer the text of dpm 2.
It looks sharper, darker and less dull on my screen compared to the latest version of dpm3.
Please suggest a good quick image upload page so I can post a side by side comparsion image.
Edit: here is a link to the image
https://i.postimg.cc/28q8Y7T5/DPMeter-comparison.jpg

Yes, some texts look "lighter". Let me see what we can do here :-)

[TBProAudio]

V 1.3.1:

- GUI: small fixes

- GUI: VST2 resize fix for Audition

[TBProAudio]

1.3.4:
- Mouse handling consolidated: shift mouse drag slows down parameter change, ctrl mouse drag accelerates parameter change
- Fix for automation data processing
1.3.3:
- WaveLab: DAW sync fix
1.3.2:
- Preset manager: update

[sinkmusic]

Thank you for the regular updates, TBProaudio.

[kfj452]

So I am a little confused about the units here. AES17 says:

3.4
full-scale signal level FS

signal amplitude relative to the full-scale amplitude expressed in decibels, full scale or percent, full scale

NOTE Because the definition of full scale is based on a sine wave, it will be possible with square-wave test signals to read as much as + 3,01 dB FS. Square-wave signals at this level are not recommended because tilt or overshoot introduced by any filtering operations will cause clipping of the signal.

3.3.1
decibels, full scale dB FS

amplitude expressed as a level in decibels relative to full-scale amplitude (20 times the common logarithm of the amplitude over the full-scale amplitude)

So:

• If a sine wave has peaks at -14 dBFS, then the RMS level should also be -14 dBFS.
• If a square wave has peaks at -17 dBFS, then the RMS level should be -14 dBFS.

But in dpMeter4 the RMS value seems to be offset by 3 dB:






I have channel config=Left, so it should just be looking at one channel and measuring the level, correct?


It seems you are actually measuring in dBov, not dBFS.

• Full-scale sine wave = 0 dBFS = -3 dBov = 0 dBTP

• Full-scale square wave = +3 dBFS = 0 dBov = a bit more than 0 dBTP due to intersample peaks.

Also, could the RMS Mode tooltip be improved?



The manual says it has to do with the way channels are combined to provide a single reading, but the tooltip and labels in the software don't say anything about channels.

Also "Sum/Average + 3dB/Average" looks kind of like a math formula with divisions in it, rather than 3 different options separated by slashes. Maybe vertical bars instead? ¯\_(ツ)_/¯

[TBProAudio]

Originally Posted by kfj452

So I am a little confused about the units here. AES17 says:

So:

• If a sine wave has peaks at -14 dBFS, then the RMS level should also be -14 dBFS.
• If a square wave has peaks at -17 dBFS, then the RMS level should be -14 dBFS.

But in dpMeter4 the RMS value seems to be offset by 3 dB:






I have channel config=Left, so it should just be looking at one channel and measuring the level, correct?


It seems you are actually measuring in dBov, not dBFS.

• Full-scale sine wave = 0 dBFS = -3 dBov = 0 dBTP

• Full-scale square wave = +3 dBFS = 0 dBov = a bit more than 0 dBTP due to intersample peaks.

Also, could the RMS Mode tooltip be improved?



The manual says it has to do with the way channels are combined to provide a single reading, but the tooltip and labels in the software don't say anything about channels.

Also "Sum/Average + 3dB/Average" looks kind of like a math formula with divisions in it, rather than 3 different options separated by slashes. Maybe vertical bars instead? ¯\_(ツ)_/¯

We don't think that dpMeter4 is wrong. If you need/want AES17 you need to use RMS Mode "AVG+3".
We will revise toolt-tip test, thank you for this.

[kfj452]

Originally Posted by TBProAudio

We don't think that dpMeter4 is wrong. If you need/want AES17 you need to use RMS Mode "AVG+3".
We will revise toolt-tip test, thank you for this.

Could you change the labels to "dBFS" and "dBov" instead?

[TBProAudio]

Originally Posted by kfj452

Could you change the labels to "dBFS" and "dBov" instead?

Hmm, why should we do this?
RMS mode is calibrated to 0 dBFS.

[kfj452]

Originally Posted by TBProAudio

Hmm, why should we do this?
RMS mode is calibrated to 0 dBFS.

But... it's not... That's what I'm saying. Do I not have it configured correctly?

If I put a 0 dBFS sine wave tone into dpMeter4, in RMS mode, the peak measurement says 0 dBFS, or 0 dBTP, which are correct, but the RMS measurement says "-3 dBFS" which is not correct:


This is single channel, so the "RMS mode" drop-down doesn't affect it.

It should either say "-3 dBov" or "0 dBFS":

• a full-scale sine wave is 0 dBFS or -3 dBov
• a full-scale square wave is +3 dBFS or 0 dBov

https://www.sis.se/api/document/preview/571704/

3.10
full-scale amplitude
FS
amplitude of a 997 Hz sinusoid whose peak positive sample just reaches positive digital full-scale

3.4
decibels full-scale
dBFS
the r.m.s. amplitude of a sinusoid described in 3.10 is defined as 0 dB FS

https://www.itu.int/rec/dologin_pub....F-E&type=items

8.7 The unit "dBov"

The level of a tone with a digital amplitude (peak value) of xover is therefore L= –3.01 dBov.

[TBProAudio]

Originally Posted by kfj452

This is single channel, so the "RMS mode" drop-down doesn't affect it.

Well this is obviously not true. dpmeter4 RMS mode matters:

SUM: sum of all root mean square (RMS) values

AVG: avg of all root mean square (RMS) values


AVG+3: avg of all root mean square (RMS) values +3dB according AES17


In any case: we will change naming "AVG+3" to "AES17".

[kfj452]

Originally Posted by TBProAudio

Well this is obviously not true. dpmeter4 RMS mode matters:

I mean that I have Ch Config set to "Left", and Mode set to "RMS", so it's just measuring a single channel and I want to measure the RMS level (and A-weighted RMS level) of a single signal, and not deal with stereo vs multichannel vs whatever.

If I change "RMS mode" button to "sum" or "avg", the measurement is the same, since there's only one channel. Shouldn't it read 0 dBFS in this case?

[TBProAudio]

Originally Posted by kfj452

I mean that I have Ch Config set to "Left", and Mode set to "RMS", so it's just measuring a single channel and I want to measure the RMS level (and A-weighted RMS level) of a single signal, and not deal with stereo vs multichannel vs whatever.

If I change "RMS mode" button to "sum" or "avg", the measurement is the same, since there's only one channel. Shouldn't it read 0 dBFS in this case?

OK: why not set RMS mode to "AVG+3"?
Thank you.

[kfj452]

Originally Posted by TBProAudio

OK: why not set RMS mode to "AVG+3"?
Thank you.

Yes, adding a 3 dB offset causes it to report the correct number, but I mean that the unit labels are not correct. When RMS mode is set to "SUM" or "AVG", it says "-3 dBFS":



which is not correct. If you want it to be offset by -3 dB like this, it should not say "dBFS", since that's not how dBFS is defined. It could say "-3 dBov" though, since that unit is defined with a reference that is 3 dB higher.

Like when you turn on Offset, the unit changes to "dB":



which is correct, since it's no longer referenced to full-scale. (It could also be labeled "dBr" to highlight that it's a relative measurement)

[TBProAudio]

Originally Posted by kfj452

Y... It could say "-3 dBov" though, since that unit is defined with a reference that is 3 dB higher.

Thank you, we will change this with next release.

[TBProAudio]

Update to 4.3.3:
- FIX: RMS mode "AVG+3" changed to "AES17"






Sprache erkennenundefined
undefined











Die Sound-Funktion ist auf 200 Zeichen begrenzt


Optionen : Geschichte : Feedback : DonateSchließen

[kfj452]

Originally Posted by TBProAudio

Update to 4.3.3:
- FIX: RMS mode "AVG+3" changed to "AES17"

Thank you for changing it! But... the units are reversed. :/ In AES17 mode it should say "dBFS", and in "sum" and "avg" modes it should say "dBov".

• Full-scale sine wave is 0 dBFS (AES17, IEC 61606, ITU-T P.38x)
• Full-scale sine wave is -3 dBov (ITU-T G.100.1)