FabFilter plugins include code that plays very loud noise if it thinks the copy is pirated

[Teksonik]

not a single word of timebombs or noise bursts

It's in the Title of the FAQ segment.....

"I'm getting noise bursts and I'm being redirected to your website with a message about piracy. What's wrong"?

Where does FF say "No we don't have any noise burst as part of our CP scheme" ?

Anyway like I said I'm grateful for the information provided in this thread. I've determined a logical and simple course of action to prevent the noise from ever occurring here.

The rest of you can continue to argue. In out. Have a nice day everybody.

[revvy]

Let's call FF and ask if the system has changed since PPC days

[Gamma-UT]

Let's call FF and ask if the system has changed since PPC days

That's madness!

Let's have pages more speculation about what is most likely an unfortunate bug in a specific plugin and not some evil plan to deafen crackers.

[whyterabbyt]

Let me run through it again. FF has admitted the noise exists.

I know they've admitted a noise exists. Could you please provide the information as to where they confirm they've listened to the OP's noise and confirmed that its their intentionally programmed 'noise burst?'

Can you provide any information that the noise wasn't caused by their intentionally programmed 'noise burst?'

That would basically be the same information, and since its only you out of the two of us who has made the assertion either way, its up to you to provide it, not me.

[grayish]

I guess you actually have to use your ears with FabFilter plugins after all...

[MirkoVanHauten]

I see the pattern here: FabFilter also never explicitely said they wouldn't erase your harddrive, so be cautious

SMH some really need to learn to read & understand and especially stop throwing in causal relationships. Btw why you think the OP in the fabfilter forum is a legit user? Took me 5 minutes to google and the only ones being upset by getting timebombed (btw not a single word about noise bursts, only deactivating the product and being redirected to the anti piracy fabfilter page) are pirates using cracked stuff since forever which ran fine until then.

[revvy]

Btw why you think the OP in the fabfilter forum is a legit user?

Dude never replies again after being told it's related to cracks....

So what we we've got here, unless I'm missing a point, is a guy on FF forum who shuts up after being told it relates to cracks, an FAQ that refers to noise bursts in the PPC era and OP sharing some views from forums that 'cannot be linked to'. Seems legit.

[excuse me please]

I usually mix at 12 (windows level). At level 16 I must hear everything clearly. So really, I can't believe damaging my ears at these levels. In other words: I'm highly sceptical about this story.
It's disturbing. Not that I'm planning to purchase FF licenses, but something does not at add here IMHO.

[MirkoVanHauten]

but something does not at add here IMHO.

Indeed. Fabfilter is also just not known for doing any punishments to their customers or pirates. I mean you can even write in their forum you've used a cracked license and they'll offer you 10% discount on your first buy

[nIGhT-SoN]

That's a nice way to get customers, I must admit. I really appreciate Fab Filter, but if this is true, it's a bit scary. It's like sitting on a bomb and the government says: as long as you pay your taxes, there is nothing to worry about. That bomb won't blow up. But if you don't, it will. That's not comforting thought, is it?

[Rockatansky]

Let's not forget that noise bursts could also be memory related. If a plugin uses variables (which they all do), the content of those variables will be stored in RAM and also retrieved from there. If anything about those values changes between storing and retrieving, possibly because of a physical corruption ('dead bit' etc.), or maybe because another application screws up a pointer address and alters memory that it shouldn't be altering, then anything could happen. Same thing if a cracker went through the binary and altered memory locations, in order to maybe outsmart a validity check (serial OK - jump to memory offset X, serial invalid - jump to memory offset Y) but screwed something up, sending the code to a completely unrelated area of memory. Say the plugin code limits/clips the signal to a float/double value between -1 and +1 (which is 0 dBfs) and stores this restricted value in memory. Say something now currupts the -1/+1 value stored in memory, its data may now represent any random value in (essentially) any range. If the plugin retrieves such a corrupted value from RAM, and processes what it expects to be between -1 and +1, but the data contained at the memory address now actually converts to a float/double number of, say, +2847292 (which is quite a bit louder than 0 dBfs)... then who knows what may happen.

[vurt]

BTW, ANY plugin can destroy your ears if the developer wasn't careful enough. That's why it's absolutely careless not to use a limiter, or have speakers which don't have a built in limiter.

Thread title is

Horrifically loud noise produced from Pro L2 out of nowhere

Pro L2 is Fabfilter's limiter plugin. So which limiter should I use to protect my hearing from problems with the Pro L2 limiter plugin?


And what if that has problems?

just put a chain of pro l2s.
i doubt theyd all fail at once...

[Fleer]

BTW, ANY plugin can destroy your ears if the developer wasn't careful enough. That's why it's absolutely careless not to use a limiter, or have speakers which don't have a built in limiter.

... or listen to the boy who cried wolf.
I put my trust in FabFilter.

[dune_rave]

reaper has settings to auto mute master or track volume if the volume level exceeds x ...

[NAD]

reaper has settings to auto mute master or track volume if the volume level exceeds x ...

Oh boy, here we go with the Reaper fanboys chiming in....
(Joking of course, Reaper is the best.)