| Hi Steven,
On Sep 18, 2005, at 4:46 PM, Steven Yi wrote:
> 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. =)
Ah yes, I had subscribed and I view the list from the address that I
was sending from (not this one) and it still gave errors.
>
> 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.
>
yes the ps -aux works great and then kill -9 It is
possibly good to point out for other users that the -9 flag is key!! A
vanilla kill will not work in this case.
The process does not continue and is terminated as expected with
versions of Csound4:
csound4.23f11
csound4.23f12
csound4.23f13.gbs0
however it is only with Csound5 (canonical CVS) that the process does
not terminate. Perhaps Blue does not have a method for recognizing that
the end of csoundPerformKsmps() should terminate the performance and
the executable continues because it expects a method from flavors of
csound4 where many functions are of void type.
> Is the project you were working on in blue one which is for live
> performance, or simply rendering in realtime?
>
It is ultimately going to be rendered, but I am always thinking about
using these things in realtime!
-David
--
Send bugs reports to this list.
To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk |