KVR Audio

Niowiad · Post by **Niowiad** » Sat Jul 25, 2020 4:36 pm

It would be useful to know which dBFS value we're talking about.

I have ZERO cracked software but if for some kind of update/malfunction they're interpreted by the PC as cracked, that would suck

For what it's worth I keep REAPER's auto-mute option when any track reaches +10 dBFS

Teksonik · Post by **Teksonik** » Sat Jul 25, 2020 4:37 pm

chk071 wrote: Sat Jul 25, 2020 4:28 pm Ok, so the sound is "the most horrifically loud and distorted noise imaginable. Truly ear bursting." just because someone says so. That's some truly factualy stuff right there.

And you don't believe them just because it was the first post of the person who reported this issue? That's some truly illogical thinking there......

Do you even own any FF plugins so you too might have to worry about the noise if CP is ever broken ?

At any rate I only own FF Twin and Timeless 2 and the first thing I'm going to do when I boot the studio this morning is to make sure they are still authorized since it's been awhile since I've used either one.

I'll do the same thing after each major Winblows update just out of caution to ensure the noise won't be an issue here.

chk071 · Post by **chk071** » Sat Jul 25, 2020 4:39 pm

I don't believe anything. I know that it's BS.

Teksonik · Post by **Teksonik** » Sat Jul 25, 2020 4:39 pm

whyterabbyt wrote: Sat Jul 25, 2020 4:35 pm
Teksonik wrote: Sat Jul 25, 2020 4:24 pm There is a huge difference between accidental noises caused by plugins and a noise that is intentionally programmed into the code.
Yeah, the intentional ones will be far more controlled.

I meant a difference in concept. I thought that would be obvious. Sorry I overestimated.

frizzbee · Post by **frizzbee** » Sat Jul 25, 2020 4:40 pm

rumors, rumors, rumors, only because someone used a buggy cracked plugin version... go ahead, do it, change a byte in the binary and see what happens. i'll take the fun out of it: nothing will happen. you can't even load the plugin anymore

whyterabbyt · Post by **whyterabbyt** » Sat Jul 25, 2020 4:43 pm

chk071 wrote: Sat Jul 25, 2020 4:15 pm 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?

whyterabbyt · Post by **whyterabbyt** » Sat Jul 25, 2020 4:44 pm

Teksonik wrote: Sat Jul 25, 2020 4:39 pm
whyterabbyt wrote: Sat Jul 25, 2020 4:35 pm
Teksonik wrote: Sat Jul 25, 2020 4:24 pm There is a huge difference between accidental noises caused by plugins and a noise that is intentionally programmed into the code.
Yeah, the intentional ones will be far more controlled.
I meant a difference in concept. I thought that would be obvious. Sorry I overestimated.

Obvious enough not to need stated, yes.

Teksonik · Post by **Teksonik** » Sat Jul 25, 2020 4:46 pm

chk071 wrote: Sat Jul 25, 2020 4:39 pm I don't believe anything. I know that it's BS.

And how do you know ? Based on what facts ? Based on what information ?

Let me run through it again. FF has admitted the noise exists. Windows 10 updates have broken CP on some plugins here. Unlike you I actually own FF plugins so going forward I will make sure to check they are still authorized after any major Win 10 update in the unlikely event that CP has been broken so I can avoid any chance the noise will occur here.

So I am grateful for the information provided in the OP whether the extent of the noise is exaggerated or not.

Pretty simple right ?

frizzbee · Post by **frizzbee** » Sat Jul 25, 2020 4:49 pm

Teksonik wrote: Sat Jul 25, 2020 4:46 pm
chk071 wrote: Sat Jul 25, 2020 4:39 pm I don't believe anything. I know that it's BS.
And how do you know ? Based on what facts ? Based on what information ?

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

bullshit. where? in the faq where they only explain the piracy warning? have you actually tried to alter the binary like i did before posting?

also adding https://www.fabfilter.com/forum/1747/pr ... ?replies=7:

