TBProAudio releases TBPAClip - clip and saturation plugin for Windows and Mac OS X

[TB-ProAudio]

TBProAudio releases TBPAClip, a DAW plugin for all clip and saturation tasks in todays audio productions.



Intro Video:

TBPAClip is designed from scratch for modern clip and saturation tasks, used either with individual track, bus or master track.
• single-band/multi-band saturator/clipper in one plugin
• advanced symmetric and asymmetric clipping functions
• saturation before clipping, both optional
• extensive clip tone control
• x256 oversampling for aliasing free processing
• parameter modulation at audio rate
• Simple and fast workflow to achieve clipping and saturation goals.

Features:

• single/multi band clipper
• single/dual clipper operation
• 6 clip types
• advanced clip response
• single/multiband saturator
• 6 saturation types
• up to x256 oversampling
• flexible gain-staging
• saturation and clip score
• EBU R128 measurement
• mid/side processing
• non OS final clipper
• DC blocker
• extensive monitoring options like mid/side, delta and unity gain
• smart silence processing
• parameter A/B
• parameter modulation at audio rate
• free GUI scaling

System requirements:

• Windows 7 or newer
• Mac OS X 10.11 or newer
• OpenGL2
• compatible DAW
• Win: VST2/VST3/AAX/CLAP, 32/64 Bit
• OS X: VST2/VST3/AAX/AU/CLAP, 64 Bit

Price: 39€

[billinder33]

I don't need another clipper, but I love Impress3 so much that I'm definitely going to demo this. My current go-to clipper is Kclip. The visual feedback in this looks exactly like what I always wished KClip had.

2 questions:
1. Do you know if one of the clipping algos in TBPAClip is similar or the same as the default 'Smooth' in KClip?
2. One of the reasons I've stuck with KClip over BX_clipper is due to KClip's much lower CPU consumption. Have you performance tested TBPAClip in Single Band mode against KClip? Or alternatively can you share any experiences with performance testing you've done?

[TB-ProAudio]

I don't need another clipper, but I love Impress3 so much that I'm definitely going to demo this. My current go-to clipper is Kclip. The visual feedback in this looks exactly like what I always wished KClip had.

2 questions:
1. Do you know if one of the clipping algos in TBPAClip is similar or the same as the default 'Smooth' in KClip?
2. One of the reasons I've stuck with KClip over BX_clipper is due to KClip's much lower CPU consumption. Have you performance tested TBPAClip in Single Band mode against KClip? Or alternatively can you share any experiences with performance testing you've done?

Thank you.

1) You can build every possible clip curve in advanced mode.
2) Please be assured that we have looked at all relevant market competitors. We have further developed the positive features and added a few new features

[mcbpete]

Should 'x265' be 'x256' or is the oversampling 9 times betterer than others

[TB-ProAudio]

Should 'x265' be 'x256' or is the oversampling 9 times betterer than others

Sorry, typo. Corrected.

[SeeingInMidi]

is the limiting/clipping mode in slm2 in here too?

[TB-ProAudio]

is the limiting/clipping mode in slm2 in here too?

No. SLM2 is wave length limiting (including latency).
TBPAClip has no latency (if OS set to 1x).

[SeeingInMidi]

is the limiting/clipping mode in slm2 in here too?

No. SLM2 is wave length limiting (including latency).
TBPAClip has no latency (if OS set to 1x).

Ah, I was hoping the algorithm would be in there so I could take advantage of the multiband,

[oobesan]

Looks sweet, definitely going to pick this up

[Zeisner]

Well, there goes my plan to not buy new plugins...

[billinder33]

@TB, I'm digging the multiband mode, but why is the final hard clipping stage disabled in that mode?

I love what you can do creatively in multiband, but I still need it to clip the final output. Ideally without adding a second instance at the end of the FX chain.

[TB-ProAudio]

@TB, I'm digging the multiband mode, but why is the final hard clipping stage disabled in that mode?

I love what you can do creatively in multiband, but I still need it to clip the final output. Ideally without adding a second instance at the end of the FX chain.

Because in multi-band there is no dedicated ceil level. We may add this in a future update.
In single-band mode the level of the final hard clipper is controlled by the ceil level.

[billinder33]

@TB, I'm digging the multiband mode, but why is the final hard clipping stage disabled in that mode?

I love what you can do creatively in multiband, but I still need it to clip the final output. Ideally without adding a second instance at the end of the FX chain.

Because in multi-band there is no dedicated ceil level. We may add this in a future update.
In single-band mode the level of the final hard clipper is controlled by the ceil level.

I think it's an important feature if you want to take on something like Krafter. I was getting Krafter-like results with TBPAClip, but Krafter knocks down the peak overs before output, so hard to directly compare without a second instance added to the chain. Having that final clip stage option in MB mode would definitely improve workflow and make it more useful.

I also used the MB mode to juice up the midrange of synth last night. Very cool. Again, biggest complaint was that I had to follow it with a second clipper to avoid peak overs. No CPU issues in single or MB mode (Mac M1/Bitwig). If I push it hard in MB mode there is a noticeable bump in CPU % (maybe up to 10%), but nothing crazy or unexpected. Overall it seems very efficient.

I haven't yet tried it on drums for standard end-of-FX-chain clipping on peaks, but I'm guessing it would perform as well as KClip, definitely with better visual feedback. Will spend more time with it this weekend. I don't really need another clipper, but I boy do want this. The visual feedback is excellent and I'm glad you borrowed from the general UI concepts of Impress 3. Nice work!!!

[TB-ProAudio]

@TB, I'm digging the multiband mode, but why is the final hard clipping stage disabled in that mode?

I love what you can do creatively in multiband, but I still need it to clip the final output. Ideally without adding a second instance at the end of the FX chain.

Because in multi-band there is no dedicated ceil level. We may add this in a future update.
In single-band mode the level of the final hard clipper is controlled by the ceil level.

I think it's an important feature if you want to take on something like Krafter. I was getting Krafter-like results with TBPAClip, but Krafter knocks down the peak overs before output, so hard to directly compare without a second instance added to the chain. Having that final clip stage option in MB mode would definitely improve workflow and make it more useful.

I also used the MB mode to juice up the midrange of synth last night. Very cool. Again, biggest complaint was that I had to follow it with a second clipper to avoid peak overs. No CPU issues in single or MB mode (Mac M1/Bitwig). If I push it hard in MB mode there is a noticeable bump in CPU % (maybe up to 10%), but nothing crazy or unexpected. Overall it seems very efficient.

I haven't yet tried it on drums for standard end-of-FX-chain clipping on peaks, but I'm guessing it would perform as well as KClip, definitely with better visual feedback. Will spend more time with it this weekend. I don't really need another clipper, but I boy do want this. The visual feedback is excellent and I'm glad you borrowed from the general UI concepts of Impress 3. Nice work!!!

OK, got the point. We will see how to integrate this.

[TB-ProAudio]

Update 1.0.2:
- NEW: added multi-band final clipper with dedicated ceil level
- UPDATE: small GUI changes