28 Sep
2008
28 Sep
'08
5:20 p.m.
On Sun, Sep 28, 2008 at 11:43 AM, Paul Davis <paul(a)linuxaudiosystems.com> wrote:
On Sun, 2008-09-28 at 12:08 -0400, Darren Landrum
wrote:
I was skeptical to see the claim that csound "cannot do oversampling"
(not because of some knowledge of oversampling, but rather past
experience with a) how comprehensively synthesis techniques are
represented in csound and b) how easy it is to prototype synthesis
techniques directly in csound). There is an article on csound journal
http://www.csounds.com/journal/issue6/BandLimiting.html describing the
hows and whys of oversampling, and it uses pd rather than csound in
most of the examples(!). This should be informative because not only
does it show how to make a butterworth filter in pd from scratch, but
it gives a good explanation of what oversampling aims at, and how to
implement it in just about any computerized audio processing
environment.
Did I misunderstand what I have found about oversampling, or is it
just another name or special case for bandlimiting of arbitrary
signals?
Why couldn't we make something like that for audio? It would most likely
be C++ rather than Java, but the idea of building up DSP networks using
a large framework of code, plus some pre-defined functions and settings,
and being able to launch our new code with a one-touch button into a
JACK client (or whatever), is extremely appealing to me.
SKINI, Chuck, Faust and CSound/SuperCollider spring to mind.
Throw in some
GUI-building elements (Cairo-based, perhaps) that can handle
mouse-clicks, keyboard input, and the like,
oops ...
Processing has wrapped a language with a lot *less* power than
SuperCollider in a front end that is much easier to learn. Its a shame.
But it also seems to be way the world works.
--p
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev