Csound Csound-dev Csound-tekno Search About

[Csnd] blue and Csound5

Date2005-09-18 05:16
FromDavid Akbari
Subject[Csnd] blue and Csound5
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

Date2005-09-18 21:46
FromSteven Yi
SubjectRe: [Csnd] blue and Csound5
AttachmentsNone  

Date2005-09-18 22:41
FromDavid Akbari
SubjectRe: [Csnd] blue and Csound5
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

Date2005-09-19 01:27
FromSteven Yi
SubjectRe: [Csnd] blue and Csound5
AttachmentsNone  

Date2005-09-21 03:10
FromDavid Akbari
SubjectRe: [Csnd] blue and Csound5
To follow up on this,

It seems that the STOP button in the upper right hand corner's 
transport does not have an explicit method to terminate Csound. If I 
start a realtime performance with an instr that is quite long and then 
press STOP quickly after the Csound process does not seem to respond, 
and it doesn't even appear that you can break the Csound process (F7) 
with CTRL + C!

What seems to work quite well is to use the CMD + SHIFT + F9 command to 
render to disk. I have not had one error yet using this technique. It 
seems also that the "F7" csound process and the cmd + shift + F9 are 
calling Csound in different ways ...

Using the render method however, I have found blue to be quite an 
amazing tool for use in computer music composition. The XML system also 
allows for easy extendibility, like appending opcodes from Csound5 to 
the contextual menu. Is it hard to make the  print to the 
lower bar window on opcode highlight. This bar usually says the last 
action for example "Saved blue.blue to $HOME" it would be really great 
if you could parse the text from the signature tag on the screen as a 
"mini manual" like in MacCsound or Cecilia.

Otherwise Blue is a joy to work with, keep up the good work Steven and 
others using the program!


-David

-- 
Send bugs reports to this list.
To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk

Date2005-09-21 07:07
FromSteven Yi
SubjectRe: [Csnd] blue and Csound5
AttachmentsNone  

Date2005-09-21 09:28
Fromsokratesla
SubjectRe: [Csnd] blue and Csound5
AttachmentsNone