MeldaProduction

werzel · Post by **werzel** » Sun Jun 04, 2017 5:16 pm

I've noticed that modulating the delay parameter into the upper half creates a much higher CPU hit. MDelayMB/Effects/Burning Tape, .../Something Weird, .../Flyin', .../Heavy Machinery (slightly heavy on CPU), etc. Is this something that can be fine-tuned to be more CPU friendly? What can be done to soften the zipper effect or possibly even make it more controllable?

Upon deeper inspection the CPU hit seems to greatest when the modulation is moving the delay parameter between 6000 and 10000ms (rough numbers). I tried to slow the modulation down on the presets that exhibited the problem and found the offending range. I then noticed that the CPU usage meter (in FL Studio 12.4) showed a sine wave of activity moving from about 18% at it the trough to 92% at the peak. The culprit speed seems to be around 5000ms, where FLS' CPU meter moves from white to red and crackling begins to occur.

I'm not sure how this effects other DAWs. Just passing observed information on.

werzel

jmg8 · Post by **jmg8** » Sun Jun 04, 2017 6:18 pm

Yes, I noticed that modulating the delay parameter really hits the cpu too.

werzel · Post by **werzel** » Sun Jun 04, 2017 8:33 pm

jmg8, I don't know if you have FLS or not, but they are working on a new Delay plugin themselves. This link is to their Help file page on it (that is a work in progress). https://www.image-line.com/support/FLHe ... ay%203.htm
Just in case you find anything of interest or inspiration.

Chandlerhimself · Post by **Chandlerhimself** » Mon Jun 05, 2017 3:21 am

I noticed the same thing. The CPU goes wild once you modulate things with long delay times. Perhaps we should look at work arounds or maybe Vojtech can fix it.

I haven't tried it yet, but I think vibrato works by changing the delay times. If that is the case, for longer delay times we can just use a vibrato effect before longer delays instead of modulating the times manually. If not we could put a delay tap before the delay and modulate the delay tap instead of the longer delay.

I'll check to see if these solutions work later. Also I'll try to post something I've been working on later. With the improvements to MXXX we can now share modules and we can connect them like Reaktor blocks.

jmg8 · Post by **jmg8** » Mon Jun 05, 2017 8:22 am

werzel wrote:jmg8, I don't know if you have FLS or not, but they are working on a new Delay plugin themselves. This link is to their Help file page on it (that is a work in progress). https://www.image-line.com/support/FLHe ... ay%203.htm
Just in case you find anything of interest or inspiration.

Thanks! I took a look at it for you to see if there was any interesting features. To be honest its pretty basic, MDelayMB can do a LOT more than it already.

MeldaProduction · Post by **MeldaProduction** » Mon Jun 05, 2017 1:09 pm

About the modulation of long delays - the problem is the longer the delay is, the longer buffer it needs to reinterpolate, so it takes hell of a lot of CPU every time it needs to do that. But there's quite no other solution I'm aware of. We could for instance reinterpolate only last second or something, but then you would have weird pitch changes... Or no reinterpolation at all -> brutal zipper noise.

KTlin · Post by **KTlin** » Mon Jun 05, 2017 1:23 pm

Chandlerhimself wrote:With the improvements to MXXX we can now share modules and we can connect them like Reaktor blocks.

Sorry for the off-topic question, but what do you mean by "connect them like Reaktor blocks"? Did Vojtech change the structure of MXXX and the way effect modules are connected in the v.11?

MeldaProduction

KVR Audio

MTurboDelay