Is this when you're driving command line csound with the keyboard? You might have better results writing a python/csound activity using csndsugui library, I think you might have better latency results with keyboard commands using python/gtk instead of sending them on the command line. On Thu, Jan 8, 2009 at 8:22 PM, Art Hunkins wrote: > I continue to have issues of extremely heavy CPU usage with ASCII keyboard > input on the OLPC. > > In Windows, there is a *modest* CPU penalty incurred with keyboard input > (via sensekey), but with Linux/OLPC it is major. > > Of course, the OLPC prints the sensekey input to the console, whereas > Windows does not, and this may well be part of the problem. > > Indeed if one watches CPU usage via top in Linux, you can see usage jump > significantly (both overall and within Csound) with keyboard input. > > Can someone have a look at sensekey to determine: > 1) if there's any way of keeping it from printing to the terminal (in > Linux); 2) if there's any other way in which Linux overhead could be > minimized with ASCII input? > > The penalty is so bad that I may not be able to use sensekey messaging with > the OLPC, but rather use only MIDI controllers - which require no such > overhead at all. > > Art Hunkins > > > > Send bugs reports to this list. > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe > csound" >