I just wanted to know a bit more about the Composers Desktop Project
software. I read that this incorporates some Csound code. I can't find
too much info about the software. I read up that Richard Devine used
it, and read up somewhere that it used csound elements in it.

Is it worth looking into? Is is easy going from Csound to CDP, or does
it incorporate other audio programming languages?

I am a Core Developer for CDP (well, one has to have some sort of 
title!); so feel free to email me or Archer Endrich off-list for CDP 
questions. Most of the software however is written by Trevor Wishart 
(whoi continues to ply us with wierd and wonderful processes we have to 
figure out), and does not incorporate Csound code as such. However we 
have a very long history with Csound going back to the birth of the 
system in the early 80's, and supplied early versions of it with the 
original Atari-based system. A few contributors wrote tools that 
generated Csound scores or data for hetro (and we supported the "cscore" 
utility as a stand-alone program).

The two systems are not directly comparable, so it is not so much a 
question of "going" from one to the other, as finding complementary uses 
for both. Partly because of our support for Csound, CDP has virtually no 
synthesis tools as such (or even standard dsp things for that matter, 
apart from a set of filters and filter banks, etc) - almost all the 
programs are focussed on performing musique-concrete style 
transformations. And of course the programs are all "offline" tools; 
apart from the occasional foray into plugin design (hoping to do more 
ere long) the CDP system itself does not offer any real-time processing 
facilities; it is all soundfile-based.

The CDP website is at:

http:/www.composersdesktop.com
See also Trevor's site: http://www.trevorwishart.co.uk

I don't really know exactly what bits of CDP Richard Devine and other 
composers use (apart from the granular synthesis tools which are widely 
cited); but he, Aphex Twin and BT have all indicated they use it from 
time to time - along with all sort of other things including Csound 
(which BT is especially associated with). One web forum had a nice 
comment about CDP as "archaic and interesting" - who could  ask for more?

Richard Dobson



gary hiebner wrote:
> I just wanted to know a bit more about the Composers Desktop Project
> software. I read that this incorporates some Csound code. I can't find
> too much info about the software. I read up that Richard Devine used
> it, and read up somewhere that it used csound elements in it.
> 
> Is it worth looking into? Is is easy going from Csound to CDP, or does
> it incorporate other audio programming languages?
> 




Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Thanks for the info Richard. I will check out the website. The
software sounds interesting. I am using CSound more as a sound
manipulation tool than for any realtime processes. So it will be
interesting to check CDP out.

On 8/17/09, Richard Dobson  wrote:
> I am a Core Developer for CDP (well, one has to have some sort of
> title!); so feel free to email me or Archer Endrich off-list for CDP
> questions. Most of the software however is written by Trevor Wishart
> (whoi continues to ply us with wierd and wonderful processes we have to
> figure out), and does not incorporate Csound code as such. However we
> have a very long history with Csound going back to the birth of the
> system in the early 80's, and supplied early versions of it with the
> original Atari-based system. A few contributors wrote tools that
> generated Csound scores or data for hetro (and we supported the "cscore"
> utility as a stand-alone program).
>
> The two systems are not directly comparable, so it is not so much a
> question of "going" from one to the other, as finding complementary uses
> for both. Partly because of our support for Csound, CDP has virtually no
> synthesis tools as such (or even standard dsp things for that matter,
> apart from a set of filters and filter banks, etc) - almost all the
> programs are focussed on performing musique-concrete style
> transformations. And of course the programs are all "offline" tools;
> apart from the occasional foray into plugin design (hoping to do more
> ere long) the CDP system itself does not offer any real-time processing
> facilities; it is all soundfile-based.
>
> The CDP website is at:
>
> http:/www.composersdesktop.com
> See also Trevor's site: http://www.trevorwishart.co.uk
>
> I don't really know exactly what bits of CDP Richard Devine and other
> composers use (apart from the granular synthesis tools which are widely
> cited); but he, Aphex Twin and BT have all indicated they use it from
> time to time - along with all sort of other things including Csound
> (which BT is especially associated with). One web forum had a nice
> comment about CDP as "archaic and interesting" - who could  ask for more?
>
> Richard Dobson
>
>
>
> gary hiebner wrote:
>> I just wanted to know a bit more about the Composers Desktop Project
>> software. I read that this incorporates some Csound code. I can't find
>> too much info about the software. I read up that Richard Devine used
>> it, and read up somewhere that it used csound elements in it.
>>
>> Is it worth looking into? Is is easy going from Csound to CDP, or does
>> it incorporate other audio programming languages?
>>
>
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>

I have been looking into this as well. Apparently Richard Devine was using 
a tool called Sound Loom, which is found in the CDP. Here is a listing of
some 
of its capabilities. http://www.trevorwishart.co.uk/transformation.html

