Hi David,

The bluemusic-users mailing list only accepts messages from people who
are subscribed to the list as a measure to prevent spamming of the
list, so not that the list doesn't like you, just that you need to
become friends with it. =)

As for the stray csound command, I've come across that before but
thought I had gotten rid of the problem.  I'll take a look at the code
to see if there isn't any checking code that is off.  Whenever it's
happened to me, I've always done a "ps -Al" (not sure that works on
OSX, but a ps command with -aux maybe will do) to see if a csound
process is hanging around, then will use either "killall csound" to
kill all the processes, or if it's not stopping to issue a "kill -i #"
where # is the process number.  I think that should work for OSX.

Is the project you were working on in blue one which is for live
performance, or simply rendering in realtime?

steven

On 9/17/05, David Akbari <dakbari@gmail.com> wrote:
> Hi List,
> 
> I tried emailing this to the Bluemusic-users list but the mailman
> doesn't like me :( ...
> 
> Anyway,  I have found Blue to be an amazing tool for use with studying
> computer music composition.
> 
> I currently use the current CVS builds of both Csound5 and Blue
> (0.99.7) and I have found the sometimes the csound process fails to
> quit on OSX (10.3.9). The Blue process proceeds as normal but it
> appears suddenly that the computer slows to a halt! A top command
> reveals that it is a stray csound process that had not been terminated
> properly!
> 
> How is it that users would be able to fix this problem? Is it a
> preference intended for use with realtime performance??
> 
> 
> -David
> 
> --
> Send bugs reports to this list.
> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
>
-- 
Send bugs reports to this list.
To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk