FAC Clipper by Frederic Corvest (Released)

seawind161

@Blipsford_Baubie said:
And rest assured, I have Decimal, Substraction, and Percentages knowledge.👊

LOL!

McD

@Blipsford_Baubie said:
Reading the app description leaves (me) the impression that you can control the amount of uh…pegness above the set clip limit. Think rounded square wave from a clean sine. Sounds like you can make it out to be a hard or soft clipper.

Thanks. When I think able the major problem with clipping I worry about over heating the voice coil in a speaker. When the wave form changes values the speaker cone moves to a new position and there is impedance in the coil so the circuit current has a limit. But a coil stuck in a position when a low frequency wave is clipped becomes a virtual open wire with no resistance to current flow. So the coil gets hot and the wire melts.

In the frequency domain the clipped wave form adds hundreds of unintended freqencies and severely distorts the signal with doses of high frequency .

Anyway, I’m getting it to see if I can hear the best use cases.

thesoundtestroom

Here is a demo for Clipper with no talking, I push it hard in places.
I also placed a limiter after the clipper on the master channel so I could as bonkers as I like.

aaa

Any owners of Nebrini LoFi Vintage Clipper or ToneBoosters TB Barricade pick up this new one? I've been holding off for a good discount but maybe now is the time to choose. Curious how they stack up against each other.

I'm especially curious about how FAC Clipper performs when set to its most transparent settings, acting almost like a limiter.

Mountain_Hamlet

I just saw this tutorial on a use case for clippers and given the questions about clippers that have been posted I thought it might be nice to post this here for everybody.

I found it useful.

Luxthor

@Mountain_Hamlet said:
I just saw this tutorial on a use case for clippers and given the questions about clippers that have been posted I thought it might be nice to post this here for everybody.

Using a clipper in sound design is one thing, but using one in mastering is completely different. Even the thought of using any clipper in mastering makes me uncomfortable. 🫣

Mountain_Hamlet

@Luxthor said:

show previous quotes

@Mountain_Hamlet said:
I just saw this tutorial on a use case for clippers and given the questions about clippers that have been posted I thought it might be nice to post this here for everybody.

Using a clipper in sound design is one thing, but using one in mastering is completely different. Even the thought of using any clipper in mastering makes me uncomfortable. 🫣

I agree.

What he showed about what happens to the wave form depending on where you place the EQ change I found interesting. A bit nerdy I know, but I’ve been working on understanding my mixing process in greater detail, so this is invaluable information to me. What he was talking about was really happening pre mastering. One would hope that the peaks have been tamed by the time one reaches the mastering stage.

Luxthor

@Mountain_Hamlet said:

show previous quotes

@Luxthor said:

@Mountain_Hamlet said:
I just saw this tutorial on a use case for clippers and given the questions about clippers that have been posted I thought it might be nice to post this here for everybody.

Using a clipper in sound design is one thing, but using one in mastering is completely different. Even the thought of using any clipper in mastering makes me uncomfortable. 🫣

I agree.

What he showed about what happens to the wave form depending on where you place the EQ change I found interesting. A bit nerdy I know, but I’ve been working on understanding my mixing process in greater detail, so this is invaluable information to me. What he was talking about was really happening pre mastering. One would hope that the peaks have been tamed by the time one reaches the mastering stage.

Nicholas is an uber-nerd, did you see him manually cleaning transients sample by sample?! It’s a fantastic resource of knowledge and a good recommendation. 👍

tubespace

@Mountain_Hamlet said:

show previous quotes

@Luxthor said:

@Mountain_Hamlet said:
I just saw this tutorial on a use case for clippers and given the questions about clippers that have been posted I thought it might be nice to post this here for everybody.

Using a clipper in sound design is one thing, but using one in mastering is completely different. Even the thought of using any clipper in mastering makes me uncomfortable. 🫣

I agree.

What he showed about what happens to the wave form depending on where you place the EQ change I found interesting. A bit nerdy I know, but I’ve been working on understanding my mixing process in greater detail, so this is invaluable information to me. What he was talking about was really happening pre mastering. One would hope that the peaks have been tamed by the time one reaches the mastering stage.

