TBProAudio releases mvMeter - Multivariable Meter including RMS, EBUR128, VU and PPM measurement for

[TB-ProAudio]

to be inaccurate (stereo mode)

Well, the "stereo" thing has been explained several times:
some call it "stereo mode" (mvMeter) others call it "mono/stereo sum" (single needle mode).

In fact mvMeter shows in this mode the mono signal (if mono input) or the stereo sum (if stereo input) with a single needle.

I hope this helps

[Compyfox]

... I find it sad that his products are inaccurate ...

Well, this is obviously not true.

Er... I proved it with all my early posts in this thread?

Are you implying now, that you "fixed that all yourself", without any further help or anybody pointing out the gaping issues? Is that meant to be a joke, or are you serious with this?

Otherwise please provide facts that you can understand. Thank you.

Might be a translation error, but why should I provide facts that I can understand?
Honestly, I do understand this topic (metering), hence me posting in here - but do you understand it?

Well, the "stereo" thing has been explained several times:
some call it "stereo mode" (mvMeter) others call it "mono/stereo sum" (single needle mode).

Stereo Mode is the complete wrong term for that (IMO and all that), and should never be called like that either. If we're talking "stereo", then we talks two VU's with one for each channel or one VU but with dual needles. (see various VU's that came before yours, including zplane's PPMulator!)

"Stereo SUM" is in this case also not the same. I sent in a "MID" signal, and it read complete different values than a "stereo signal" being summed (the way you do). I wrote about this in detail a couple of posts back, and I also wrote how to fix this.

Apparently, you either completely ignored it, or don't understand yet again what's going on (remember our conversations for several mails and forum pages about the AES+17 offset for dpMeter?)

In fact mvMeter shows in this mode the mono signal (if mono input) or the stereo sum (if stereo input) with a single needle.

I hope this helps

And that is wrong. The "stereo sum" can have a random offset between 2dB to 7dB! Nobody can reproduce the same readout, depending on what material you feed through it. (again, see earlier posts of mine)

Furthermore, last time I checked your manual, it's not really properly explained either. In fact, I currently have it open - your manual is still as scarce as it can get. And once more, the RMS realtime meter is not based upon the K-System - these values are rooted with the Dorrough Patent, which Bob Katz adapted with a shifting reference point to create his K-System! This alone gives me the impression that you're not skilled in this area, and only code tools "because you can" (which is good and fine, but you still need to adhere to known standards!).

You've created a "made up standard" yet again and try to sell it (in this case, give it away for free/promote it) as accurate and "flawless" - if in fact it isn't flawless or even accurate! To me, it's a gigantic flaw! And judging by the various posts made by users (and very aggressive fans, if I might add), they don't understand that this is a design flaw and results in offset material! Therefore the learning factor of such a tool has been thrown out the window, and in worst case, people start to assume that all other tools are therefore offset and consecutively unusable.

How often do I need to point this out?

It's like you trying to build an airplane - based upon well known plans - and using the Imperial System for measurements, yet don't point it out that you did, made some changes in the process even. While others build it the same way, as accurate as they can and are then not surprised why their device can fly, and yours has some wonky behavior.



Add to that, some minor things like the "hold mode", or your marketing babble that you overhauled the code in favor for lower CPU usage, but calling it "ideal VU meter ballistics" while you didn't touch the ballistics at all.




To quote yourself again:

Otherwise please provide facts that you can understand. Thank you.

Again - are you really understanding the topic?

[Digivolt]

Is this plugin inaccurate ?

Peak RMS Studio1 18db, Mvmeter2 reports RMS as -22.5



Both "calibrated" to -18dbfs no ?

Maybe I'm doing something wrong

[TB-ProAudio]

Is this plugin inaccurate ?

Peak RMS Studio1 18db, Mvmeter2 reports RMS as -22.5



Both "calibrated" to -18dbfs no ?

Maybe I'm doing something wrong

It would be helpful to know exactly the input signal
Calibration can be quickly verified with a defined signal is used: e.g. WhiteNoise, -18dbFS peak or sinus 1kHz, -18dbFS peak.

[Digivolt]

It would be helpful to know exactly the input signal
Calibration can be quickly verified with a defined signal is used: e.g. WhiteNoise, -18dbFS peak or sinus 1kHz, -18dbFS peak.

Thanks, I just tried with 1k sine @ -18db and it shows as 0 for both vu meters

I just assumed that when playing for instance a bass sample they would all show the same readout, so what causes the difference between the vu meters to read different numbers for identical sound ?

[TB-ProAudio]

It would be helpful to know exactly the input signal
Calibration can be quickly verified with a defined signal is used: e.g. WhiteNoise, -18dbFS peak or sinus 1kHz, -18dbFS peak.

Thanks, I just tried with 1k sine @ -18db and it shows as 0 for both vu meters

I just assumed that when playing for instance a bass sample they would all show the same readout, so what causes the difference between the vu meters to read different numbers for identical sound ?

Well, the value depends on the meter ballistics. VU meters have 300ms raise/fall time.
What value do you get for white noise, -18dbFS peak? mvMeter2 should should show -2.0 VU.

[Digivolt]

What value do you get for white noise, -18dbFS peak? mvMeter2 should should show -2.0 VU.

300ms White Noise burst @ -18db = -5.1 mvmeter2 vs -3.1 in S1 VU Meter
Constant White Noise @ -18db = -5.4 mvemeter2 vs -2 in S1 VU Meter

Also to further test I downloaded Sleepy Time records VU Meter and it is showing same values as MVMeter2 so I have no idea why they're both showing vastly lower values vs S1 VU Meter and why white noise at -18db is not showing the value you suggest it should show ?

[TB-ProAudio]

Thank you.
I guess your input signal is not a full band white noise with max. peak level -18dBFS.
Maybe you use this to generate your input signal: https://www.wavtones.com/functiongenerator.php
noise: white
Level: -18
Duration: 5
44.1kHz

This file should give you the -2.0 VU with mvMeter2 and others.

[Digivolt]

Thank you.
I guess your input signal is not a full band white noise with max. peak level -18dBFS.
Maybe you use this to generate your input signal: https://www.wavtones.com/functiongenerator.php
noise: white
Level: -18
Duration: 5
44.1kHz

This file should give you the -2.0 VU with mvMeter2 and others.

I think I figured the problem

I was putting the VU meters on master channel instead of instrument/track channel

On master that white noise gives -5
On actual channel it gives -2 like you said

Interestingly though S1 VU Meter is still different, it shows -3.2 on master but 0 on channel

[The Noodlist]

...

[TB-ProAudio]

I noticed the target button is missing on the latest version, it was useful.

Just fixed with V1.0.23. Please install from our website, thank you.

[The Noodlist]

Just fixed with V1.0.23. Please install from our website, thank you.

I'm sure the error at my end, user error, thanks.

[TB-ProAudio]

Update to 2.2.0:
- UPDATE: Mac universal binaries
- NEW: free GUI scaling
- FIX: small GUI errors

[Digivolt]

Update to 2.2.0:
- UPDATE: Mac universal binaries
- NEW: free GUI scaling
- FIX: small GUI errors

Is there a way to set a default skin ? I prefer retro but it seems saving presets or saving as default only applies to the volume level algorithm and not the skin (unless this is a bug ?)

[Calagan]

Yep, same feature request. I truly like the retro skin, not because it's retro but because it's much easier to read/follow...