Composers Desktop Project Forum

the default directory of saved ana files in Soundloom is C:/cdp8/_cdp, how to change it?

I am also having this issue. PortAudio is installed on my system, and for good measure I installed libportaudio2 in case that is what is referenced, no change. I also did a search and the pa_ringbuffer.h file is in the portaudio directory.
I'm willing to try the solution you suggested of deleting the directories but which directories should I delete? Should I junk the whole build folder or should I get into specific ones and delete those to get it to correct itself?

Mode 2 means that the bash config file '.bash_profile' exists, but needs updating with the new PATH information. If this step fails, the usual reason is some problem with write permissions. This is a file that has to be in your home directory, the leading dot in the name makes it hidden (not displayed by the Finder). If - in your home directory - you type the directory listing command 'ls' with the flags '-la', so thus:

ls -la

It will included all the current hidden files and folder in the printed list. '.bash_profile' should be present. The -l flag makes all the current permissions printed along with each file name

You can then print the contents using the 'cat' command:

cat .bash_profile

It would typically show something like:

-rw-r--r--@  ....  .bash_profile

This show the file has write permission for the admin user, but is read-only for everyone else. If you are running as admin (as is the usual case for anyone running a personal machine), this would be fine. If not, the permissions would need to be set by someone with admin privileges.

I can't diagnose further without more information, e.g. the output from those suggested commands.

One final pont - if you are running any of the latest versions of MacOS, your default shell will be zsh, not bash. The install scripts also create an initial CDP config file for zsh, which should also appear in the directory listing (the title bar of the Terminal window will also indicate the zsh shell). I see no indication those file have failed to be created, so it may well be that in the z shell everything will in fact be up and running. Run any CDP program (such as 'dirsf') to verify one way or the other. Best to start a new Terminal session to be sure the new config information has been used.

Finally: I note you have run the xattr -rc command on Soundloom.app. This is fine as far as it goes, but my recommendation now (mentioned in the documentation) is to run it on the whole ~/cdpr8 directory (which will thus cover the app as supplied - the -r flag means 'recursive'), to ensure all the 140+ CDP programs are also covered. This will not in itself change any permissions though. R.

Hello!

I have placed the CDP8 folder in my Home directory and run xattr -rc on soundloomE.app but when I go to run cdp8install.command I get this error. I'm not very familiar with Mac and Terminal, so any assistance would be greatly appreciated.


Last login: Tue Jun 18 11:36:39 on ttys001
/Users/Studio-PC/cdpr8/cdp8install.command ; exit;
(base) Studio-PC@STUDIO ~ % /Users/Studio-PC/cdpr8/cdp8install.command ; exit;
CDP Install script: Mode 2.
CDP Install script copyfile: Error opening outfile /Users/Studio-PC/.bash_profile
CDP Install script ERROR: failed to write output to .bash_profile

Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

[Process completed]

thanks rwdobson, I had incorrectly assumed that folder inside my home folder (ie; Documents) would be fine, but I've moved it up a level and it works. Appreciate your quick reply and help : )

Caveat: sadly I am far from an expert on CMake. Yes, this is a strange problem. I have not been able to reproduce it here (Ubuntu, full portaudio install). I am assuming you are using the latest code set from github.

It does seem that CMake can get in a bit of a muddle, and the time-honoured solution has been to delete the whole CMakeFiles directory (in the 'paplay" directory inside the main 'build' directory set up before running Cmake for the first time). This will force CMake (when you  run 'make' in the build directory) to reconstruct all the internal config files, reading CMakeLists.txt to do so. You can inspect CMake's record of all target include files by checking the file CMakeFiles/paplay.dir/paplay.c.o.d. A quick way to reach this is using 'grep' recursively in, say, the paplay directory:

grep -R pa_ringbuffer .

Alternatively, run this from the build directory itself, which should find the instances for recsf, paplay, pvplay (four source files in all).

It is also useful to remember that you can run 'make' on a single target program to check it (e.g.: 'make paplay'), no need to run through the whole program set each time.

There are quite a lot of Command Line and Batch-file examples within the CDP Documentation, but they're not catalogued as such, so are maybe not easy to find (something we can look into).

However, I've thrown together a very basic tutorial on the Command Line and batch files, with examples, and put it here:
https://soundshaper.net/downloads/BasicCDPCommandline.pdf
It also refers to a more detailed document in the CDP documentation and also a couple of useful websites.
This is for Windows. Bash scripts for MacOS are very similar and more versatile, I think.

Batch scripts can be very useful for repeating standard tasks with variations of parameter values and sound files.

Hi All

What is the best way to learn how to operate CDP at the Command Line? I like the idea of running batch files. I use the SoundShaper and Process pack
a lot but, just for my own learning (is it more efficient than the GUIs?) I'd like to know how to get up to speed with the Command Line.

Thanks

CDP has only a fixed standard or "default" installation, which is in the user's home directory (as provided by the command shell "zsh" each time the Terminal app is launched, or a new shell Window is opened). The all-important PATH configuration assumes this. In the Finder is is shown by the little house icon, with the name chosen when running the machine for the first time -  = your User Name. Putting the whole CDPr8 folder in /Documents means that the PATH for command line users is then wrong, likewise also the file which tells Soundloom where the software is - hence the error messages. This can be fixed by hand editing the required hidden text files (see the document "Manual Install" for details), but we would strongly recommend that for the usual case of a single user on a single machine the software is indeed installed as per the README file etc, in your home directory. Whatever the CDP system might be, it is not "a document", and therefore "Documents" is not an appropriate location for it all.

Hi, M1 user here (running Sonoma), have followed the instructions for the 64-bit Mac installation (the 'cdpr8' folder is in my Documents folder, Ive run the executable command in Terminal - xattr -rc cdpr8 - and lastly I've run 'cdp8install.command'), but am getting the classic "No _cdp folder found!" error.
The 'SoundloomE.app' is inside the 'cdpr8' folder (although I did try all of this with it in Applications), is this a PATH issue? And if so what steps should I try to resolve?

Appreciate any assistance, cheers