Denorm bug /w Overdrive FX

[Jeremy_NSL]

I think I found a denormalization issue with the overdrive fx. My track had really high cpu and I narrowed the offending plugin down to rhino, which was strange cause I was running a simple 1osc patch. BUT overdrive and stereo delay were enabled.

Turning overdrive off instantly brought my cpu down from around 25% on idle to 5% or so. Also playing a note actually lowers cpu - isnt that a classic denorm sign? Thinking it might be Tracktion at fault, I also tried Chainer. Same results. Also if I turn off the 'remove DC' option under these circumstances, cpu usage shoots even higher, to 70%, and back down to normal if I play a few notes. More strange behaviour with overdrive enabled: sometimes notes won't sound unless 'serial mode' is unchecked, regardless of what the other fx is.

My system is a p4 2.1ghz, running win2k and the latest version of Tracktion + Chainer. The patch in particular is 'Clavinet' from the Analog Polysynth pack, but I tried a few more patchs and it doesn't seem patch-dependent. Hope all this helps you track it down, 'Tick

[Big Tick]

Hi,

I couldn't find any denormal problem with that fx. Indeed, it uses some cpu, but nothing unreasonable given the amazing amount of computation required

By the way, the preset you mention doesn't use the overdrive. Or am I missing something ?
Could you email me the offending preset, and I'll stress-test it ?
Cheers,
'Tick

[Jeremy_NSL]

Yeah, I added overdrive to that preset. I'll email it to you.

I experienced another weird occurance while testing this preset. It seems not to save the fx settings for the 2nd fx, whether its overdrive or anything else.

eg: I have overdrive set to have no hp or lp, a gain and drive of both 50, and a wet/dry mix of 50. Then I save the patch to a .fxp file. I load the fxp file in a new slot. The overdrive settings are all changed - hp filter up to 99, and lp to 32, wet/dry at 99, etc. All operations were on the internal bank. Something strange is going on here...

[Big Tick]

That's because for this preset, FX2 parameters are mapped to user sliders - and user slider values override their assigned parameters. When you change the FX type, the old user assignments are still in action...

'Tick

[Jeremy_NSL]

I never would have thought of that. Thanks for the assist.

[Big Tick]

You're not the first one to get fooled by this little trick
'Tick