TBProAudio releases dpMeter II - Free Digital Precision Meter Plugin including Loudness Matching

[Lesha]

I just think AVG should be set as default.

[TB-ProAudio]

I just think AVG should be set as default.

No prob, will go into next version, thank you.

[Lesha]

I just think AVG should be set as default.

No prob, will go into next version, thank you.

Thank you

[MogwaiBoy]

Hi - I'm experiencing the same issue that was happening with the original dpMeter. Specs: FL Studio 12.2 64-bit, Windows 10, dpMeter II 64-bit VST2.

When I launch dpMeter II on the master bus it automatically increases the signal volume dramatically, pushing my peaks above 0db into clipping. I can reduce the input Gain level to compensate but then that throws off all the readings. As soon as I disable the plugin the volume returns to normal.

Trying the VST3 version in FL Studio just says "The plugin is disabled because of an error during processing" whilst passing nothing through the plugin.

Tried 32-bit versions also with no luck - then they took down (crashed) FL Studio.

I'm going to have to sit this one out until it's working in my DAW. This looks like the perfect tool for my uses and I really hope it gets tidied up.

[TB-ProAudio]

When I launch dpMeter II on the master bus it automatically increases the signal volume dramatically, pushing my peaks above 0db into clipping. I can reduce the input Gain level to compensate but then that throws off all the readings. As soon as I disable the plugin the volume returns to normal.

Thank you for this feedback. Will be fixed very soon with next version.

[TB-ProAudio]

Update to V1.2.3
- Limit output channel to channel config (FL Studio fix)
- Reset parameter available for automation
- RMS mode: avg as default

[planetearth]

When I launch dpMeter II on the master bus it automatically increases the signal volume dramatically, pushing my peaks above 0db into clipping. I can reduce the input Gain level to compensate but then that throws off all the readings. As soon as I disable the plugin the volume returns to normal.

Thank you for this feedback. Will be fixed very soon with next version.

That happened to me as well, in Sonar X3 Producer (64-bit). I simply turned off the plug-in when I saved my default template. When I then loaded it, I could turn it on with no problem. If it was already on when I loaded the template, it drastically increased the volume.

I'll try the latest version to see if your fix also helps Sonar users.

Thanks again for your great service and quick turn-around on these issues!

Steve

EDIT: On the Download page of your website, there's a typo where it says "Systemrequirements". Thought you might want to know.

[MogwaiBoy]

TBProAudio you win the award for fastest Customer-Feedback-to-Update time ever! Thank you - I will try it out <3

[xx JPRacer xx]

Sorry, i´m not a fan of Facebook...

[TB-ProAudio]

TBProAudio you win the award for fastest Customer-Feedback-to-Update time ever! Thank you - I will try it out <3

Thank you for your nice feedback!

[twoodts]

Has anyone managed to get this to show up in Adobe Premiere or Audition (CC version)? This plugin works fine in Reaper but refuses to show up in previously mentioned programs when I scan the plugin folders. Am I missing something or does this fine plugin not work with Adobe software?

I'm using Windows 10 Pro, vst3 64-bit version of the plugin.

I know I can use the Adobe's Loudness Radar but I'd rather use dpMeter instead.

[TB-ProAudio]

We will check this, thank you.

[TB-ProAudio]

Update to V1.2.4: AU Ableton output channel fix

[MogwaiBoy]

Just want to say this plugin is in my "Master Bus Favourites" folder permanently. It works beautifully in FL Studio now. Thank you TB for offering this!

[planetearth]

Just want to say this plugin is in my "Master Bus Favourites" folder permanently. It works beautifully in FL Studio now. Thank you TB for offering this!

+1

Steve