Hi David, > 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. Strange; if you could send me the error message the mail server gave (off list) I can check to see if there's something funny with it. > 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. Well, this is strange as blue does not call csound using the API, only executes the program. The exit behavior for running csound5 with blue should be exactly the same as if running csound5 from the commandline, in that blue is waiting for csound5 to return from it's execution before stopping. If you generate a CSD to disk and run csound5 on the CSD from the commandline, do you also get a hang at the end of processing or does it return you to the prompt? > It is ultimately going to be rendered, but I am always thinking about > using these things in realtime! Ah, okay, I think you use it pretty much as I do, which is to listen in realtime while working, but ultimately rendering to disk in the end. There's no reason why it should work on OSX. I haven't tested with OSX in quite some time, and I probably won't be able to for at least a week as I'm still on jury duty this week and won't be accessing my OSX computer at work until next week, but I've written a note to take a look at it when I get back into the office. steven -- Send bugs reports to this list. To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk