With the change to csound5 the old (MFC-based) Winsound has been
finally buried.  However I slightly mourn its loss, and so in a fit
of excitement yesterday I created winsound5, a GUI for csound5.
However it is FLTK based and should run on all three platforms (and
others).  Not totally finished yet as it is lacking some of the
utilities, but it is in the CVS for anyone brave enough or nostalgic
enough to want a simple launcher.
  It has also acted as a way of trying to learn how to use the API.
Any comments welcome; positive one especially welcome.
==John ffitch

Thanks a million John!

I am thrilled to think that it will survive and be useable. Although I work
extensively with Linux and OSX on a daily basis I still find that I am most
comfortable working with Winsound and so I do for all my compositions. This
is perhaps because it is what I cut my teeth on when first starting out. It
is perfect for my compositional processes and because it has not been
available for Csound 5 I have continued working with version 4.23f03, which
I feel is the most stable of the 4.x family.

I would be happy to help you test it, just let me know how I can help.

Michael Rhoades
www.perceptionfactory.com





On 3/21/06 4:18 PM, "jpff@codemist.co.uk"  wrote:

> With the change to csound5 the old (MFC-based) Winsound has been
> finally buried.  However I slightly mourn its loss, and so in a fit
> of excitement yesterday I created winsound5, a GUI for csound5.
> However it is FLTK based and should run on all three platforms (and
> others).  Not totally finished yet as it is lacking some of the
> utilities, but it is in the CVS for anyone brave enough or nostalgic
> enough to want a simple launcher.
> It has also acted as a way of trying to learn how to use the API.
> Any comments welcome; positive one especially welcome.
> ==John ffitch

Thanks a million John!

I am thrilled to think that it will survive and be useable. Although I work
extensively with Linux and OSX on a daily basis I still find that I am most
comfortable working with Winsound and so I do for all my compositions. This
is perhaps because it is what I cut my teeth on when first starting out. It
is perfect for my compositional processes and because it has not been
available for Csound 5 I have continued working with ver sion 4.23f03, which
I feel is the most stable of the 4.x family.

I would be happy to help you test it, just let me know how I can help.

Michael Rhoades
www.perceptionfactory.com





On 3/21/06 4:18 PM, "jpff@codemist.co.uk" wrote:

> With the change to csound5 the old (MFC-based) Winsound has been
> finally buried. However I slightly mourn its loss, and so in a fit
> of excitement yesterday I created winsound5, a GUI for csound5.
> However it is FLTK based and should run on all three platforms (and
> others). Not totally finished yet as it is lacking some of the
> utilities, but it is in the CVS for anyone brave enough or nostalgic
> enough to want a simple launcher.
> It has also acted as a way of trying to learn how to use the API.
> Any comments welcome; positive one especially welcome.
> ==John ffitch

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

Dear John, and All Csound5 Developers....

Can't wait to check out John's WinSound frontEnd for Csound5.

The installers are great.  And I am thrilled with all the new  
features and opcodes in Csound5,
but...
I and my students end up still using and teaching with MacCsound.
And even when I use Csound5, I use MacCsound as my editor.

MacCsound5 - would be amazingly wonderful (Matt?)
WinSound5 - on the Mac would be very very nice too

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...

I would love to encourage John, Victor, Istvan, Michael, Anthony,  
Matt, Richard, and any of the fantastic Csound5
Developers to explore the API and make GUI's for the next generation  
of Csound Composers and Users.

Thanks so much for ALL your amazing work on the program.

Dr. B.


On Mar 21, 2006, at 5:07 PM, Michael Rhoades wrote:

> Thanks a million John!
>
> I am thrilled to think that it will survive and be useable.  
> Although I work
> extensively with Linux and OSX on a daily basis I still find that I  
> am most
> comfortable working with Winsound and so I do for all my  
> compositions. This
> is perhaps because it is what I cut my teeth on when first starting  
> out. It
> is perfect for my compositional processes and because it has not been
> available for Csound 5 I have continued working with version  
> 4.23f03, which
> I feel is the most stable of the 4.x family.
>
> I would be happy to help you test it, just let me know how I can help.
>
> Michael Rhoades
> www.perceptionfactory.com
>
>
>
>
>
> On 3/21/06 4:18 PM, "jpff@codemist.co.uk"  wrote:
>
>> With the change to csound5 the old (MFC-based) Winsound has been
>> finally buried.  However I slightly mourn its loss, and so in a fit
>> of excitement yesterday I created winsound5, a GUI for csound5.
>> However it is FLTK based and should run on all three platforms (and
>> others).  Not totally finished yet as it is lacking some of the
>> utilities, but it is in the CVS for anyone brave enough or nostalgic
>> enough to want a simple launcher.
>> It has also acted as a way of trying to learn how to use the API.
>> Any comments welcome; positive one especially welcome.
>> ==John ffitch
>
> -- 
> Send bugs reports to this list.
> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk

