posted 15 October 2004 22:09            

I'm using Kyma for some time now and I've noticed that Kyma is using LOTS of CPU (something like 80%), even when no sound is processed. It seems it is a problem with the management of windows, since the CPU usage turns down to about 5% when I click on the menu bar, for instance, to desactivate the Kyma window. Also, if I close most of the windows inside Kyma (timeline, VCS, etc.) the CPU usage gets lower. It looks like there is some infinite loop that calls the windows all the time, even when there is no activity (just watching an info window for eg).

This is overheating the CPU so the fan of my laptop is running most of the time, which is a real problem for live performance.

My configuration: Kyma X.09 with Penthium III 1GHz running Windows XP Home SP1.

I wonder if other people have the same problem...

Many thanks

posted 04 November 2004 00:45            

Sorry for my late answer.

Closing the DSP Status Window does'n make any real difference. Usually, closing the VCS window is more efficient in reducing the CPU usage. But of course, this is not a "solution"!

Again, this is happening even when no Sound is playing, which makes me thinking it is a bug in the program. I'm wondering if other people are experimenting the same problem?

Best

posted 04 November 2004 23:09            

Look, I love Kyma and I wouldn't care it uses that much CPU, but the problem is that it is causing my laptop to overheat and it even starts making some audible noise in the high frequencies, like to say "please don't push me so hard, or I will collapse soon"!

I don't know if this can be useful to make Kyma use less CPU in the future, but I noted some values that help tracking which are the windows that "eat" so much CPU. When no Timeline is used, if I close the VCS then the CPU usage comes down from above 80% to around 50%, and if I close both the VCS and the DSP Status then it comes down to around 15%, which is a more understandable value for the idle state. Then, if I run a Sound with both the VCS and DSP status windows closed, it still stays around 15%, which is also very reasonable. If the timeline is used then we get the values below:
Timeline not playing, VCS and DSP status closed: CPU around 60%
Timeline is playing, VCS and DSP status closed: CPU above 90%
Timeline not playing, DSP status open: CPU above 80%

The funny thing is that during compiling, the CPU comes down to around 20%!!!

posted 16 December 2004 20:22            

quote:

---

Originally posted by SSC:
We will look into this for the next update...

---

Thanks, that would be nice. I'm experiencing the same in OS X (10.3.5). Kyma's
idle CPU'ing causes the fans in my G5 2 x 2,5 to rev up and down much of the
time. Closing DSP status and hiding the program helps though when having Kyma
in the background (doing sequensing in Logic). In Mac OS9 it was
possible to open Kyma in ResEdit and disable "can background" which lead
Kyma to only take CPU when really needed. Is a similar hack in possible OS
X?