Just to be clear: unlike some other plugins, our demo versions are fully functional and do not generate noise bursts.

it will only go into demo mode if no license if found. no need to worry. don't use buggy cracks, then there are no problems.

whyterabbyt · Post by **whyterabbyt** » Sat Jul 25, 2020 4:49 pm

Teksonik wrote: Sat Jul 25, 2020 4:46 pm 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?'

Teksonik · Post by **Teksonik** » Sat Jul 25, 2020 4:56 pm

frizzbee wrote: Sat Jul 25, 2020 4:49 pm bullshit. where?

https://www.fabfilter.com/support/faq/# ... hats-wrong

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

"Otherwise, could it be that you have ever installed unofficial versions of our plug-ins, and that some of these are still in your plug-ins folder"?

frizzbee · Post by **frizzbee** » Sat Jul 25, 2020 5:00 pm

Teksonik wrote: Sat Jul 25, 2020 4:56 pm
frizzbee wrote: Sat Jul 25, 2020 4:49 pm bullshit. where?
https://www.fabfilter.com/support/faq/# ... hats-wrong

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

"Otherwise, could it be that you have ever installed unofficial versions of our plug-ins, and that some of these are still in your plug-ins folder"?

Do you possibly use tools like lipo or Monoligual to strip the PowerPC binary from the plug-ins? Or any other tool that might alter the binary? This will trigger the piracy warning...

not a single word of timebombs or noise bursts

schpaeckulum · Post by **schpaeckulum** » Sat Jul 25, 2020 5:02 pm

Ahem, it's obvious that the post the OP is referring to was made by a legit user. He is complaining about this issue on FabFilter's very forum and is going 'WTF went wrong?!' Please try to pay attention!
The noise could be triggered not by an altered binary, but by the plugin losing the link to the registry information, which could happen e.g. if you log off with your DAW open and project loaded, then log on again and start playing immediately - in this case plugins may have failed to 'call' their registry info - assume they're not registered and - there you go, loud noise burst, especially if Pro-L is "pumped" from its Gain parameter.
THAT'S what the complaint is about, NOT that he's whining about his pirated copy having triggered a timebomb. IOW, a valid issue. I assume this has been/will be addressed.

Teksonik · Post by **Teksonik** » Sat Jul 25, 2020 5:02 pm

whyterabbyt wrote: Sat Jul 25, 2020 4:49 pm
Teksonik wrote: Sat Jul 25, 2020 4:46 pm 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?'

I don't see any denial from FF.

Like I said given the information in this thread out of an abundance of caution I'll make sure to check that the FF plugins I own are still authorized in the unlikely event their CP is broken during a Win10 update.

That way I'll be sure to never have to experience the noise. Certainly that's logical no ?

DocSnyder · Post by **DocSnyder** » Sat Jul 25, 2020 5:04 pm

schpaeckulum wrote: Sat Jul 25, 2020 5:02 pm Ahem, it's obvious that the post the OP is referring to was made by a legit user. He is complaining about this issue on FabFilter's very forum and is going 'WTF went wrong?!' Please try to pay attention!
The noise could be triggered not by an altered binary, but by the plugin losing the link to the registry information, which could happen e.g. if you log off with your DAW open and project loaded, then log on again and start playing immediately - in this case plugins may have failed to 'call' their registry info assume they're not registered and - there you go, loud noise burst, especially if Pro-L is "pumped" from its Gain parameter.
THAT'S what the complaint is about, NOT that he's whining about his pirated copy having triggered a timebomb. IOW, a valid issue. I assume this has been/will be addressed.

Disagree. I just tried and removed license information during work. If at all (took some tries) it switches to demo mode.

Lots of paranoia and a faq from power pc times - that's kvr. You do not use cracks, then all is fine. Altered binaries or licenses due to an windows update (crazy unprobable thought) will lead to not being able to load the plugin at all (altered binary) or only in demo mode (altered license).

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