With the change to csound5 the old (MFC-based) Winsound has been
finally buried. However I slightly mourn its loss, and so in a fit
of excitement yesterday I created winsound5, a GUI for csound5.
However it is FLTK based and should run on all three platforms (and
others). Not totally finished yet as it is lacking some of the
utilities, but it is in the CVS for anyone brave enough or nostalgic
enough to want a simple launcher.
It has also acted as a way of trying to learn how to use the API.
Any comments welcome; positive one especially welcome.
==John ffitch
--
Send bugs reports to this list.
To unsubscribe , send email to csound-unsubscribe@lists.bath.ac.uk

A couple things:

1) it tries to look for libcsound64.a in the Makefile
*) Fixed by either
  ln -s ../../libcsound.a ../../libcsound64.a
or rename libcsound64.a to libcsound.a in the Makefile

2) compiler errors out because of space between -L and /usr/X11R6/lib
* removing the space between -L /usr/X11R6/lib to -L/usr/X11R6/lib 
fixes it.

3) on successful compilation, it's impossible for the window to take 
focus on OS X without command+clicking on the window. Similar to the 
problems with the [gemwin] in Pd for the longest time they just fixed. 
All functionality does seem to work, keeping in mind you basically have 
to command+click everything and realize that Winsound is always in the 
background. I also can't seem to change the values for -b and -B in the 
"Extras" dialogue...

Otherwise, Nice job!


-David

On Mar 21, 2006, at 4:18 PM, jpff@codemist.co.uk wrote:

> With the change to csound5 the old (MFC-based) Winsound has been
> finally buried.  However I slightly mourn its loss, and so in a fit
> of excitement yesterday I created winsound5, a GUI for csound5.
> However it is FLTK based and should run on all three platforms (and
> others).  Not totally finished yet as it is lacking some of the
> utilities, but it is in the CVS for anyone brave enough or nostalgic
> enough to want a simple launcher.
>   It has also acted as a way of trying to learn how to use the API.
> Any comments welcome; positive one especially welcome.
> ==John ffitch
> -- 
> Send bugs reports to this list.
> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
>

you need to run Rez on it, something like

/Developer/Tools/Rez -i APPL -o [app-name] cs5.r

the cs5.r file is found in the top-level sources.

At 02:58 22/03/2006, you wrote:


>3) on successful compilation, it's impossible for the window to take focus 
>on OS X without command+clicking on the window. Similar to the problems 
>with the [gemwin] in Pd for the longest time they just fixed. All 
>functionality does seem to work, keeping in mind you basically have to 
>command+click everything and realize that Winsound is always in the 
>background. I also can't seem to change the values for -b and -B in the 
>"Extras" dialogue...

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

Matt has a CsoundXAlpha frontend you can try. No editor at the moment,
though.

Victor

At 01:16 22/03/2006, you wrote:
>Dear John, and All Csound5 Developers....
>
>Can't wait to check out John's WinSound frontEnd for Csound5.
>
>The installers are great.  And I am thrilled with all the new
>features and opcodes in Csound5,
>but...
>I and my students end up still using and teaching with MacCsound.
>And even when I use Csound5, I use MacCsound as my editor.
>
>MacCsound5 - would be amazingly wonderful (Matt?)
>WinSound5 - on the Mac would be very very nice too
>
>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...
>
>I would love to encourage John, Victor, Istvan, Michael, Anthony,
>Matt, Richard, and any of the fantastic Csound5
>Developers to explore the API and make GUI's for the next generation
>of Csound Composers and Users.
>
>Thanks so much for ALL your amazing work on the program.
>
>Dr. B.
>
>
>On Mar 21, 2006, at 5:07 PM, Michael Rhoades wrote:
>
>>Thanks a million John!
>>
>>I am thrilled to think that it will survive and be useable.
>>Although I work
>>extensively with Linux and OSX on a daily basis I still find that I
>>am most
>>comfortable working with Winsound and so I do for all my
>>compositions. This
>>is perhaps because it is what I cut my teeth on when first starting
>>out. It
>>is perfect for my compositional processes and because it has not been
>>available for Csound 5 I have continued working with version
>>4.23f03, which
>>I feel is the most stable of the 4.x family.
>>
>>I would be happy to help you test it, just let me know how I can help.
>>
>>Michael Rhoades
>>www.perceptionfactory.com
>>
>>
>>
>>
>>
>>On 3/21/06 4:18 PM, "jpff@codemist.co.uk"  wrote:
>>
>>>With the change to csound5 the old (MFC-based) Winsound has been
>>>finally buried.  However I slightly mourn its loss, and so in a fit
>>>of excitement yesterday I created winsound5, a GUI for csound5.
>>>However it is FLTK based and should run on all three platforms (and
>>>others).  Not totally finished yet as it is lacking some of the
>>>utilities, but it is in the CVS for anyone brave enough or nostalgic
>>>enough to want a simple launcher.
>>>It has also acted as a way of trying to learn how to use the API.
>>>Any comments welcome; positive one especially welcome.
>>>==John ffitch
>>
>>--
>>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 

