I found that while CsoundQt was a more convenient way to setup the options,
it often crashed on me for various reasons on windows and linux. Winsound i
only used briefly, so can't comment on it.

Now i use the terminal (in linux) and vim editor with the csound syntax
plugin, for the colored syntax. This i found to be the best route for me and
i also learned more about the CsOption flags this way.



--
View this message in context: http://csound.1045644.n5.nabble.com/Csound-on-Windows-tp5734042p5734044.html
Sent from the Csound - General mailing list archive at Nabble.com.

We have four modules that use Csound. Students must take the first
two, after that they have a choice. WinXound/Csound6 is used in module
1. This is all score driven work(basic sound synthesis). In module 2 I
introduce the idea of using Csound with a sound editor, enter csLADSPA
and Audacity(basic signal modification/processing). Module 3 is
exclusively MIDI and Csound (more advanced synthesis techniques). The
final module introduces Cabbage. Students are expected to pull
together everything they have learned in the previous modules and
start developing Csound-based plugins(effects or synths).

A student asked me recently why they didn't have a play button on
their screen like the one they could see on my main teaching screen. I
told them to enable the toolbar in WinXound and showed them how to on
the projector. They said they didn't have that option. I made another
few suggestions, to which the students again replied 'it doesn't
work?'. So I made my way down to find that the student in question had
CsoundQT open instead of WinXound! I guess he must have been looking
so hard for the darned play button that he neglected to realise he was
using a completely different software to everyone else!


On 9 April 2014 09:42, Askwazzup  wrote:
> I found that while CsoundQt was a more convenient way to setup the options,
> it often crashed on me for various reasons on windows and linux. Winsound i
> only used briefly, so can't comment on it.
>
> Now i use the terminal (in linux) and vim editor with the csound syntax
> plugin, for the colored syntax. This i found to be the best route for me and
> i also learned more about the CsOption flags this way.
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Csound-on-Windows-tp5734042p5734044.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
>

We have four modules that use Csound. Students must take the first
two, after that they have a choice. WinXound/Csound6 is used in module
1. This is all score driven work(basic sound synthesis). In module 2 I
introduce the idea of using Csound with a sound editor, enter csLADSPA
and Audacity(basic signal modification/processing). Module 3 is
exclusively MIDI and Csound (more advanced synthesis techniques). The
final module introduces Cabbage. Students are expected to pull
together everything they have learned in the previous modules and
start developing Csound-based plugins(effects or synths).

A student asked me recently why they didn't have a play button on
their screen like the one they could see on my main teaching screen. I
told them to enable the toolbar in WinXound and showed them how to on
the projector. They said they didn't have that option. I made another
few suggestions, to which the students again replied 'it doesn't
work?'. So I made my way down to find that the student in question had
CsoundQT open instead of WinXound! I guess he must have been looking
so hard for the darned play button that he neglected to realise he was
using a completely different software to everyone else!


On 9 April 2014 09:42, Askwazzup <aistiskaikaris@mail.com> wrote:

I found that while CsoundQt was a more convenient way to setup the options,
it often crashed on me for various reasons on windows and linux. Winsound i
only used briefly, so can't comment on it.

Now i use the terminal (in linux) and vim editor with the csound syntax
plugin, for the colored syntax. This i found to be the best route for me and
i also learned more about the CsOption flags this way.



--
View this message in context: http://csound.1045644.n5.nabble.com/Csound-on-Windows-tp5734042p5734044.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

We teach Csound for both Mac and Win students here at ntnu. I tend to think that the command line is the safest and simplest. We also teach cabbage from early on in the course as it is very convenient for the students to plug their custom modules into a daw workflow. I love qt too,  but the command line is more transparent for teaching.

We teach Csound for both Mac and Win students here at ntnu. I tend to think that the command line is the safest and simplest. We also teach cabbage from early on in the course as it is very convenient for the students to plug their custom modules into a daw workflow. I love qt too,  but the command line is more transparent for teaching.

9. apr. 2014 17:29 skrev "Michael Gogins" <michael.gogins@gmail.com> følgende:

Windows is my main platform for running Csound. I also run on Linux sometimes.

On Wiindows, in order of decreasing usage:

CsoundQt. It crashes for me sometimes, but I need those widgets.

SciTE, a text editor with customizable commands, it will automatically run csd files using Csound, or Lua files using LuaJIT. But no widgets.

The Windows command line. If things are crashing I run on the command line to see more information.

WinXSound, sometimes.

blue, occasionally.

Cabbage, occasionally.

None of these environments actually meets all of my needs!

Hope this helps,

Mike

-----------------------------------------------------

Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Wed, Apr 9, 2014 at 4:32 AM, Luis Antunes Pena <k_o_m_p@yahoo.de> wrote:

Hello,

I will use csound to teach a new course and would like to gather some of your experience running csound on windows. I would like to ask how do you currently run csound on windows. Do you use CsoundQt, WinSound? Do you run csound from a terminal? Blue, Cabbage? What would you advise?

Thank you for your help.

Best,
Luis

--
http://luisantunespena.eu

Not as serious as it looks! It's kept very simple throughout. In year
one they will do additive synthesis, and some simple AM and Ring
Modulation. They will also have built several simple time-domain
csLADSPA effect such as flangers, reverb, chorus, wah-wah etc., which
they can use for their EA composition modules. Year 3 is more about
controlling instruments, with MIDI introduced first and then VST
plugins. One or two more techniques such as FM and subtractive
synthesis are introduced within these modules too, but overall it's
quite basic stuff. I guess we might be unique in that all of our sound
synthesis/processing modules use Csound. I wonder why ;)