Reaktor Question

So I've made a little macro widget that's essentially an LFO/panel control for MIDI CC controllers. It works fine, but when I put three or four of them at once, I get start to get CPU overloads -- Reaktor shuts off and pops up a notice saying I've gone over my voices, or something. The CPU usage always hangs around 1-10% right up until the overload, so I am strongly suspicious that it is because of how I have it set up, rather than my CPU running out.

I tried switching it all to mono, that helped a bit... but I still find it hard to believe that four LFOs going out to CC messages could overload my computer. Perhaps

1) I'm sending out CC messages too fast, things get clogged. If it's this, how can I stop that? Like, ensure that it doesn't send out more than one message every N milliseconds? The "Hold" widget had warnings about inaccurate timing... maybe it'd work though?

2) It's something to do with settings, of the Controller Midi Out widget specifically. I seem to have to set them to "always active" in order to get anything to happen, what's up with that?

3) Someone plz sendspace me the Reaktor 5 manual PDF?

Any suggestions/ideas are appreciated.

You should upload the patch.

To not answer your question, it's always been my experience that Reaktor essentially sucks balls when it comes to outputting MIDI. To answer your question with another question, have you tried lowering the control rate? To try to answer your question, you might also try quantizing the output of the LFO module (or whatever the hell you're trying to use) to 7-bit values, although I'm not certain that would actually reduce the number of messages that Reaktor is trying to spew out (in fact, I'm rather doubtful it would).

yeah post the patch , ill take a look at it and try to optimize it

  On 2/23/2010 at 8:39 AM, children r r future said:

To not answer your question, it's always been my experience that Reaktor essentially sucks balls when it comes to outputting MIDI. To answer your question with another question, have you tried lowering the control rate? To try to answer your question, you might also try quantizing the output of the LFO module (or whatever the hell you're trying to use) to 7-bit values, although I'm not certain that would actually reduce the number of messages that Reaktor is trying to spew out (in fact, I'm rather doubtful it would).

you win the cake. dropping the control rate fixed the problem immediately.

p.s. what is control rate? is it specifically for midi, or is it for panel controls? just a general message rate? it'd be nice to understand what i am adjusting

control rate is the sampling rate for event processors. when we listen to digital sound we need high sampling rates like 44.1/48/96khz because our ears are very sensitive to artifacts of that type, but when we are just controlling something like the cutoff frequency of a filter with an LFO, it doesn't need to be at audio rate, because we're not going to hear filter sweeps in grains the size of 1/44100th of a second. that's why there's a much smaller "control rate" which just says that anything in reaktor that connects to a red input (event) is operating at a resolution of 400hz or whatever you have it set to.

i know it might be obvious, but back up your reaktor patches in multiple x2 places.

ive never been so upset as i was when i lost my heavily customised krypt ensemble. still dont know how it happened with the amount of drives i have

the widget in question is CCControlMKI of which there can be only one