Pops/Crackles on homemade Zebra2 Patches

[Senamental]

Hey all,

My name is Nick Sena, I'm primarily a film/tv composer and this is my first post on the u-he board so bear with me. I just bought Zebra2 the other day, started designing sounds and mind blown. Anyway, one sound that I've got going is an arp with 2 OSC, 2 filters and a comb filter and maybe 12-16 different parameters controlled by a few LFOs and few envelopes. Nothing in the sound should create pops but I'm getting a lot of them - tiny inconsistent almost crackles. I'm guessing this is a computer performance issue but I wanted to ask the community first. I'm running a late 2015 iMac 32gb ram, ssd, 4ghz i7 and have never had a soft synth pops and click because of performance. Zebra2 feels like a heavy hitter though with processer power. The other sound thats creating more logical pops is a bass sound thats popping randomly on the attack of the note although none of the envelopes would suggest a pop. There are a few MSEG's on modulation parameters that look to be the culprits but taking them off still leaves me with pops. I'm pretty confused here so anyway - should I post the patches? Anyone have any tips/ideas here? Thanks!!

[Funkybot's Evil Twin]

Zebra2 (note: the title of your post says Diva2) is generally pretty efficient for a U-he synth, but depending on what you're doing in a patch, things can get hairy (in terms of CPU use). Really hard to say without trying the patches, or knowing more about what else is going on. For instance, what else is happening in your DAW/host? Is it an empty project, or is there other stuff using up CPU?

[Senamental]

Thanks for the reply. I’m using logic - within a template of many other sounds - I wiped about half my template but still noticed the sounds. I guess next step is to wipe everything but the patch..

[Funkybot's Evil Twin]

Thanks for the reply. I’m using logic - within a template of many other sounds - I wiped about half my template but still noticed the sounds. I guess next step is to wipe everything but the patch..

Depending on how Logic handles core balancing, and your particular Logic project, there’s a chance that one or more cores is being maxed out. Hence why I asked. Let’s say you had two instances of Zebra2 running on two separate tracks, then into the master. Your DAW would likely split those up between two cores. But if those two instances were being bussed and processed together with some other effects, the DAW may end up running that entire signal chain on the same core and over-taxing the CPU. Hence why it’s best to check in an empty project just as a point of reference.