Fabfilter Pro-C 3

[coroknight]

No rms control?

[bnz]

No rms control?

Yes, I wished they went a bit more into the direction of the Woodstock Open Compressor with the detection circuit parameters instead those "smooth" like black-box modes. Oh well. You can't make everyone happy I guess. Still a good update though.

[bmanic]

Now that the cat is out of the bag, I can disclose that I am indeed somewhat involved with the actual development itself (last time I was hired by FabFilter was with Pro-L2). So once you all have the demo running and want to ask any more specific questions I may be able to answer some of them.

Don't expect an unbiased review or opinion on Pro-C3 from me though, I'm way too deeply connected to the development process this time around. Having said that, those that know me, that doesn't stop me from being critical of even my own work.

I like to switch my compressor to RMS detection for pianos and sometimes busses. Pro C is supposed to be a put-it-anywhere, “ABC” compressor. Not including an option for RMS detection mode seems like a lazy and weird choice.

Yeah, I do somewhat agree. However, the original idea all that time ago, with Pro-C was to minimize the amount of controls and streamline the user experience. Thus you do not have RMS controls but you do instead have multiple different algorithms, all suitable for different things. For instance, now in Pro-C3 you can use the new 'Smooth' algorithm to easily do very gentle, easy to manage compression which is sort of similar to RMS compression. It's not directly an RMS based compressor but the end result of how it behaves behind the scenes results in similar behavior.

And in Pro-C2 you already had the 'Mastering' algorithm (which is still there in Pro-C3 of course). It behaves exactly like super gentle RMS compression with a relatively long window, yet it's much more capable than simply slapping on RMS detection on an hoping that the users set the values correctly and understand what RMS actually means and how it works.

If you do get the Pro-C3 demo, please check the 'Keys' preset folder. I made several presets that are quite specific for piano. For instance these two:

"Beautifyllu Sustained" (yes.. oops, I guess that typo will stay in the preset name )
"Invisible Sustain". These two presets represent exactly what one would normally do with RMS style of compression on piano.

Though if you are talking about "cunky / blocky" very obvious pumping sort of RMS piano compression, then there are solutions for that too but I assume you are talking about the more invisible kind as it's usually the more common thing.

Hope that helps!

[bmanic]

Probably has the same opinion. I bet his involvement is mainly around the new comp algos...

Yeah, I'm sure. He's had some prior feedback ignored on UI stuff in prior betas but I don't think that should stop us from beating up on him over it.

Well there are no FF devs here, so he's the next best (worst in his case ) person!

Unfortunately I agree with you both there.. but my power of influence when it comes to design choices for the usability and UI is virtually nil. God knows I have spoken my piece when it comes to Timeless 3 and Twin 2.. and I'm trying not to risk further employment possibilities by not becoming too obnoxious about it (hell, who am I kidding.. I do complain about these things all the time when I remember and get a chance. The filter in me was borked at birth).

Over the course of development I've sorta gotten used to the UI so I'm not as annoyed any more.. until just now when you reminded me again!

[bmanic]

Now that the cat is out of the bag, I can disclose that I am indeed somewhat involved with the actual development itself (last time I was hired by FabFilter was with Pro-L2). So once you all have the demo running and want to ask any more specific questions I may be able to answer some of them.

Can I ask whether you were part of the beta testing, using CLAP formats of Pro-C3 and Pro-Q 4, or only the VST3 formats? - And if so, which DAW you tested in?

Well, yes sort of. I was officially part of the beta test too but didn't have all that much time to actually participate as I was trying to keep my algorithms from blowing up and not bugging out. So I did sort of dropped the ball on actual serious testing. Very sorry about that..

I do have a CLAP capable DAW (Reaper) but I always used the VST3 version of the plugin. I'll check the CLAP version ASAP. Heck I don't even think I've yet installed the official release even. I'm probably a whole release candidate behind in versions.

[tumface]

I don't mind the curvy knee/range/lookahead/hold sliders. Doesn't bug me at all. The UI is a huge upgrade over v2, for me. The knobs are easier to read, there's no "don't click on this" circular-mode-notch on the knobs, the colors have better contrast, the meters are easier to read. Easy purchase, didn't have to think about it for more than a few seconds. The "Versatile" model is pretty nice! And it's nice having a single-band upwards compressor that I can dial in a little hotness without having to pull out my big guns (with latency) like Multiplicity.

I also like that they added a max lookahead setting, so that turning on lookahead at all no longer adds a full mandatory 20ms of PDC.

[coroknight]

Yeah, I do somewhat agree. However, the original idea all that time ago, with Pro-C was to minimize the amount of controls and streamline the user experience. Thus you do not have RMS controls but you do instead have multiple different algorithms, all suitable for different things.

Sorry but that is weak reasoning. And based on the rest of your comment my understanding is instead of adding one rms control they added multiple compressor types.

I guess that makes it easier to advertise “we have 14 compression algorithms!”

[Erik_Lucas]

instabuy

[Raketenbauer]

Could some other users please also test how their CLAP format is performing for them within the "Instance List" view within other DAWs? (i.e. for any projects containing multiple instances of these plugins - CLAP format only).

This is how it renders in Bitwig, all CLAP format:

[whassup]

Dan vid is up, updated the thread.

Dang yes.
I wanted to be not impressed by this comp but forgot that Dan is FabFilter's master presenter with his videos that are extraordinaire!
Now I have to download the demo.
Thanx Dan!

[bmanic]

Yeah, I do somewhat agree. However, the original idea all that time ago, with Pro-C was to minimize the amount of controls and streamline the user experience. Thus you do not have RMS controls but you do instead have multiple different algorithms, all suitable for different things.

Sorry but that is weak reasoning. And based on the rest of your comment my understanding is instead of adding one rms control they added multiple compressor types.

I guess that makes it easier to advertise “we have 14 compression algorithms!”

No, you'd be surprised how few people actually understand how RMS detection works, where to use it and why. Thus having different compression styles that excel at certain tasks is much more palatable for the majority of users. At least that is what I assume was the reasoning by FabFilter and I would agree with them on that.

As for reasoning, you haven't yet told me exactly why and what you need RMS compression for? What window size limits, what kind of signal filtering? What are you actually expecting from RMS detection? What are you comparing it to.. meaning, what are you actually missing?

[VladK]

BTW, FF also released minor version upgrades for DS (1.3) and G (1.4).

[teilo]

Something is screwed up with their price discount mechanism. I own every single FabFilter plugin, including Pro C2, and my upgrade is $69. I have never paid that much for a FF plugin upgrade.

[cryophonik]

Something is screwed up with their price discount mechanism. I own every single FabFilter plugin, including Pro C2, and my upgrade is $69. I have never paid that much for a FF plugin upgrade.

Same here, although as I mentioned in another thread yesterday, my Pro-Q4 upgrade was only slightly less.

[fisherKing]

Something is screwed up with their price discount mechanism. I own every single FabFilter plugin, including Pro C2, and my upgrade is $69. I have never paid that much for a FF plugin upgrade.

that's what it cost (i just purchased, upgrading from C2). they're doing the work, let them get paid....