Of course some of this stuff sounds familiar and probably has counter
parts in the csound world. Has anyone here used Sound Loom?
I am curious to know how the interface works and if it would be 
possible to create a similar tool in csound.



Anthony



gary hiebner-2 wrote:
> 
> I just wanted to know a bit more about the Composers Desktop Project
> software. I read that this incorporates some Csound code. I can't find
> too much info about the software. I read up that Richard Devine used
> it, and read up somewhere that it used csound elements in it.
> 
> Is it worth looking into? Is is easy going from Csound to CDP, or does
> it incorporate other audio programming languages?
> 
> -- 
> Sent from my mobile device
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
> 
> 

Afaik Sound loom is a GUI frontend for CDP. Many of the processes in
CDP can already be achieved using Csound. It would also be easy to
develop a GUI frontend for Csound instruments that do spectral
manipulations.

Rory.


2009/8/25 apalomba :
>
> I have been looking into this as well. Apparently Richard Devine was using
> a tool called Sound Loom, which is found in the CDP. Here is a listing of
> some
> of its capabilities. http://www.trevorwishart.co.uk/transformation.html
>
> Of course some of this stuff sounds familiar and probably has counter
> parts in the csound world. Has anyone here used Sound Loom?
> I am curious to know how the interface works and if it would be
> possible to create a similar tool in csound.
>
>
>
> Anthony
>
>
>
> gary hiebner-2 wrote:
>>
>> I just wanted to know a bit more about the Composers Desktop Project
>> software. I read that this incorporates some Csound code. I can't find
>> too much info about the software. I read up that Richard Devine used
>> it, and read up somewhere that it used csound elements in it.
>>
>> Is it worth looking into? Is is easy going from Csound to CDP, or does
>> it incorporate other audio programming languages?
>>
>> --
>> Sent from my mobile device
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Composers-Desktop-project-tp25013883p25136952.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>


Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

In a sense, people already are; SoundLoom is a GUI front-end written in 
tcltk (in Trevor Wishart's unique style of design) to the CDP programs 
(most of which he wrote - that page is really a summary of his CDP 
processes); it is not a self-contained or standalone tool. Similarly, 
the various Csound front-ends drive Csound internally, while adding all 
manner of infrastructure on top. A primary impetus from Trevor's point 
of view was a desire for a system that would help him manage the 
sometimes literally thousands of soundfiles used in a composition  (some 
tools automatically extract N files from an input file). It is 
interactive in that sense, but not in any other - all processing is 
strictly offline, non-destructive file-based (like Csound used to be!).

Richard Dobson



apalomba wrote:
> I have been looking into this as well. Apparently Richard Devine was using 
> a tool called Sound Loom, which is found in the CDP. Here is a listing of
> some 
> of its capabilities. http://www.trevorwishart.co.uk/transformation.html
> 
> Of course some of this stuff sounds familiar and probably has counter
> parts in the csound world. Has anyone here used Sound Loom?
> I am curious to know how the interface works and if it would be 
> possible to create a similar tool in csound.
> 
>



Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I guess that is what I am getting at. It seems like Sound Loom
is a tool that consolidates all these processes into one interface.
This certainly makes exploring the transformation of sound 
a lot easier. I wish there were something like that for csound.

I know you code do a good number of similar processing with 
the PVS opcodes. But trying to tie together disparate opcodes
and transformation techniques into one work environment 
is a lot of work.

At some point I want to make music!



Anthony


---- Richard Dobson  wrote: 
> In a sense, people already are; SoundLoom is a GUI front-end written in 
> tcltk (in Trevor Wishart's unique style of design) to the CDP programs 
> (most of which he wrote - that page is really a summary of his CDP 
> processes); it is not a self-contained or standalone tool. Similarly, 
> the various Csound front-ends drive Csound internally, while adding all 
> manner of infrastructure on top. A primary impetus from Trevor's point 
> of view was a desire for a system that would help him manage the 
> sometimes literally thousands of soundfiles used in a composition  (some 
> tools automatically extract N files from an input file). It is 
> interactive in that sense, but not in any other - all processing is 
> strictly offline, non-destructive file-based (like Csound used to be!).
> 
> Richard Dobson
> 
> 
> 
> apalomba wrote:
> > I have been looking into this as well. Apparently Richard Devine was using 
> > a tool called Sound Loom, which is found in the CDP. Here is a listing of
> > some 
> > of its capabilities. http://www.trevorwishart.co.uk/transformation.html
> > 
> > Of course some of this stuff sounds familiar and probably has counter
> > parts in the csound world. Has anyone here used Sound Loom?
> > I am curious to know how the interface works and if it would be 
> > possible to create a similar tool in csound.
> > 
> >
> 
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"


Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"