Thanks Victor! Using Rez does the trick for getting the window to gain 
focus.

As far as the buffersize issue, before I knew about the Rez thing I 
just edited winsound.cxx and changed mb->value() from 512 to 1024. I 
also added a value to the -M command so it will always look for MIDI

/* from winsound.cxx : 574 */
     { Fl_Value_Input* o = mB = new Fl_Value_Input(335, 149, 40, 25, 
"Samples/Hardware (-B)");
       mB->value(1024);
     }
     { Fl_Value_Input* o = mb = new Fl_Value_Input(335, 180, 40, 25, 
"Samples/Hardware (-b)");
       mb->value(1024);
     }
     { Fl_File_Input* o = mM = new Fl_File_Input(20, 240, 160, 25, "MIDI 
File input (-M)");
       mM->value(0);
	  o->align(FL_ALIGN_TOP_LEFT);
     }


Here is the Makefile I used


LIBS = -I../../H -lfltk -L/usr/X11R6/lib -lX11 ../../libcsound.a 
-lsndfile -lpthread
CXX = g++

wins5:	main.cxx winsound.cxx winsound.h
	${CXX} -o wins5 -g main.cxx winsound.cxx ${LIBS}

winsound.cxx: winsound.fl
	fluid -c winsound.fl

winsound.h: winsound.fl
	fluid -c winsound.fl

to build it I actually made a shell script on OS X that looks like

#! /bin/tcsh

make;\
cp wins5 ../../wins5;\
cd ../../;\
/Developer/Tools/Rez -i APPL -o wins5 cs5.r

and typed sh make.sh in the winsound directory. It now spits out a very 
workable and useable wins5 executable in the top level of the Csound5 
source tree. Very nice!



-David

On Mar 22, 2006, at 4:34 AM, Victor Lazzarini wrote:

> you need to run Rez on it, something like
>
> /Developer/Tools/Rez -i APPL -o [app-name] cs5.r
>
> the cs5.r file is found in the top-level sources.

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...

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

Victor Lazzarini wrote:

> 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).

This leads me to:

Is anybody maintaining the debian package for csound? Has there been a 
release of csound5 into debian/unstable?

The next step would be to have the emacs mode as a seperate debian 
package, which is much better than throwing it in the main csound 
package. For instance I tend to compile csound myself, but would be 
interrested in having the emacs mode from debian...

-- 
peace, love & harmony
Atte

http://www.atte.dk

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 

What I suggested was to put up a package with emacs and the csound modes etc.
So any new users could install emacs with all the stuff in it. Emacs users 
would
probably know or find out how to add these modes.

At 10:50 23/03/2006, you wrote:
>Victor Lazzarini wrote:
>
>>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).
>
>This leads me to:
>
>Is anybody maintaining the debian package for csound? Has there been a 
>release of csound5 into debian/unstable?
>
>The next step would be to have the emacs mode as a seperate debian 
>package, which is much better than throwing it in the main csound package. 
>For instance I tend to compile csound myself, but would be interrested in 
>having the emacs mode from debian...
>
>--
>peace, love & harmony
>Atte
>
>http://www.atte.dk
>--
>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 

Hi All.

