| Michael,
Thanks for all your work with the new Windows installer.
I was so happy to download it from SourceForge, install everything,
launch QuteCsound
and get sound out instantly! WOW... what a major simplification and
improvement.
Thanks so much.
I was also able to plug in my nanoKontrol, set the MIDI settings in
QuteCsound and BAM - midi.
Also, I launched some of Ian's fantastic FLTK collection - some with
MIDI and some without and they all
worked too.
So too did my Toots, Chapter 1 and All my Examples. Thanks for
including them.
To further simplify, standardize and clarify things, I would like to
make a couple of suggestions:
1. You install a folder of aliases in the Program Files Directory and
Start Menu called Csound (that's super)
- but in this folder, there are broken aliases and aliases to front-
ends that are no longer developed or supported.
SUGGESTION ONE: This folder should only include aliases to:
A: Uninstall,
B: QuteCsound,
C: The Csound Manual,
D: The Examples Directory
(in which one should find a Basics Folder - which would be all of my
subfolders,
and an Advanced folder (which would be the API stuff, the Python
stuff, essentially...
all the extra stuff currently in the Examples folder)
E: A NEW Tutorials Folder (in which you put - "The Gogins
Tutorials" (Csound5, CsoundAC and CsoundVST) in a Folder and "The
Boulanger Tutorials" in another folder (there would be my TOOTS and my
Chapter 1 from The Csound Book - currently in the examples folder)
F: A README file that explains what these few things are and maybe
explains where some of the other Csound Developer Stuff is and old
FrontEnds, etc.
G: Optional: An Alias to the Terminal where you could run Csound from
the Commandline
I am making these suggestions becase.... It was easy to install, but
there was still too much stuff there - that was deprecated and not
maintained and not linked. I know to launch QuteCsound. A beginner
might click the alias to Csound - and .... nothing happens. That
would be a shame since with QuteCsound... A LOT HAPPENS... The
examples and other stuff are currently installed, but it is difficult
to find them - and for a beginner, playing these compositions and
getting all these MIDI instruments working is a very very important
and welcoming First Step into the world of Csound. Hopefully you agree.
Maybe others who are working with Windows have some suggestions too.
My goal, is to make sure that the first experience of Windows Users is
the simplest and also the most powerful.
Like me, they should install - and hit run - and say... wow...
We are so close to that now. Thanks to you and this installer.
Rick
PS.... have you checked out all the examples that Joachim and Andres
have added to QuteCsound? Like WOW.... Amazing stuff.
On my Mac....... The view code graph menu option is working amazingly
- WOW.... Block Diagram Heaven.
Dr. Richard Boulanger - rboulanger@berklee.edu
On Oct 2, 2009, at 9:28 AM, Michael Gogins wrote:
> I have uploaded the double and perhaps also the float Windows
> installers to SourceForge, the latter may have completed uploading
> since I left for work. I have not done any of the accounting required
> to get the uploads to show up on the download page. I can do that
> tonight, or someone else can do it.
>
> Changes:
>
> Completely new Windows installer with default, core, complete, and
> custom selections of components. The default and core choices do not
> depend on any extra third party software such as Python.
>
> Includes all examples and tutorial code from Richard Boulanger.
>
> New Csound tutorial based on QuteCsound.
>
> All new CsoundAC tutorial.
>
> CsoundAC now has a Lua interface in addition to its existing Python
> interface.
>
> The README file has been rewritten to more quickly orient new users
> of Csound.
>
> New performance test Python script in the examples/Python directory.
>
> The crash on exit bugs on Window are, I think, gone.
>
> The installers are even bigger than they were before!
>
> Email problems to this list or to me personally.
>
> Regards,
> Mike
>
>
>
> On 10/2/09, Victor Lazzarini wrote:
>> when are we planning to do this?
>>
>> Victor
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry® Developer Conference in SF,
>> CA
>> is the only developer event you need to attend this year. Jumpstart
>> your
>> developing skills, take BlackBerry mobile applications to market
>> and stay
>> ahead of the curve. Join us from November 9-12, 2009. Register
>> now!
>> http://p.sf.net/sfu/devconf
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
> --
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart
> your
> developing skills, take BlackBerry mobile applications to market and
> stay
> ahead of the curve. Join us from November 9-12, 2009. Register
> now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net |