How to Download from AudioZ?
  • Get the best VPN on the market with 66% Discount!
Software » Windows
Plugin Alliance bx_clipper v1.0.0 Incl Patched and Keygen-R2R screenshot
Team R2R | 2023.09.08 | 32.6 MB
The ultimate clipping solution – ease of use meets uncompromised sound quality

Create competitively loud masters and maintain clarity
The Brainworx bx_clipper truncates the peaks of waveforms above a set threshold level (Ceiling). It allows you to create mixes that playback louder without increasing their peak level. Unlike a limiter, bx_clipper increases loudness while avoiding squashed pumping effects.

Your limiter’s new best friend
Applying bx_clipper to the end of your mastering chain — before or after your limiter — will help you create modern and crystal-clear mixes that feel as dense and loud as the competition. bx_clipper picks up where your limiter leaves off and bridges the gap between loud and ultra-loud.

Choose from smooth to edgy clipping effects
The clipping engine found within bx_clipper offers two modes of operation. FET mode provides a smooth and natural sound, while Diode mode delivers edgy distortion. Combined with bx_clipper's Ceiling and Knee controls, FET mode and Diode mode allow you to choose from a spectrum of soft clipping to hard clipping effects.

Maximize loudness while avoiding distortion
bx_clipper's Auto Ceiling feature analyzes the peaks in your audio signal and automatically sets the plugin's Ceiling level. The level at which the Ceiling is set will maximize perceived loudness while avoiding unwanted distortion. As a result, bx_clipper allows you to create extremely loud masters without destroying your mix.

Avoid loudness bias with equal-loudness comparisons
The Auto Trim feature provided by bx_clipper analyzes the RMS difference between the input and processed signals. Auto Trim automatically adjusts bx_clipper's output level and lets you conduct equal-loudness comparisons. It helps you tame summing-related peaks that occur in instrument groups without unbalancing your mix.

Clip the mids and sides of your mixes independently
Similar to other Brainworx products, bx_clipper features dual-mono and M/S operation modes for enhanced stereo control. You can apply varying clipping effects to the left and right channels when working with an unsymmetrical mix. Create loud masters with clarity by using the aggressive Diode mode on the sides and the softer FET mode on the center of your stereo image.

Analog warmth and digital-only features
By combining analog-modeled circuits with a digital design, bx_clipper delivers the best of both worlds. Digital-only features like Ambience allow you to audition the information lost from clipping and craft unique creative effects. Another digital-only highlight is the Wet knob, which extends beyond 100% to deliver over-fold distortion, allowing you to infuse kicks and snares with the characteristic flavor of drum synthesizers from the 80s and 90s.



download from free file storage
click to show download links



A witch says,

Don't forget updating WrapperCore :)
download from any file hoster with just one LinkSnappy account
download from more than 100 file hosters at once with LinkSnappy.

comments

  Resident 20.06.2021 320
+86
the Comment has been Removed
  Resident 15.10.2020 149
+30
the Comment has been Removed
  Member 19.12.2022 1 234
+120
apShaper produces less aliasing than this for less CPU usage with more clipping shapes available.
  Moderator 21.01.2012 2361 16056
+161471
apShaper is not a clipper as far as I understand?
  Member 22.09.2019 45
+11
Distortion/saturation plugins (apShaper, MSaturator) have built-in -clippers (hard/soft), maybe that's what they mean. But effectively he's applying saturation/distortion if using a lot of shaping. I tried apShaper but couldn't get it to hard clip properly (output is over 0dB), but MSaturator hard clipped just fine.
  Member 19.12.2022 1 234
+120
Well, most clippers, even hard clippers, go over 0db for me noticeably. I genuinely don't know why, but it's just been my experience. Minimum phase oversampling will understandably raise the level in certain frequencies due to phase shift, but even when linear phase is used this happens too. StandardClip & V-clip do this.
As for apShaper, setting "clip out" to 0db will produce a hard clipper after the soft clipper so that may help.
Generally I have a true peak limiter after a soft clipper to catch anything that slips past.
  Resident 11.08.2012 19 248
+662
This is because after upsampling, we need to downsample to the original sample rate, and that process involves a low pass filter, which Is likely to create overshoots
Come back, on the fonky track
  Member 22.09.2019 45
+11
I haven't done thorough testing, but Kazrog KClip seems to hard clip to 0dB very well. Never had issues with it.

Regarding apShaper, I tried all kinds of settings (lowest knee setting, different waveshaping models, both in/out clipping), it went noticeably above 0dB.
  Resident 11.08.2012 19 248
+662
Yes, extra steps need to be taken after downsampling in order to make sure the ceiling is not crossed. The same issue arises with limiters; Fabian from TDR for example does state that making a proper oversampled limiter is not a piece of cake!
Come back, on the fonky track
  Member 19.12.2022 1 234
+120
Most saturators are in a way a clipper (gated distortion is just an inverse clipper) but apShaper provides multiple variable knee (from infinity to 0db) clipper shapes.
  Resident 2.02.2014 1 2649
+1458
According to harmonic tests vs StandardClip, it is almost same, but 6x times less cpu usage, according to graphs and test on GS. . So yes, it can be a clipper too
.
  Member 12.01.2021 600
+295
So, I finally made some measurements and tests.

