Hi David,

The stop button should terminate csound but I have noticed something
similar to what you are mentioning before.  That whole bit of code is
not the cleanest and is needing some attention, and having a scenario
of pressing it quickly after a Csound process starts is very helpful. 
Thanks for that bit of feedback!

As for cmd-shift-F9, you can also use shift-F9 to render to disk and
have blue automatically play the file after rendering.  The two
methods of rendering (to disk versus normal render) differ in calling
csound but only as you define it in the project properties.  They do
differ in what they do around it because of the different use case
scenarios.  I think now that the issue may be because rendering live
there is a lot of threads going on and checks for loop rendering and I
suspect that there is perhaps a bug there.

As for the signature, I find it more useful to use the code completion
feature (ctrl-space) which pops open a dialog and fills in the rest of
the code with he signature from the opcodes.xml file, I guess
primarily becuase it matches my usage of development environments I
program in (eclipse, netbeans, etc.).  To better implement something
like you mention though I'd like to redo some other code to get the
status area more usable.  Anyways, if you could, please file a feature
request at the blue sourceforge page (accessible from the help menu in
blue), as I'm just now getting to a backlog of emails and other things
and am afraid I will miss the request in the future.

Very glad to hear you're enjoying blue and glad to hear your feedback on it! 

^_^

steven

On 9/20/05, David Akbari <dakbari@gmail.com> wrote:
> 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 <signature> 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
>
-- 
Send bugs reports to this list.
To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk