Creative Bundle spikes

[woodsdenis]

First of all what an amazing set of plugins, especially for total mangling. For the sale price this is a total no brainer.


I have noticed on first opening a plugin in Studio One when I move one of the Easy knobs the CPU spikes, after that first touch its fine, not a deal breaker but an annoyance. There is no way to accurately repeat this either, It happened when I moved 'Shape' on the MMultiRingMod the first time, I removed the plug and reloaded it and moving the 'Shape' did not spike the CPU. Go figure

Edit Here is a repeatable one in all plugins in single band mode on all multi plugin, altering the band volume or pan in the top graphic area spikes the CPU, some worse than others, but most maxing out and causing audible glitches.

I dont notice this in Live 9 (latest rev)

[MeldaProduction]

Thank you for the info. I'll check it out. Anyway there will be some reasonable improvements on the Mac versions in the next update, so hopefully it will help. It won't technically reduce CPU requirements, as there's not really much to optimize anymore, but the multithreading engine on OSX is rather clumsy and there was a bottleneck, which shall be improved. Recently there was this report about MRhythmizer vs. MMultibandRhythmizer, where we got from 10% to 3%, so a big difference. So I'm assuming this will help this too.

[woodsdenis]

Tx for reply, they are all very reasonable CPU wise when in operation, it's just when moving some parameters. As I said moving the band volume or pan of a single band using the top graphical interface is always repeatable.

TBH I thought that having a Multiband fx processor was a bit of a gimmick for most applications, but it really opens up tons of really creative avenues, fantastic work. Now let it be on sale next so I can snap it up !

[MeldaProduction]

The problem is with synchronization - most of the OSX stuff is really like ancient Unix crap from 70ths (and then the new stuff always dysfunctional and getting deprecated, so rather hands away from that...), so it is really hard to make something work reasonably on OSX. This current bug (or rather nonideal situation) is no taking away CPU, but rather leaving it for other tasks... technical crap . But it will get better.

And thank you!