Csound Csound-dev Csound-tekno Search About

Re: The future of computer music? (was Re: [Csnd] The future of winsound)

Date2006-03-23 15:12
FromVictor Lazzarini
SubjectRe: The future of computer music? (was Re: [Csnd] The future of winsound)
CsoundVST would build on a Mac if it was not a python module as well,
as I pointed out before.

Victor

At 14:59 23/03/2006, you wrote:
>CsoundVST is in fact this GUI frontend program, and already has an editor. 
>However, I do not have a Mac, so have not ported it to OS X. Note that 
>CsoundVST also does not have dialogs for helping with running utilities, 
>setting options, etc... the user has to type in a regular Csound command 
>line in a text box.
>
>Regards,
>Mike
>
>-----Original Message-----
> >From: Victor Lazzarini 
> >Sent: Mar 23, 2006 7:26 AM
> >To: csound@lists.bath.ac.uk
> >Subject: Re: [Csnd] The future of computer music? (was Re: [Csnd] The 
> future of winsound)
> >
> >I agree with you. For instance, the Csound 5 OSX GUI does not add anything
> >to the command-line interface apart from play-pause-rewind buttons. What it
> >does (and took me a while of fiddling to achieve) is 99% (if not 100%)
> >compatibility with the command-line, so there is nothing that can be done in
> >the command-line that cannot be done in it (FLTK included)
> >
> >So it does not add anything really. However, I did not see that as the
> >reason for
> >spending part of my Christmas holiday putting it together, but because I
> >believe
> >that outside the Unix-originated world there are lots of people that are
> >put off typing
> >things into a terminal, esp. Mac users who prior to OSX did not even have a
> >straightforward terminal to use. I believe we had to cater for these
> >people, even
> >if in a limited fashion, so that the csound distribution included a basic
> >GUI frontend.
> >
> >I can see that people might like an all-in-one GUI environment with an
> >editor and
> >other stuff. I am sure someone will do it.
> >
> >Victor
> >
> >At 10:52 23/03/2006, you wrote:
> >>I may be alone with this opinion, but most of the GUI frontends add
> >>little if anything compared to the command line interface, and those
> >>that do (Blue, Cabel, and various plugins for other software like PD,
> >>Max, Cubase, etc.) are available for Csound 5. The GUIs for Csound 4
> >>like Winsound or CsoundAV may look impressive to new users, but do not
> >>in fact add real new functionality, and the built-in editors can be
> >>limited compared for example to vim or emacs with a Csound mode.
> >>
> >>On Thursday 23 March 2006 11:16, Victor Lazzarini wrote:
> >>
> >> > I say Csound 5 already looks the future of  computer music,
> >> > even if I say it so myself. Apart from the 'base system', there
> >> > are various exciting API projects that are coming onstream.
> >> >
> >> > Perhaps from a Mac-only perspective it might not immediately
> >> > seem a revolution, but even in that platform it is.  For OSX,
> >> > there are seven different frontends
> >> > already: the csound 5 GUI, csound 5 wish, csoundapi~ (PD), csound~
> >> (MaxMSP),
> >> > CSDPlayer, CsoundXAlpha and csound 'classic' command-line (as
> >> > well as cstclsh, so there are eight), and that does not include John's
> >> > winsound (and also Blue and Cabel, which are not API-based).
> >> > There is no MacCsound with an editor, but I am sure Matt
> >> > will eventually include an editor in his version.
> >> >
> >> > In any case, editors are plentiful. The most useful of them seems to be
> >> > emacs with the csound modes (it might be an idea to offer an emacs
> >> > package including these modes in CSounds.com).
> >> >
> >> > At 01:16 22/03/2006, you wrote:
> >> > >Typing commandlines in the Terminal has a sort of nostalgic super
> >> > >user / computer wizard / hacker vibe that a few
> >> > >of my students can totally appreciate, but for most of them...
> >> > >Csound5 looks and feels like a step back in time and
> >> > >not a step forward into the future of computer music...
> >>--
> >>Send bugs reports to this list.
> >>To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
> >
> >Victor Lazzarini
> >Music Technology Laboratory
> >Music Department
> >National University of Ireland, Maynooth
> >
> >--
> >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

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 

