posted 28 August 2005 15:10            

Today I was using an array in the frequency field of a filter to choose between several different LFOs, and the sound was breaking up. The index of the array was being controlled by a hot parameter, and after some experimentation I realized that if I took out the hot parameter and just wrote in an index number the sound would be fine.

After more experimentation, the problem turned out to be that I was maxing out one of the processors. The other two were barely registering use. When I used a ForcedProcessorAssignment prototype in front of the filter to put it on another processor, all was well.

A few questions arise from this:

I concluded that as long as I have have a hot parameter as an index for an array, Kyma has to calculate all of the items in the array in case the hot parameter is switched during performance. Is this correct?

Is there any way to program this to reduce the CPU load?

Why was everything going to one processor, instead of being broken up (maybe you'd have to see the sound)?

Is the use of the ForcedProcessorAssignment going to come back and haunt me later when I try to use this sound simulaneously with other sounds, and the CPU load situation is different?

thanks,
Phil

posted 28 August 2005 16:42            

An even better approach might be to use a single LFO and put hot Arrays into its parameter fields. All the Arrays could share a single Index. That way you could switch between parameter sets (including frequency, waveform, formant, amplitude etc).