My mistake. I should have said interruptions, dropouts, synchronization problems. It's not static like an old TV at night. -Chuckk On Thu, Oct 23, 2008 at 1:07 PM, Oeyvind Brandtsegg wrote: > Getting "lots of static any time I move the cursor over the score" > seems very strange. Did you investigate to see that this is really a > tkinter/csound problem ? The only time I've had static noise when > moving the mouse was when having a ground loop between my computer and > the soundcard. If you're running this on a laptop, try running it on > battery (temporarily), as the noise should go away if you do. > Oeyvind > > 2008/10/23 Chuckk Hubbard : >> I'm revisiting this question for my own project now, and I'm curious >> about this. I have been using Tkinter and the API in Python, >> assembling a complete csd when ready to audition and running Csound. >> It's worked well enough for me, but I get lots of static any time I >> move the cursor over the score, even though I start a separate thread >> for Csound. A Pd expert I visited last week suggested using OSC to >> avoid that, which would also have the advantage that one could control >> Pd or any other OSC-capable software, if one prefers that to Csound. >> I'm working on paring down my app into an understandable example to >> ask for help. Could be I'm not using the API right. >> My dilemma is whether to keep it as it is and disable mouse callbacks >> during playback, or to switch to an orchestra with no score and send >> it real-time events (instead of putting all notes into the csd to >> start), as you suggest here, or to send OSC events at an API-run >> orchestra, or even to start a separate Csound process instead of using >> the API. >> Could it be I'm just not including the proper audio latency >> optimization or scheduling priority in the API command? >> I'll post an example later today, if it reproduces the problem. >> >> -Chuckk >> >> On Mon, Oct 13, 2008 at 12:49 AM, victor wrote: >>> With Python, you don't even need OSC, it can be much simpler, >>> just use RT events (and possibly channels). No need to involve >>> networking of any sort (unless you are using remote machines). >>> >>> Victor >>> ----- Original Message ----- From: "Brian Redfern" >>> To: >>> Sent: Sunday, October 12, 2008 10:11 PM >>> Subject: [Csnd] Re: Re: Re: Re: Re: Re: Re: AW: Re: AW: Re: tkinter within >>> csound >>> >>> >>>> Yeah what I'm thinking of doing is to run an orchestra that is >>>> full-featured and then live code the score by firing off osc at it >>>> from the python shell. >>>> >>>> On Sun, Oct 12, 2008 at 1:02 PM, victor wrote: >>>>> >>>>> Of course with PD, this is even easier, because the mixing is done >>>>> by the host program. Sounds quite interesting. >>>>> >>>>> Victor >>>>> ----- Original Message ----- From: "Chuckk Hubbard" >>>>> >>>>> To: >>>>> Sent: Sunday, October 12, 2008 8:22 PM >>>>> Subject: [Csnd] Re: Re: Re: Re: Re: AW: Re: AW: Re: tkinter within csound >>>>> th >>>>> >>>>>> I was doing something like that with Pd and csoundapi~ once upon a >>>>>> time; I set it so a certain key started a new instance using the >>>>>> edited csd file, then faded that one in and the other out before >>>>>> stopping it. Worked pretty well at the time, haven't done it lately. >>>>>> >>>>>> -Chuckk >>>>>> >>>>>> On 10/12/08, victor wrote: >>>>>>> >>>>>>> The type of live-coding possible here is one of setting up >>>>>>> a comprehensive orchestra and then controlling it with >>>>>>> live-coded events. >>>>>>> >>>>>>> Another possibility is to run two or more instances of >>>>>>> Csound alongside and live-code instruments, compile >>>>>>> and run in these different instances (stopping them if >>>>>>> you want to set a new instrument running). You'd need >>>>>>> Jack on Linux to do this. On Windows, this cannot be >>>>>>> done with ASIO (it is single-client). >>>>>>> >>>>>>> This is because it is possible to unload instruments, but not >>>>>>> possible to load them yet on a running instance. >>>>>>> >>>>>>> However, if you have a good orchestra, there is no need >>>>>>> to be creating instruments on the fly, as you can start them, >>>>>>> interconnect, modify, etc all with RT events. >>>>>>> >>>>>>> Victor >>>>>>> >>>>>>> ----- Original Message ----- From: "Brian Redfern" >>>>>>> >>>>>>> To: >>>>>>> Sent: Sunday, October 12, 2008 5:46 AM >>>>>>> Subject: [Csnd] Re: Re: Re: AW: Re: AW: Re: tkinter within csound >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> > Ultmately at the first step I'd like to learn to use csoundac from > >>>>>>> > the >>>>>>> > python shell to do live coding. >>>>>>> > >>>>>>> > I'm not sure whether I can do live coding with the csound api, or >>>>>>> > whether I need to use python to fire off midi or osc at a csd that is >>>>>>> > just a running csound process that takes score from midi or osc > >>>>>>> > input. >>>>>>> > >>>>>>> > On Sat, Oct 11, 2008 at 11:55 AM, Chuckk Hubbard >>>>>>> > wrote: >>>>>>> > >>>>>>> > > Have you checked out Pure Data with Gem? It was being used a lot > >>>>>>> > > > for >>>>>>> > > such things for a few years. I believe it uses a syntax/library > >>>>>>> > > > > > >>>>>>> > > based >>>>>>> > > on OpenGL, and you can create 3d objects, or 2d of course, and make >>>>>>> > > them interact with sound. It's a whole new thing to learn, of > > >>>>>>> > > course, >>>>>>> > > but last I tried, Victor's csoundapi object worked great. There's >>>>>>> > > > > a >>>>>>> > > tilda after "csoundapi", but I'm using my wife's old European Mac > >>>>>>> > > > and >>>>>>> > > I can't find the tilda...~ there it is >>>>>>> > > -Chuckk >>>>>>> > > >>>>>>> > > On 10/9/08, Brian Redfern wrote: >>>>>>> > > >>>>>>> > > > Yeah what I'm looking at doing is putting a animated interface, > >>>>>>> > > > > > so >>>>>>> > > > > > > you >>>>>>> > > > have music running and the animation is tied to the music and by >>>>>>> > > > manipulating the animated objects you change the sound. Not a > >>>>>>> > > > > > > > >>>>>>> > > > > widget >>>>>>> > > > type interface. >>>>>>> > > > >>>>>>> > > > >>>>>>> > > > >>>>>>> > > > Send bugs reports to this list. >>>>>>> > > > To unsubscribe, send email sympa@lists.bath.ac.uk with body >>>>>>> "unsubscribe csound" >>>>>>> > > > >>>>>>> > > > >>>>>>> > > >>>>>>> > > >>>>>>> > > -- >>>>>>> > > http://www.badmuthahubbard.com >>>>>>> > > >>>>>>> > > >>>>>>> > > 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" >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> http://www.badmuthahubbard.com >>>>>> >>>>>> >>>>>> 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" >>> >>> >>> >>> Send bugs reports to this list. >>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe >>> csound" >>> >> >> >> >> -- >> http://www.badmuthahubbard.com >> >> >> 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" > -- http://www.badmuthahubbard.com