The module regularly freezes up, overloading the CPU whenever the partials knob it turned over 70%. I tested this even with only the one module loaded and it happens pretty regularly.
Sorry I missed this a while back.
This isn’t a bug, it’s just that the module’s algorithm gets more intense as partials are increased. At 48kHz it’s possible to exceed all available CPU with just this one module if you turn partials up and have frequency down. Note that you can turn partials all the way up if frequency is also up. For instance you can have Partials at 100% if Frequency is at around the “1” on the dial (assuming there is no CV inputs). But if you turn Frequency down, then the CPU usage will go up. The reason (I think) is that the higher partials are not calculated since they are out of the audio range.
If you run the MetaModule at 32kHz by changing the audio settings, then I think you can run the Additator at any settings (I haven’t done a complete test, but at first try it seems to work). Running it at 24kHz will give you more headroom.
Ok! Gotcha! I’ll try at the different settings. Just wanted to make you aware if you weren’t.
The module kicks ass, Dan. 
1 Like