Composers Desktop Project Forum

Hi sleestack. If I understand your question correctly, then yes, the result is a directory of command line tools that can be used to alter and mangle audio.

Like with OSX, one of the benefits of this is the ability to create sophisticated scripts to process sounds with a bunch of steps.

This post is following up on another one of my posts that concerns compiling the tools under linux.

I thought that I had been able to compile the CDP tools correctly because the more simple tools worked without a problem. When I tried running the pvoc programme to create analysis files I bumped into a problem.

Running the following (and assuming that an analysis file ends in ana or is user specified) I received the following errors:

./pvoc anal 1 ./shsyn.wav output.ana
ERROR: INVALID DATA
ERROR: Cannot open output file output.ana
*** Error in `./pvoc': double free or corruption (top): 0x08872c60 ***

I have removed some of the memory dump here.


Though I have little c programming skills, I went digging with a debugger. I the problem seemed to be a problem in line 4574, file sfsys.c which does:

if((ext = getenv("CDP_SOUND_EXT")) == NULL) { /* error handing code that I omitted */ }

In the terminal I set the environment variable CDP_SOUND_EXT and run the command:

./pvoc anal 1 ./shsyn.wav output.wav

The .wav file is rather odd being 344hz file with 1024 channels. I think it worked! If I set the environment variable to ana, it does not work.

Still have to tinker to see if I can use the commands that require analysis files.

This does leave me with the question though - is this request for the environment variable necessary? Is this the intended behaviour? Is this indicated somewhere in the documentation that I have not seen?

Also, is there some sense in creating a git repository? I have been tinkering with the linux Makefiles (the ordering of some of libraries is wrong for gcc on Ubuntu anyway). Is there a good way to make code contributions? I could provide a diff?

Thank you for the help. I will give this a try. I should also that most of the other tools were built, so I have been happily mangling sounds for the last couple of days.

I hope you will not mind me spamming this topic with the steps that I needed to do to get everything working.

To get those 32 bit versions, I removed the .a files from the sub-directories, ran make -f Makefile.linux and then copied those the libfsys.a (etc.) files into the lib folder in the top of the folder hierarchy that is extracted from the downloaded CDP archive.

There is an old versions of portaudio in the /dev/externals/paprogs -- delete it or rename it, then extract the .tgz file. Now work in this folder (the instructions this, but just for clarity)

In order to compile portaudio (instructions found in: /dev/externals/paprogs/portaudio), I had to install the the alsa dev package to get ./configure to output Alsa = yes.

sudo apt-get install libasound2-dev

Will compile away -- as the instructions say: DON'T RUN -- make install, this may mess up audio on your system.

Go to the dev folder and run makeprograms.sh -- everything compiles happily.

Seems to have a problem with libportsf.a. I am going to try to recompile it to see if it is like the other .a files that were compiled for 64 bit architecture. Does not seem to compile. Returning:

portsf.o: In function `psf_sndCreate':
portsf.c:(.text+0x378f): undefined reference to `double_to_ieee_80'
portsf.c:(.text+0x3da2): undefined reference to `double_to_ieee_80'
portsf.o: In function `psf_sndOpen':
portsf.c:(.text+0x45d9): undefined reference to `ieee_80_to_double'
portsf.c:(.text+0x5129): undefined reference to `ieee_80_to_double'
collect2: error: ld returned 1 exit status
make: *** [portsf] Error 1

Will have to get some sleep. Will try to return to this tomorrow.

Thanks for the quick reply! I have done as you said and indeed I can compile those libraries. I still have a few compilation issues to work on (still messing around with the portaudio). Some programmes worked and I have already made some weird sounds.

As a strange little aside, before you responded, I thought I would try CDP under wine. The programmes I ran worked so that is also an option for another linux user who is less interested in busying themselves with compilation.

Hi, I am not sure if you know, but your software is being mentioned at http://createdigitalmusic.com/2014/05/watch-bt-reveal-sound-design-tricks-free-geeky-cdp-learn/ and I think re-posted over at Synthopia, so good job!

I wanted to ask you about the Linux version of the command line tools. In the downloaded package there are two closed source object files: libcdp2k.a and libsfsys.a

Of course it is your prerogative to keep them closed, but they are compiled for a 64bit architecture, and as such I cannot compile the tools for my 32 bit Ubuntu machine.

I am quite excited to try these tools out, I was wondering if it would be possible to provide a 32bit version?

Many thanks for all your hard work.