I am not a new user nor do I look to Winsound for additional functionality,
it does not offer an editor. I use Excel for my score creation and WinXound
for my orchestra. All I need is a fast simple way to render. When composing
I am focusing upon the sound and then, with each successive rendering, its
further modification. I render and re-render to mold the composition into
the form it requires and do not want to focus on paths or flags at that
time, just the music. As a systems administrator I work from command line
constantly, which I prefer for many functions. It is a personal choice but
for me rendering with Winsound has always been more transparent to the
process. 

I think that Csound is the future of computer generated music. This is not
always obvious to those who have not worked with it and with computer music
in general. A composer has to dig in and begin working with it to understand
the incredible power that is afforded. To be able to compose on the micro
and macro level with such a huge variety of options is really unparalleled.
I am sure that everyone who masters Csound works with it in a different way
and likely in a different way for each composition. It is an open ended
process for creation. A little overwhelming when starting out. It generally
may not be  as pretty as many of the commercial programs but it is not
limited as they are either. I have never seen anything that comes close to
Csound.

Csound 5 will in the future be seen as a milestone in this capability.

Michael Rhoades
www.perceptionfactory.com


 

> -----Original Message-----
> From: Istvan Varga [mailto:istvan_v@fibermail.hu]
> Sent: Thursday, March 23, 2006 5:53 AM
> To: csound@lists.bath.ac.uk
> Subject: Re: [Csnd] The future of computer music? (was Re: [Csnd] The
> future of winsound)
> 
> 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
> 
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.859 / Virus Database: 585 - Release Date: 2/14/2005
> 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.859 / Virus Database: 585 - Release Date: 2/14/2005
 

I would say that Csound 5 is more like the future of computer music software
INFRASTRUCTURE.  It is a modular, reusable, programmable synthesis engine
that can be adapted in hundreds of different ways.

For instance, someone could create a GUI effects processor with dozens of
preset effects and graphical controls for editing their parameters.  Csound
could be the engine underneath of it all, but the user would never see a
line of Csound code.  (Cecilia provides this ability with its built-in
modules I think).

Other people (like Iain Duncan) will use Csound as the heart of their own
command-line based performance systems.

And I think this is the true significance of Csound 5.  I think the
developers all knew that Csound 5 when released would not immediately grab
hold of the imaginations of users who do not want to interact with a
terminal window, or "worse yet" a programmer's API in C (or Java or Python
or C++ or Lua or Lisp -- isn't this great?!).

My point is that it will take time for truly great front ends to emerge.
The Csound 5.00 release is not the end of the story (although we all wish it
was since it took 3 years to get here).  It is merely the beginning.

I sincerely hope that there will soon be a MacCsound 5, and a CsoundAV 5
(more difficult, I know), an exciting new Winsound 5, maybe even a new
version of Maurizio Puxeddo's Linux Csound Front End in Python.

For my part, I am continuing to develop Matt Ingalls' "Mills Csound" GUI for
MacOS 9 which I am now calling CsoundFront.  If I find enough time and
motivation, its interface will be radically overhauled to take advantage of
Csound 5, providing an ever more complete graphical interface to ALL of
Csound's options and utilities, as well as graphical Cscore programming,
user plugins for score generation, rendering on remote computers, and
integration with many other tools such as Midi to Csound, nGen, Sfront,
Cmix, MPW, Scheme, Python, etc.

So, I am sorry if the Csound 5 release was a let down for anyone.  I am
willing to bet than within the next year, you will see most of your Csound
dreams come true.

Anthony Kozar
anthonykozar AT sbcglobal DOT net


Victor Lazzarini wrote on 3/23/06 7:26 AM:

> 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, [...]

> 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.

> At 10:52 23/03/2006, Istvan Varga 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

>> 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.

>>> At 01:16 22/03/2006, Richard Boulanger 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...

el Thu, 23 Mar 2006 10:16:43 +0000
Victor Lazzarini  escribió:


> 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).


I'm sure you wanted to say "vim with the csound vim tools..."

:-)

http://www.eumus.edu.uy/docentes/jure/csound/vim/

(btw, a long delayed update is to be released soon)

That too, if you are vim-inclined ! :)

At 20:14 23/03/2006, you wrote:
>el Thu, 23 Mar 2006 10:16:43 +0000
>Victor Lazzarini  escribió:
>
>
> > 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).
>
>
>I'm sure you wanted to say "vim with the csound vim tools..."
>
>:-)
>
>http://www.eumus.edu.uy/docentes/jure/csound/vim/
>
>(btw, a long delayed update is to be released soon)
>--
>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