I'm writing an article for the upcoming csound journal on how to create simple activities with python, csndsugui and csound on olpc or any sugar, this would also work on a regular linux box running sugar as well. I run sugar on my desktop with fedora core 10, where its a download option for fedora. Its really tough to try to develop on the OLPC, its easier to emulate it with another machine and develop on a desktop and the copy the files down to the olpc. On Mon, Jan 12, 2009 at 7:25 PM, Art Hunkins wrote: > Brian, > > To your question: yes. > > As soon as I learn how to do it, I'll indeed be doing what you suggest. > > I have yet to get csndsugui going (or csound-editor for that matter), and > must get into Python from the bottom up. > > My goal is to write Activities with Python GUI. First, however, I must scale > my csound CPU requirements to the possibilities of the OLPC. Right now, the > ASCII keyboard activity is putting severe limitations on my plans. What can > easily be done with MIDI sliders/knobs, is quite problematic using ASCII (in > part, admittedly, because of all the additional data manipulation that must > take place). > > I've already had to reduce my 16 voices to 8, and move from a SR=44100, to > 32000. (For unknown reasons, this modest reduction in SR makes a *huge* > reduction in CPU usage. A followup email on this phenomenon will come soon.) > > Art Hunkins > > ----- Original Message ----- From: "Brian Redfern" > To: > Sent: Friday, January 09, 2009 1:31 AM > Subject: [Csnd] Re: sensekey and Linux/OLPC > > >> 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" >>> >> >> >> Send bugs reports to this list. >> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe >> csound" > > > > Send bugs reports to this list. > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe > csound" >