posted 20 December 2010 14:54            

---

Help.kym

Hi,

i have twelve DSPs (if i remember correctly) and therefore it is hard for me to believe that this simple granular patch is too much for my processing capacity. But i hear clicks and when i look at my dsp status it's red, but only on one processor. Therefore i thought it helps when i reschedule it with ForcedProcessorAssignment, but it didn't help.
Can it be, that this patch is already too much or is there something wrong with my processor assignment?

Thanks.
Best,
Florian

IP: Logged

posted 20 December 2010 15:51            

---

I don't believe a single sound like the SampleCloud will allocate across multiple DSPs. The cause is having a high grain count with interpolation turned on. If you lower the grain count you should be ok (you can only get about half as many grains with interpolation on). To get the same total number of grains, duplicate the sound with each having a unique seed.

I also seem to remember that using the time offset could increase the overhead for the processor scheduling. At one point years ago, we'd use the time offset to help with scheduling issues around the read / write mechanism but then it was optimized away at one point (Kyma 5?). Not having a Capy any longer, I can't test this out so I may be completely wrong.

IP: Logged

posted 20 December 2010 18:21            

---

Keph is right that the SampleCloud will not split across processors. However, you can get the same effect by creating a mix of several SampleClouds (ensuring that the have different Seed values so they will trigger grains at different random start times).

If a single SampleCloud is running out of real time, try reducing the value of maxGrains and putting several SampleClouds (on the same sample) in a mix. Then Kyma can split them and schedule them on separate processors if necessary.

IP: Logged

posted 21 December 2010 10:58            

---

ok, understood, thanks!

IP: Logged

All times are CT (US)