Composers Desktop Project Forum

The portsf build requires the file ieee80.c which is/should be in the portsf directory, and referenced in Makefile.linux. You may need to run make clean if I managed to leave some object files in the distribution. 

Good point about alsa dev; I will need to add that to the install instructions.

The usual cause of this error message is that the environment variable CDP_SOUND_EXT has not been defined (to wav). This can be done via Control Panel->System Settings->Advanced->Environment Variables.

We are in the process of preparing an update release (all platforms) where this variable is internally preset to wav by default, so that setting it explicitly will be optional. We will of course announce the update here, as well as on the CDP download page.

OK, thanks,  I have found another place in the snack makefile where I need to add the flag for 10.5.x support, rebuilding now, will post updated version shortly.

Yes, indeed there is. There is one further "hidden" task handled by the installer which it sounds like you need to make; it is specific to the Mac (and, now, also Linux when Soundloom is ported). Soundloom can be installed anywhere (e.g. in /Applications); which means it has to be told where the CDP programs are. This is done by means of a small hidden text file placed in the user's home directory, ".sloomrc". The leading dot means it is not visible either in the Finder, or in a normal directory listing in Terminal. It just contains the path to the CDP programs. So, if they are inside (as we recommend):
 /Users/name/cdpr7/_cdp/_cdprogs

(where "name" is your account name), that is the line which must be placed in .sloomrc.

What version of  Soundloom do you have?  This was fixed in either 14.0.3 or 14.0.4 as I recall; certainly if you do not have 14.0.4 you need to update to that (via Trevor's website).

Richard Dobson

Yes, this is the standard message from the Sandbox mechanism, for any app not downloaded from the AppStore or otherwise "signed". As noted, this "protection" (which we would have to pay for) does not extend to command line tools, which might lead one to suspect this is as much a marketing tool as a serious attempt to protect users. The only practicable solution at present is to got to Preferences->Security... and enable "allow .. from anywhere". 

Hello, this is entirely my fault, a low-level build detail was wrong in the sfsys library (test code that shouldn't have been included was included!); it unfortunately meant rebuilding all the programs. This is done, and once I know the revised installer has reached the public download page I will post again here.

Richard