Firstly, the keygen is way easier to apply than it seems when reading it. Just play dumb (shouldn't be too difficult for some , not here, of course, not here) and follow it step by step, takes less than a minute.

Pro:
- runs on WiN7
- L/R, M/S
- two different knees
- OS without phase issues
- different graphs
- and yes, different colour schemes

Neutral:
- adds more harmonics than StandardClip (for instance)

Con:
- raises the output of the not clipped parts a bit (aka cheating)
- no real hard knee (even at 0dB it's a bit soft)
- Diode knee affects the harmonics, even at 0dB knee and raises the RMS audibly (I'd call that cheating too)
- CPU hug, needs 4x StandardClip!
- way too expensive, IMHO

The basic FET sound is pretty much like StandardClip, the additional harmonics and the slight emphasized output lead to a bit higher RMS, mainly for the unclipped parts, with Diode the difference in level is obvious.
  Member 22.09.2019 45
+11
If you're correct in that StandardClip is more transparent (fewer harmonics) and lower CPU, then bx_clipper is a no-go.

Do you know how KClip compares to StandardClip? I've heard KClip is more transparent, but have no idea of CPU use.
  Member 12.01.2021 600
+295
Standard vs K?
- Difference is inaudible for hard clipping (they almost nil).
- They have pretty different knees (K more what you'd expect).
- K has different algos, MB option and different options for online and off-line rendering.
- K needs ~ 40% more CPU (but has less latency, surprisingly).
  Member 22.09.2019 45
+11
Yup, StandardClip has slightly more aliasing but it's not very noticeable.

I'm inclined to test the CPU out myself. Did you use similar settings in oversampling etc? I didn't expect a 40% difference (which matters if you use dozens of clippers).
  Member 12.01.2021 600
+295
quote by easterDid you use similar settings in oversampling etc?

The same (4x), ofc.
  Member 22.09.2019 45
+11
I tested KClip3.5.1/StandardClip1.6 in Ableton, with 2xOS they both used 17-18% CPU, but KClip had lower latency (31 vs 64 samples).

I tested TrackLimit too (supposedly clipper-like with aggressive settings), with TruePeak off it used 9% CPU, 11 samples latency, so better than the clippers. (TruePeak on used 28%, 55 samples). Looks like I'll be trying TrackLimit more often...

So unless I'm doing something wrong, 2xOS KClip is overall better than StandardClip (the interface and additional soft modes are a bonus). I don't know if it's worse at higher OS rates though (you tested 4x).
  Member 12.01.2021 600
+295
quote by easterwith 2xOS they both used

I made some tests again and it seems the higher the OS the more CPU is used by KClip (relative to StandardClip). But this time the difference wasn't as great as before. I'm pretty sure I used the same test project.

quote by easter both used 17-18% CPU

Er, really? They're below 1% here on an outdated 3770.

But I too prefer KClip due to its additional options.
  Member 22.09.2019 45
+11
the Comment has been Removed
  Member 22.09.2019 45
+11
Make sure to subtract the base CPU that the DAW uses. I calculated base CPU by playing the audio without plugins on the test setup (for example 16 tracks playing the same audio, no plugins). I then added plugins, and subtracted base CPU from the results (e.g. 27% total - 10% base = 17% by the plugin instances).

The 17-18% is for all the instances put together (they're relative values, to compare performance.)
  Member 12.01.2021 600
+295
All good, Reaper can show the load per track, without a plugin it's 0%.
  Member 22.09.2019 45
+11
Just for clarification, you actually tried a large amount of instances of each plugin, right? (So the CPU reaches a few %, to make differences more prominent.)
  Member 12.01.2021 600
+295
Nope, I compared the load per track, so 2 tracks, not the resulting overall CPU load.
  Member 22.09.2019 45
+11
Hmm, but how do you get accurate results out of just 1 instance? Why not duplicate the same track 50 times or so?

Also, I tried KClip 3.1 2xOS with "eco" (latency went up to 58 samples), and got 11.5% CPU. (StandardClip got 17-18% CPU at 64 samples.) It seems that given similar latency, StandardClip performs worse, so the internal algo is probably less efficient than KClip.

KClip 3.5 doesn't have "eco mode" and uses much lower latency (0-43 samples for me, depending on OS), which probably explains why StandardClip sometimes gets lower CPU.
  Member 12.01.2021 600
+295
quote by easterhow do you get accurate results out of just 1 instance?

Because then it matters how the DAW (Reaper) is distributing the plugins over the CPU threads. And then the load can differ vastly.
  Member 22.09.2019 45
+11
If you use the same number of instances per plugin, they will all be equally afflicted by Reaper's threading, so you get useful relative values anyway?

If you add enough instances to cause high CPU load (20-50%), I doubt Reaper's scheduling will be a major factor.
  Member 12.01.2021 600
+295
I think this goes meanwhile waaay beyond the topic of this post which is still bx_clipper. We should either talk about this in PM (here or at AS) or you could also open a thread at AS so that other could join and/or benefit from it.
  Member 26.02.2017 68
+12
the Comment has been Removed
Si hoc legere scis nimium eruditionis habes. Fac ut vivas.
  Member 26.12.2022 182
+39
the Comment has been Removed
  Member 12.11.2018 2 90
+78
Having tried other clips such as StandardClip and Newfangled Audios Saturate. I find this clipper interesting. I honestly, like how it sounds and it will likely replace those two on the stuff I do.

Spread the Word