Hey all,

Being a programmer by trade, I am used to the code-compile-test cycle
of doing things, but I'm finding it arduous for Csound. I see a lot of
people talking about the various IDEs for Csound, and I assume that
they are boosting people's productivity. What would you all recommend
for designing instruments in a more interactive, touch-and-feel sort
of way? Are there any good pieces of software for Linux-based
musicians that improve upon the code-compile-test way of life?

~ C.

-- 
When the facts change, I change my mind. What do you do, sir? ~ Keynes

Corbin Simpson

Granted I don't have a Linux System, but the only linux based choices I know
of for IDEs are WinXound or CsoundQT (also known as qutecsound). Normally I
would say to use cabbage along with it but a linux version of cabbage isn't
available yet.

Here is a link to WinXound, it's not available in 3.4.0 yet but it is
available in 3.3.x.

http://winxound.codeplex.com/releases/view/54192



--
View this message in context: http://csound.1045644.n5.nabble.com/Designing-instruments-using-IDEs-tp5716791p5716792.html
Sent from the Csound - General mailing list archive at Nabble.com.

As the largest proponent of the command line I feel I need to comment!

For experimentation with instruments I use the FLTK idgets.  I used to use
the Tcl/Tk external controls but no one else ever used them as far as I
can tell, and the FLTK route offers more options.

Cabbage builds on Linux for me, but I have not managed to work out how to
use it yet.

Of course when the instruments are ready it is back to makefiles

==John ff


> Granted I don't have a Linux System, but the only linux based choices I
> know
> of for IDEs are WinXound or CsoundQT (also known as qutecsound). Normally
> I
> would say to use cabbage along with it but a linux version of cabbage
> isn't
> available yet.
>
> Here is a link to WinXound, it's not available in 3.4.0 yet but it is
> available in 3.3.x.
>
> http://winxound.codeplex.com/releases/view/54192
>
>

I use blue for all of my work and it runs on Linux, Mac, and Windows.

I've used all the approaches discussed here, as well as conventional
studio sequencers and notation software running Csound, also used to
use RTcmix and have fooled around with Pure Data and some of Lisp
synthesis stuff.

It's clear that the best approach will, in the end, very much depend
on the individual user and his or her particular musical goals and
working style. There is no rule that fits all.

It's also clear that, if one's working life is reasonably regular,
continuing to work with a given tool set will improve one's musical
skill and productivity. So, it's important to settle on the right
tools and more or less keep using them, not without experimenting with
others from time to time in case one has missed something important.

Regarding my own work, I do pretty much only algorithmic composition,
pretty much only with Csound, prettty much all rendering to soundfile.

I compose in C++, using CsoundAC to help with compositional
housekeeping, and the Csound API for rendering music. I use a text
editor only. I do not use makefiles, as all my pieces are in one .cpp
file each. My text editor is set up to compile and link my pieces,
then run them to produce the music, with customized key bindings. I
use the FLTK widgets for user interfacing, I've found that being able
to tweak instruments and effects during rendering is useful even for
someone like me.

If I were going to create compositions intended for live performance,
I would probably switch my FLTK widgets for the Qt SDK and use
qtcreator to write and build my pieces.

I can also see where environments such as blue could be very useful,
it would all depend on how one thinks about the pieces being worked
on. I think blue would probably be better than what I do, if I were
spending more time "assembling" my pieces from parts, instead of
"generating" them in pretty much one go.

If I were notating pieces, I would use Sibelius and then I would
create VST plugins using Csound via Cabbage for the "electronic"
parts.

Hope this helps,
Mike


On Sat, Oct 13, 2012 at 5:07 AM, Steven Yi  wrote:
> I use blue for all of my work and it runs on Linux, Mac, and Windows.
>
> On Oct 13, 2012 9:36 AM,  wrote:
>>
>> As the largest proponent of the command line I feel I need to comment!
>>
>> For experimentation with instruments I use the FLTK idgets.  I used to use
>> the Tcl/Tk external controls but no one else ever used them as far as I
>> can tell, and the FLTK route offers more options.
>>
>> Cabbage builds on Linux for me, but I have not managed to work out how to
>> use it yet.
>>
>> Of course when the instruments are ready it is back to makefiles
>>
>> ==John ff
>>
>>
>> > Granted I don't have a Linux System, but the only linux based choices I
>> > know
>> > of for IDEs are WinXound or CsoundQT (also known as qutecsound).
>> > Normally
>> > I
>> > would say to use cabbage along with it but a linux version of cabbage
>> > isn't
>> > available yet.
>> >
>> > Here is a link to WinXound, it's not available in 3.4.0 yet but it is
>> > available in 3.3.x.
>> >
>> > http://winxound.codeplex.com/releases/view/54192
>> >
>> >
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com