That is some good advice - (gently) clipping stems rather than just one clipper at the master. Although I wonder what kind of latency having several limiters/clippers going at once will introduce in iOS.

Gavinski

@tubespace said:

show previous quotes

@Mountain_Hamlet said:

@Luxthor said:

@Mountain_Hamlet said:
I just saw this tutorial on a use case for clippers and given the questions about clippers that have been posted I thought it might be nice to post this here for everybody.

Using a clipper in sound design is one thing, but using one in mastering is completely different. Even the thought of using any clipper in mastering makes me uncomfortable. 🫣

I agree.

What he showed about what happens to the wave form depending on where you place the EQ change I found interesting. A bit nerdy I know, but I’ve been working on understanding my mixing process in greater detail, so this is invaluable information to me. What he was talking about was really happening pre mastering. One would hope that the peaks have been tamed by the time one reaches the mastering stage.

That is some good advice - (gently) clipping stems rather than just one clipper at the master. Although I wonder what kind of latency having several limiters/clippers going at once will introduce in iOS.

That is definitely a useful thing to do for sure - FAC Clipper is light on CPU, you can add a bunch of instances without increasing it too much

Mountain_Hamlet

@Gavinski said:

show previous quotes

@tubespace said:

@Mountain_Hamlet said:

@Luxthor said:

@Mountain_Hamlet said:
I just saw this tutorial on a use case for clippers and given the questions about clippers that have been posted I thought it might be nice to post this here for everybody.

Using a clipper in sound design is one thing, but using one in mastering is completely different. Even the thought of using any clipper in mastering makes me uncomfortable. 🫣

I agree.

What he showed about what happens to the wave form depending on where you place the EQ change I found interesting. A bit nerdy I know, but I’ve been working on understanding my mixing process in greater detail, so this is invaluable information to me. What he was talking about was really happening pre mastering. One would hope that the peaks have been tamed by the time one reaches the mastering stage.

That is some good advice - (gently) clipping stems rather than just one clipper at the master. Although I wonder what kind of latency having several limiters/clippers going at once will introduce in iOS.

That is definitely a useful thing to do for sure - FAC Clipper is light on CPU, you can add a bunch of instances without increasing it too much

If you’re not clipping every individual track, but just select ones that might be causing an issue I think you’ll be fine latency wise. It’s something you are going to be doing in the mix stage when you find a problem rather than in the playing stage so latency shouldn’t present too much of an issue.

Blipsford_Baubie

@Mountain_Hamlet said:

show previous quotes

@Gavinski said:

@tubespace said:

@Mountain_Hamlet said:

@Luxthor said:

@Mountain_Hamlet said:
I just saw this tutorial on a use case for clippers and given the questions about clippers that have been posted I thought it might be nice to post this here for everybody.

Using a clipper in sound design is one thing, but using one in mastering is completely different. Even the thought of using any clipper in mastering makes me uncomfortable. 🫣

I agree.

What he showed about what happens to the wave form depending on where you place the EQ change I found interesting. A bit nerdy I know, but I’ve been working on understanding my mixing process in greater detail, so this is invaluable information to me. What he was talking about was really happening pre mastering. One would hope that the peaks have been tamed by the time one reaches the mastering stage.

That is some good advice - (gently) clipping stems rather than just one clipper at the master. Although I wonder what kind of latency having several limiters/clippers going at once will introduce in iOS.

That is definitely a useful thing to do for sure - FAC Clipper is light on CPU, you can add a bunch of instances without increasing it too much

If you’re not clipping every individual track, but just select ones that might be causing an issue I think you’ll be fine latency wise. It’s something you are going to be doing in the mix stage when you find a problem rather than in the playing stage so latency shouldn’t present too much of an issue.

I would imagine that using any latency inducing plug-in during mix down would present just as much of an issue as in the playing stage. Each track or stem are still relative to each other. If the DAW doesn’t support delay compensation, it’s probably best to put a clipper on every track, even if not actually clipping most of them, just to delay everything by the same amount.
Or, if you tend to have projects with lots of tracks, only clip and render the problem track in place, then realign the phase.

Mountain_Hamlet

@Blipsford_Baubie

It would be interesting to measure exactly how much latency is actually introduced.