TBProAudio updates ABLM to 2.0 - AB Loudness Matching Plug-in for Windows and Mac OS X

VST, AU, etc. plug-in Virtual Effects discussion
User avatar
TB-ProAudio
KVRian
676 posts since 16 May, 2014 from Germany

Post Thu Mar 11, 2021 4:05 am

TBProAudio updates ABLM, a gain control which enables level matched and sample accurate A/B comparison of FX chains.

The simple GUI allows the user to concentrate on the most important ABLM functions. Now the user can detect even faster the impact of a parameter change of the plugin on the sound. And that without the mistake "louder is better".

The auto-linking is now much more robust and works in all DAWs. Now the user can create and configure much fast entire cascades of ABLM pairs.

The inverse match function has been revised. Now the sender loudness is adjusted to the receiver loudness. This is an important function for the mastering process.

Important Note: AAX Mac is temporarily unavailable until AAX support for Big Sur/Apple Silicon arrives. Pro Tools users should continue using ABLM V1.x until further notice.

Image

Intro Video: https://www.youtube.com/watch?v=Xm-48acCLPo

ABLM offers following features:
  • simple and expert GUI
  • match pre and post-FX loudness
  • match pre-FX loudness with reference level
  • 3 loudness match modes: manual, auto and gain stage
  • FX chain drive
  • up to 256 sender/receiver pairs including auto channel set/link
  • automatic latency measurement/compensation
  • 4 measurement modes: RMS, RMS +3dB, EBU R128 SL, EBU R128 ML
  • adjustable RMS measurement window
  • intelligent bypass
  • delta monitoring (sender receiver difference signal)
  • global activate/deactivate, match mode, ABFX, drive and delta monitoring
  • 4 snapshot slots
  • free GUI scaling
  • very CPU friendly
  • free update for existing ABLM customers

System Requirements:
  • Windows 7 or newer, OpenGL 2.1
  • Mac OS X 10.11 or newer, Metal
  • Compatible DAW
  • Win: VST2/VST3/AAX, 32/64 Bit
  • OS X: VST2/VST3/AAX/AU, 64 Bit
Price: 49€ (excl. VAT)

midi_transmission
KVRian
740 posts since 13 Feb, 2013

Post Thu Mar 11, 2021 1:28 pm

ABLM user here. That's a fantastic ui concept to show the signal flow. So well to understand what's going on. :clap:

One small thing. Wouldn't it make sense to change the position of 'Post FX Gain Diff' and 'Post FX Gain'?

This was the only thing were I needed a second to understand, because the difference between pre FX and post FX is shown as 'Post FX Gain Diff', but the gain is after the diff measurement in the signal flow. It's easy to fall in to the trap and ask yourself, why is the diff reduced when I add gain after it in the signal flow?

Now:
pre FX (0dB ) -> FX (does +2db to the signal) -> diff (2dB) -> post FX gain (0dB)
pre FX (0dB ) -> FX (does +2db to the signal) -> diff (0dB) -> post FX gain (-2dB)

Idea:
pre FX (0dB ) -> FX (does +2db to the signal) -> post FX gain (0dB) ->diff (2dB)
pre FX (0dB ) -> FX (does +2db to the signal) -> post FX gain (-2dB) ->diff (0dB)


I'm looking forward to give it an extensive test session.

User avatar
TB-ProAudio
KVRian

Topic Starter

676 posts since 16 May, 2014 from Germany

Post Thu Mar 11, 2021 10:32 pm

midi_transmission wrote:
Thu Mar 11, 2021 1:28 pm
ABLM user here. That's a fantastic ui concept to show the signal flow. So well to understand what's going on. :clap:

One small thing. Wouldn't it make sense to change the position of 'Post FX Gain Diff' and 'Post FX Gain'?

This was the only thing were I needed a second to understand, because the difference between pre FX and post FX is shown as 'Post FX Gain Diff', but the gain is after the diff measurement in the signal flow. It's easy to fall in to the trap and ask yourself, why is the diff reduced when I add gain after it in the signal flow?

Now:
pre FX (0dB ) -> FX (does +2db to the signal) -> diff (2dB) -> post FX gain (0dB)
pre FX (0dB ) -> FX (does +2db to the signal) -> diff (0dB) -> post FX gain (-2dB)

Idea:
pre FX (0dB ) -> FX (does +2db to the signal) -> post FX gain (0dB) ->diff (2dB)
pre FX (0dB ) -> FX (does +2db to the signal) -> post FX gain (-2dB) ->diff (0dB)


I'm looking forward to give it an extensive test session.
Thanks for your thoughts. And I can follow it. But we also wanted to show that the plugin (FX) does something with the loudness (regardless the match mode) => Post FX Gain Diff.
Then ABLM compensates the difference => Post FX Gain.

In any case we will consider your thoughts and may change it or not :wink:

midi_transmission
KVRian
740 posts since 13 Feb, 2013

Post Fri Mar 12, 2021 8:48 am

TB-ProAudio wrote:
Thu Mar 11, 2021 10:32 pm
In any case we will consider your thoughts and may change it or not :wink:
That's great, I think it would be easier to use this way, but it's not that it's that bad now. I would be happy in both cases.

I only change to the advanced ui when I want to control some advanced things like snapshots or invert gain, otherwise the new ui is a lot more fun to use and I bet especially for new users.

User avatar
TB-ProAudio
KVRian

Topic Starter

676 posts since 16 May, 2014 from Germany

Post Fri Mar 12, 2021 9:38 am

midi_transmission wrote:
Fri Mar 12, 2021 8:48 am
I only change to the advanced ui when I want to control some advanced things like snapshots or invert gain, otherwise the new ui is a lot more fun to use and I bet especially for new users.
Thank you :-) This was the plan. Keep it as simple as possible ...

tusk
KVRist
82 posts since 18 Jun, 2015

Post Thu Apr 08, 2021 4:06 pm

Can this be used to make a reference track approximate the loudness of the track I am working on? This is technically possible through routing in Bitwig but do you the plugin can cope when the two streams of audio it is comparing are radically different? If so can you recommend any settings to optimise this?

User avatar
TB-ProAudio
KVRian

Topic Starter

676 posts since 16 May, 2014 from Germany

Post Thu Apr 08, 2021 8:42 pm

tusk wrote:
Thu Apr 08, 2021 4:06 pm
Can this be used to make a reference track approximate the loudness of the track I am working on? This is technically possible through routing in Bitwig but do you the plugin can cope when the two streams of audio it is comparing are radically different? If so can you recommend any settings to optimise this?
Maybe with special routing (e.g. Reaper), but not out of the box.

User avatar
masterhiggins
KVRAF
2696 posts since 31 Dec, 2004 from People's Republic of Minnesota

Post Thu Apr 08, 2021 8:54 pm

Seems like a better implementation than the one from AudioVitamins. Going to check it out for sure.

Return to “Effects”