Date2006-03-23 17:04
Fromapalomba@austin.rr.com
Subjectnew Csound5 installer?
AttachmentsNone  

Date2006-03-23 17:06
FromAnthony Kozar
Subject[Cs-dev] Re: [Csnd] Porting CsoundVST
About a month ago, I looked into whether I could get any portion of
CsoundVST to compile on MacOS 9.  I was interested in trying out the Python
extension module with all of its composition classes.

What I found was that all the different aspects of CsVST seem to be fairly
well entangled.

Just a suggestion:  If the VST functionality, the FLTK GUI, and the Python
extension code could be made more modular (at least so that one could
determine at compile-time via #defines which features one wants), then it
would be possible to use parts of CsoundVST on more platforms.

I would be very happy to provide a CsoundVST python module to my users on OS
9, but the FLTK stuff will never compile for me (1).  And it is even
feasible that the VST plugin code could work on OS 9 if it were separated.

Thanks to Michael for this tool!

Anthony Kozar
anthonykozar AT sbcglobal DOT net

(1) Although I have difficulty compiling the Boost code as well, so it may
not be possible in the end.


Victor Lazzarini wrote on 3/23/06 10:12 AM:

> CsoundVST would build on a Mac if it was not a python module as well,
> as I pointed out before.
> 
> Victor
> 
> At 14:59 23/03/2006, you wrote:
>> CsoundVST is in fact this GUI frontend program, and already has an editor.
>> However, I do not have a Mac, so have not ported it to OS X. Note that
>> CsoundVST also does not have dialogs for helping with running utilities,
>> setting options, etc... the user has to type in a regular Csound command
>> line in a text box.



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2006-03-23 17:56
FromVictor Lazzarini
SubjectRe: [Cs-dev] Re: [Csnd] Porting CsoundVST
I must correct myself. I got it to build, but not run. The modularity idea
is a good suggestion.

Victor

At 17:06 23/03/2006, you wrote:
>About a month ago, I looked into whether I could get any portion of
>CsoundVST to compile on MacOS 9.  I was interested in trying out the Python
>extension module with all of its composition classes.
>
>What I found was that all the different aspects of CsVST seem to be fairly
>well entangled.
>
>Just a suggestion:  If the VST functionality, the FLTK GUI, and the Python
>extension code could be made more modular (at least so that one could
>determine at compile-time via #defines which features one wants), then it
>would be possible to use parts of CsoundVST on more platforms.
>
>I would be very happy to provide a CsoundVST python module to my users on OS
>9, but the FLTK stuff will never compile for me (1).  And it is even
>feasible that the VST plugin code could work on OS 9 if it were separated.
>
>Thanks to Michael for this tool!
>
>Anthony Kozar
>anthonykozar AT sbcglobal DOT net
>
>(1) Although I have difficulty compiling the Boost code as well, so it may
>not be possible in the end.
>
>
>Victor Lazzarini wrote on 3/23/06 10:12 AM:
>
> > CsoundVST would build on a Mac if it was not a python module as well,
> > as I pointed out before.
> >
> > Victor
> >
> > At 14:59 23/03/2006, you wrote:
> >> CsoundVST is in fact this GUI frontend program, and already has an editor.
> >> However, I do not have a Mac, so have not ported it to OS X. Note that
> >> CsoundVST also does not have dialogs for helping with running utilities,
> >> setting options, etc... the user has to type in a regular Csound command
> >> line in a text box.
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by xPML, a groundbreaking scripting language
>that extends applications into web and mobile media. Attend the live webcast
>and join the prime developer group breaking into this new coding territory!
>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net