15 Sep
2003
15 Sep
'03
2:21 p.m.
Hi Atte,
I've used Csound alot in the past too. Mostly command line from Common Music which I
like alot. I'm trying to go more real-time though now. I just decided I would try
and get into PD!
How is your orchestra set-up. Do you have 1 synth per instrument per channel? I always
had a hard time in Csound as I wanted to have 1 synth per 16 channels and have them all
have their own set of presets. PD supports multiple midi ports so I thought that would
probably work, though learning another language will be tough as I know Csound well. I
also want the graphic routines, and as you know Csound dosen't have the Opengl stuff
in Linux, (yet). I also don't understand the status of Csound right now. Is anyone
actually working on coding Csound5? I'm on the lists but can't tell.
Thanks,
Ken
-----Original Message-----
From: Atte Andr? Jensen <atte(a)ballbreaker.dk>
Sent: Sep 15, 2003 8:47 AM
To: linux-audio-user(a)music.columbia.edu
Subject: Re: [linux-audio-user] Linux synths
On Mon, 15 Sep 2003 07:44:23 -0700 (GMT-07:00)
Ken Locarnini <renueden(a)earthlink.net> wrote:
I'm happy to be back after about 2 years away from
Linux. The
audio/music world seems to be taking off and thats great.
Indeed!
I'd like some general comments on what would be
peoples favorite
reactor type synth in Linux as of now. I'm primarily interested in
realtime, multi timbral midi controlled synths.
I simply love csound. It's flexible, powerful, stable and well
documented. I know that some (most?) people find the fact that it's text
based a minus, but I don't agree. After working with pd intensely for a
couple of weeks I realized that I work much faster in csound.
I'm running csound under debian/unstable on kernel 2.6.0-test5 with a
csound buffersize of 128 on a PIV 2400 laptop, using Evolution USB
keyboards as controllers. I have more polyphony in real time than I can
use with two hands for "normal" (subtractive, fm, sample playback,
soundfont playback, additive) patches. This is even with a few global FX
units (chorus, delay and rotary speaker) running all the time.
The only not-so-nice thing about csound is that I didn't manage (or try
that hard, actually) to make it run alongside other sound-producing
applications, including jack, pd or fluidsynth. Could be a problem if
you want to use LADSPA plugins or do hd-recording...
How about sequencers?
I didn't work much with sequencers under linux, but FWIW I've settled on
Muse. Needless to say it's quite simple to route midi events from Muse
to csound.
--
peace, love & harmony
Atte
15 Sep
15 Sep
2:49 p.m.
New subject: [linux-audio-user] Linux synths
On Mon, Sep 15, 2003 at 09:06:37AM -0700, Ken Locarnini wrote:
I've used Csound alot in the past too. Mostly
command line from Common Music which I like alot. I'm trying to go more real-time
though now. I just decided I would try and get into PD!
Csound can do realtime stuff also.
How is your orchestra set-up. Do you have 1 synth per instrument per channel? I always
had a hard time in Csound as I wanted to have 1 synth per 16 channels and have them all
have their own set of presets. PD supports multiple midi ports so I thought that would
probably work, though learning another language will be tough as I know Csound well. I
also want the graphic routines, and as you know Csound dosen't have the Opengl stuff
in Linux, (yet). I also don't understand the status of Csound right now. Is anyone
actually working on coding Csound5? I'm on the lists but can't tell.
csound supports that also.
This is how you bind different instruments to midi channels:
; massign ichnl, insnum
massign 1, 1
massign 2, 2 ;bind instr 2 to midi channel 2
massign 3, 2
openGL support I don't know about that but you can use fltk controlers or tk
sliders. A good environment maybe cecilia using fltk controlers and or tk sliders. The
fltk controlers can be data entry fields sliders, nobs, or whatever.
On the other hand pd can use csound as an extension. Can you do non
realtime stuff in pd. I was wondering if you can render stuff as a wav
or aiff in non realtime. The reason I ask is if you have extremly
complex tasks that your computer can't do in realtime you have that
rendered instead. Then if you can composite openGL and the audio
together into a format similar to divx or something that would be really
cool.
Right now I am using gimp,povray, or blender to do animation like stuff
and csounds for audio. I then composit them in Cinelerra.
Jeremiah
16 Sep
16 Sep
7:13 a.m.
New subject: [linux-audio-user] Linux synths
Hallo,
Jeremiah Benham hat gesagt: // Jeremiah Benham wrote:
On Mon, Sep 15, 2003 at 09:06:37AM -0700, Ken
Locarnini wrote:
Can Csound do runtime changes to its patches now? I think one of the
major differences between Pd/(j)Max and 'compiled' languages like
Csound or sfront is the ability to directly edit a patch while it is
running. It's a bit like: Csound is great if you know what you're
doing in advance, while with Pd you can experiment and immediatly hear
or see what you're developing while you're doing so.
Of course it is dangerous to just let Pd patches stay that: an
interactive work-in-progess mess. But in general I've found that in Pd
I would build things - with the same "opcodes" or building blocks as
in Csound -, I would have never thought of while still using Csound.
I *think* (never used it yet) that Supercollider is somehow in between
in that it has a dynamic, interactive language interpreter a bit like
the one in Python.
Supercollider seems to be the coolest anyway. I want Debian packages
of it ;)
ciao
--
Frank Barknecht _ ______footils.org__
I've used Csound alot in the past too.
Mostly command line from
Common Music which I like alot. I'm trying to go more real-time
though now. I just decided I would try and get into PD!
Csound can do realtime stuff also. 
7:23 p.m.
New subject: [linux-audio-user] Linux synths
On Tue, 16 Sep 2003 10:58:08 +0200
Frank Barknecht <fbar(a)footils.org> wrote:
Well of course you have to make a change to your text file, save it and
rerun csound on it. Maybe the emacs mode and friends make things more
interactive, but the old way works great for me. But I must admit that
this is probl. only because I use realtime input from keyboards with
assignable potmeters 90% of the time. If we're talking pure csound
driven by an .sco file I'm working much too slow. In fact I never
completed one single project in pure csound.
Csound can do
realtime stuff also.
Can Csound do runtime changes to its patches now? I think one of the
major differences between Pd/(j)Max and 'compiled' languages like
Csound or sfront is the ability to directly edit a patch while it is
running. It's a bit like: Csound is great if you know what you're
doing in advance, while with Pd you can experiment and immediatly hear
or see what you're developing while you're doing so. Supercollider seems to be the coolest anyway. I want
Debian packages
of it ;)
Maybe one ought to check it out. Just for the fun of it...
--
peace, love & harmony
Atte
15 Sep
15 Sep
3:31 p.m.
New subject: [linux-audio-user] Linux synths
Ken Locarnini wrote:
I'd like some general comments on what would be
peoples favorite
reactor type synth in Linux as of now. I'm primarily interested in
realtime, multi timbral midi controlled synths.
Hi Ken:
FWIW, my Linux Journal article on Linux software synths is now
on-line:
http://www.linuxjournal.com/article.php?sid=6320
It may help you get an idea of the state of things in May 2003...
Best regards,
== dp
5:31 p.m.
New subject: [linux-audio-user] Linux synths
On Mon, 15 Sep 2003 09:06:37 -0700 (GMT-07:00)
Ken Locarnini <renueden(a)earthlink.net> wrote:
Hi Atte,
I've used Csound alot in the past too. Mostly command line from
Common Music which I like alot. I'm trying to go more real-time
though now. I just decided I would try and get into PD!
Sounds like me two months ago. Maybe you make it (I didn't) :-)
How is your orchestra set-up. Do you have 1 synth per
instrument per
channel?
One long (1600+ lines) .csd file with
* one "patch/synth" per instr which gives one one patch per program
change
* a few global (always on) fx instruments
* a special "output instrument" that does a little eq + compression
* patching/routing with global variables.
Each USB keyboard sends on a seperate midi channel, but they all access
the same pool of patches. Since the Evolution will let you assign a
program change to each of the 0-9 buttons (and remember them after
poweroff) I always use the same Evolution for the same thing (one for
pads for instance) and program each button to point to different
instr's.
I always had a hard time in Csound as I wanted to have
1 synth per 16
channels and have them all have their own set of presets.
You could run multiple instances of csound, which might (or might
not...) give relatively poorer performance. But I don't understand why
this configuration is paramount to you..??!?
PD supports multiple midi ports so I thought that would
probably work,
though learning another language will be tough as I know Csound well.
Be prepared that pd doesn't handle polyphonic patches gracefully IMHO.
I also want the graphic routines, and as you know
Csound dosen't have
the Opengl stuff in Linux, (yet).
Might be, never messed with that...
I also don't understand the status of Csound right
now. Is anyone
actually working on coding Csound5?
AFAIK the guys are working like mad, cleaning up code (and API's?) and
preparing for csound5. I even thing it's for download somewhere, maybee
sourceforge somewhere. You might also be pleased to hear that csound
recently turned GPL. There are still a few contributed opcodes that
haven't been GPL'ed (scanned opcodes for instance) but that's probl.
gonna happen soon from what I hear.
--
peace, love & harmony
Atte
7788
days inactive
7789
days old
linux-audio-user@lists.linuxaudio.org
5 comments
5 participants
participants (5)
-
Atte André Jensen -
Dave Phillips -
Frank Barknecht -
jjbenham＠chicagoguitar.com -
Ken Locarnini