MSF - loud thump noise when adjusting some FX parameters from zero to something

[Sampleconstruct]

Several FX modules produce loud thump noises when dialing in values other than 0, eg assigning flanger mix to a Macro with a range from 0 – 100%, automating the Macro will produce a loud thump noise at the transition from 0 -> 0.01. I noticed the same in the Turbo EQ when assigning frequency gain to Macros.

[DarkStar]

Could you post the parameter settings that demonstrate the problem?

You probably know this, but, jut in case: click the Copy button in the Toolbar on the right-hand side, then paste it into a Code box here.

[Sampleconstruct]

Could you post the parameter settings that demonstrate the problem?

You probably know this, but, jut in case: click the Copy button in the Toolbar on the right-hand side, then paste it into a Code box here.

Sure, here it comes, this thump noise happens when the flanger is running in tape mode, just dial in the Macro on the easy screen in this preset to hear it.

Code: Select all

$eNqVll1T6joUhu-5FZlwq9BvykzbPboFD7NFOZTt9lzGdgEZ06aTpB49v-5MUkBEhXrTSZNnrfVm5WtFP14Khp5BSMrLGNs9CyMoM57TchXjWi3PQ-wj6UTTlNdlPiaZ4uJVglK0XEnUjbGNUfea8UfC5II8xtjB6GctBJRqJkCCmlzF+AqWpGYKo1FOFRcp-Q9ibAe2fzZ0-f3eEZGvMbat0DsLQh+jv-7+XUlSVMyosTC6oQVVIEzYm3laMaoUGFM7xo43tHq279qBYwWH406MA8frhV4QuoOh52M0JS8347tLxrOnRpHrYDStmaIzIkgBCoT8yRkjlYTcRL-fpin0nYEb4CRK68cZq1e03GQmiZrf9H2GPg2VAoNMQd5YxNg6s-DWXm4baFwzdksKiPFFnlNFnwEZh-JpUhpR7wcxejC9-+jvF2q6qRJ1pmoBe9P7QmU-ifqNk11D7lpbv0nU-5CIzl5uHr4Q8lnAb6dlzEi5AqGz8q6jVSauoFJrg3XHAPkjyZ5ibPX8QYBRd8pziPGCVIBRt1oTCTldLvW444UYdec6jqP-Lcv1htbQt20rDD2MuoIoiPG51fP8cDiwLMtzXe0yJaoWRJlNZPUcs+M+SUISTSdXk7k+P-0kkmtSAUoXo9lsPkpHC623-9kifG+hHpJONCqf7SRaCCg44+kXcQxkWKcN6zSs24Z1G9Zrw3oN67dh-YYN2rBBww7asIOGDduwYdKJmptxVD6jC6VI9mRwvfRuEGI0BwZEmv+BZw+HVuANPWewG9jQ51YvHAYYpQXnat1chT3H9NRSEX1IbHxS0U5K0oluxnc2uoFypTe-PnMHtCGck4R7kvBOEv5JIjhJDE4S4XFiTsqcF+YkkFIuuSjMGUWj2-stGJokbsGtidPWxNmZuG1N3J2J19ZEH5Ff8CozwqDFbN7QNzOnvZme0z0wnlHVOuQBf+DA+aaDfQWHaOfNla5EZC3gGEJVtr6EMj-CTHn+Zw3AjiALWjwKGHhHkEsBRK0t5wgyeqm0YspL2z6C3XIFd8vlR+Ka0by5PD6OHRQ4yUGHha4Fr6sYjx8wuv49aWqz5iW81avCMHr-9-4VntIXjNIKNhVT+q-O64JqRBdQhNV7rcbRDEQGpZL6kd7KMO+7eV9j7GG0698Ee0DnaPfuo3NknnGMNgZWzzdb5WBmH3pk0okuMl01NaUq2pZDCwGNSj375nL9SRSsuHidKCgm5ZL3k2hT5n60akRqCRezxrNWsx9JBxYVmpsqQRdZnWhqFDlJdFerKbqismLkdUpeaFEXmyv8D83VeppEKa9FBmgmYEmZArEpjnWQLdLfuutE-c9Kd5l0-ge9pr8B

[DarkStar]

Got it. thank you. Yes, I can confirm the thump - I get it here too, when changing the MP value from or to 0.00%.

[vectorwarrior]

I haven't checked out this specific case, but I have had this happen myself when automating a low shelf eq back to zero. If I set if to plus or minus 0.1db or something very close to zero, there is no click.

I presume melda has an optimization that disables processes that shouldn't be doing anything. When that happens it can cause a click, that's my guess anyway. I wonder if that's what's happening here.

[MeldaProduction]

Exactly, it's an optimization, that disables some processing, when it wouldn't in fact do anything. But there may for example be a phase shift caused by some filters etc. In that case I'd simply set the minimum to like 0.001% (which is pretty much 0%) and that will do the trick.

[DarkStar]

Would it be better to code that into the software, rather than us having to remember to set the minimum to 0.001%?

[vectorwarrior]

I don't know what you mean by code it into the software. They've deliberately added this feature to CPU optimize things. The problem is when things go from active to disabled. What might be nice is a setting to disable this, in cases where we can't be bothered to track down what's causing the click and don't care about the optimization, we just need a clean render.

[jmg8]

Or what about a momentary volume dip of the wet signal at that point. It wouldn't be noticeable if the wet ratio is 0.001% so this would be surly preferred over the click, right?

[mevla]

I don't know what you mean by code it into the software. They've deliberately added this feature to CPU optimize things.

Optimization-wise it might not be a big deal to filter just before the action. Eg:

If user asks for 0
make it 0.001
done

But the 'if' is a penalty for sure. Repeated too often it can bog down the app, the whole computer ! It could be done via a lookup table, or maybe using a Pattern, although the 'if' remains very simple to add.

That would be what was suggested.

[Sampleconstruct]

Or what about a momentary volume dip of the wet signal at that point. It wouldn't be noticeable if the wet ratio is 0.001% so this would be surly preferred over the click, right?

That would be my favorite solution.

[vectorwarrior]

I think a tiny Crossfade from wet to dry before disabling the effect may cause less of a click. But the phase difference is going to have an artifact when switching regardless of how you handle it I guess.

[MeldaProduction]

I'm afraid none of this is a feasible solution (there are always problematic scenarios). So, assuming it is an optimization, then I can remove the optimization, that's about it. Let's see, it's all about 0% depth, so it probably won't matter.

[Sampleconstruct]

The same thing occurs in TurboEQ, today I used a passive EQ and wanted to assign a Macro with a range of -12 to +12 dB for the high frequency range, as soon as the Macro knob reaches the middle position (50%), there is a loud click noise when the range switches from -1 to 0 to +1 dB. So I skipped that idea and only used a high cut EQ.

[MeldaProduction]

The same thing occurs in TurboEQ, today I used a passive EQ and wanted to assign a Macro with a range of -12 to +12 dB for the high frequency range, as soon as the Macro knob reaches the middle position (50%), there is a loud click noise when the range switches from -1 to 0 to +1 dB. So I skipped that idea and only used a high cut EQ.

It is probably enabling/disabling some filters, most likely nothing that can be fixed I'm afraid. I'll check though. Anyways the flanger thingy should be fixed in 14.04.