Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Robert Fraser

Pages: 1 2 [3] 4 5
Announce / Soundshaper 5: support for Csound
« on: April 30, 2019, 09:13:40 PM »
The latest Soundshaper update (5.03) adds support for running Csound scripts, as well as users' own Batch scripts. The Csound scripts can either be for synthesis, writing to an output file, or for sound processing, with one or more input files. (Real-time output is not supported at present.)

The inputs and outputs are integrated within Soundshaper patches (process chains), i.e. a Csound process can precede or follow a CDP process, and the overall patch can be saved and recalled. Taken together, CDP and Csound cover a vast range of audio processes and a huge number of Csound examples are readily available, particularly for synthesis, which by comparison is a bit thin within CDP.

The update also includes Csound's implementation of Paulstretch (extreme time-stretching), hard-coded as a "normal" process with parameter control. I will be looking for other opcodes and scripts that would be worth integrating in this way and would welcome any suggestions and feedback.

Announce / Soundshaper 5 released
« on: March 01, 2019, 10:54:11 AM »
Soundshaper 5.0 (beta) has now been released. This version has important new features designed to improve workflow:
 - built-in streaming player/viewer, with extensive provision for editing and processing part of the sound
 - multi-layer patches: patches extended to multiple layers. Embed a patch within a patch; save and load this as a single object within a patch and so on
 - revised Process List: supports user-saved parameter settings (single presets) for rapid recall of favourite processes
 - improved file-saving
 - re-designed Main Page: clearer layout and menus. Support for many new skinned styles.

Soundshaper 5 (PC only, Vista-Win10) can be downloaded from .

Mac installation / Re: Soundshaper for OSX coming?
« on: February 07, 2019, 10:18:09 PM »
Soundshaper has been run successfully on Mac via Parallels and similar products. Not having a Mac, I can't test this. Apart from hardware limitations, I'm in the middle of upgrading Soundshaper to v.5.0, which has to precede any possible port.

General Board / Re: Applying multiple fx
« on: August 26, 2018, 02:54:14 PM »
Yes bash is almost identical to CMD. I don't have a Mac, but do have winbash if you're stuck. Try reading Richard Dobson's guide to Terminal, particularly his advice to change directory (cd) to where some sounds are; you'll see his CDP command lines are identical to those for Windows. As I'm sure you know, you no longer need .aifs for Mac, but CDP can handle them anyway, ir you can use COPYSFX to convert them to WAV.  The Terminal document is here:

General Board / Re: Applying multiple fx
« on: August 12, 2018, 07:37:54 PM »
In Windows CMD, you would write a batch script, the core of which is a sequence of CDP statements, something like this:

modify brassage 6 %1.wav %1(brassage).wav 0.7 5.0 100 0 1 0.5 5 5
reverb  %1.wav %1(reverb).wav 0.5 0.5 1 0 0 5
pvoc anal 1 %1.wav %1.ana -c1024 -o3
blur blur %1.ana %1(blur).ana 20
pvoc synth %1(blur).ana %1(blur).wav

%1 is a parameter you're passing to the script, in this case the name of your source file (e.g. "myfile.wav"), which is the common infile for each command line. You save the script to a text file and then change its extension to .bat (e.g. "mybatch.bat"). You then call the bat within CMD by typing:

mybatch myfile

...where myfile substitutes for %1 in the script. You don't need to call it as mybatch.bat, though you could. You mustn't put myfile.wav because that text would substitute for %1 and would become (in the first line):
 modify brassage 6 myfile.wav(brassage).wav [etc] which wouldn't work.

For blur, the infile is first converted to .ana using pvoc anal and afterwards back to sound using pvoc synth. Of course we could run a number of spectral commands with %1.ana. We can also delete the .ana files when we're done with them; after the pvoc synth line add:
 erase %1.ana
 erase %1(blur).ana

We also need to tell CMD where to find CDP programs and our files.  Unless you copy CMD.exe to your project folder, you need to make that folder the current one:
(or whatever the folder's called) - if it's in the same drive as CMD; if a different drive, put the drive name first, e.g.:
(for the folder E:\SNDS\MYPROJ)

These statements can be typed at the console before running the script.

To point the script to CDP programs, you need a PATH statement, e.g.:
 PATH C:\CDPR7\cdprogs
This can also be typed at the console, or put in the script before any CDP command lines.

The script itself is probably best put in the project folder, beside its infile. If not, the script needs the full path to the infile, e.g. call it as mybatch E:\SNDS\MYPROJ\myfile so that %1 picks up the whole path\filename. (My own preference is to use a single processing folder and copy all sources to that using copysfx, but that's another story.)

Finally, note that CMD takes only parameters %0 to %9, so there's very limited scope for passing values to the script. This is a pain, because CDP typically uses many parameters. The answer to this and other scripting issues would be to run CDP from something like PYTHON, but that solution will need some careful planning first.

Announce / Soundshaper 4.5.05 released
« on: March 12, 2018, 12:04:53 PM »
A new version for Soundshaper (4.5.05) has now been released for Windows. All users are recommended to download this version, which is available as an update to an existing 4.5, an upgrade to a previous installation of 4.4, or as a full version.

The Mix Page has been extensively revised and repaired in this version. CDP mixes are very versatile, especially for relatively short sounds and the revised page aims to make them as easy to manipulate as possible. A revised Soundshaper HTML reference for the Mix Page is also available for download and is included as a .PDF in the upgrade.

Quick-help documentation for all CDP processes has now been completed and is accessible from within Soundshaper. Other bugfixes repair a number of CDP functions that were not working.   

General Board / Re: add second file
« on: October 02, 2017, 09:34:07 PM »
Please see the thread "How to perform with spectral processes", which raises the same question. The answer is that a single-click is needed when you select the second input file from the grid. One of the replies in that thread describes it in great detail.

I will, however, change the coding in the next version of Soundshaper (or earlier) to interpret a double-click as a single one when the Add Input panel is visible.

PC Installation / Re: Soundshaper - can't use "edit at markers"
« on: June 30, 2017, 08:32:04 PM »
The error is a CDP message - there's a flaw in the path for the paste-file: the " character should be a backslash \ .

I've now posted (July 1st) a revised Soundshaper.exe to the website:
This removes the inverted commas which were surrounding the paste-file name (Infile2).

You're also using the desktop for your TEMP file. This was not always the ideal place for any CDP files as it used to (maybe still does?) have spaces in the path. I would suggest setting the TEMP file to a much shorter path with no spaces.

General Board / Re: How to perform with spectral processes?
« on: June 19, 2017, 08:59:12 PM »
Hi Phoenix cat,
When you select the first file, it will load into cell A_0 by default. Now click on cell B_0 and select the second file.  Click back on A_0. Select the process e.g. COMBINE CROSS (Menu: Spectral> Morph/Formants> Cross), and the red "Second Infile" panel appears for you to select the 2nd infile. Click on cell B_0 to do this and click the panel's OK button to proceed to the parameter page. CROSS has only one parameter-- REPLACE (degree of replacement - I usually set this to 1). Click OK or hit RETURN to run the process and return the result to Cell A_1.   

You are correct that CDP requires a conversion from wav to ana, but Soundshaper does this automatically. So the infiles can be soundfiles, as the program will auto-convert then into anas behind the scenes for a spectral process. (You can also convert them first if you prefer.) The output is also converted back to .wav if Option 5 (Auto-FFT) is checked. The output cell A_1 is coloured aqua for a spectral file, but the player will play the .wav conversion rather than invoke PVPLAY to play the .ana file directly. If you don't like the result, double-click the output cell (A_1) to return to the parameter page or hit CTRL+Z or the delete key to erase the output.

For the initial selection, the reason you have to click the cell you want to load into (actually you can just click its row) is so that you could load a file into any row. If Soundshaper just selected the next row down, this would not be as flexible. You don't need to use the file pool, but I find it helpful to stock this with commonly used sources -- it depends on your project. Also, you can load a file by drag+drop from any folder open in Windows Explorer. Again it will load into the currently selected row.  Soundshaper can also process stereo or multi-channel files for spectral processes. If you've chosen, say, one mono and one stereo source for COMBINE CROSS, it will combine channel 1 of the stereo source with the mono. (This generally works better than mixing to mono, but again you could do this yourself first.)   Hope this helps, Robert

Announce / Soundshaper 4.5 released
« on: June 13, 2017, 09:26:14 PM »
A new version of the Soundshaper interface (4.5) is now available ( This introduces the new Cell-Patch feature, in which an existing patch can be run within one cell. A patch containing one or more of these sub-patches can be saved and re-run as normal.  (Full details are in the supplied Release Notes.)

Parameter Files (.prm) can now be dropped onto the Main-Page patchgrid. This opens a parameter page with the appropriate parameters and values, so it's a quick way of selecting and running a preset. Parameter files are simple text files which can be saved from a parameter page (as 'snapshots') and are also produced as temporary files in the normal course of running Soundshaper.

General Board / Re: Gotta drop some love for this documentation
« on: May 05, 2017, 09:38:12 AM »
Oops! I'll get that link changed right now. 
The correct link is:
This is also accessible from the updates page (
Sorry about that.

General Board / Re: Gotta drop some love for this documentation
« on: April 29, 2017, 09:42:02 AM »
That's good to hear, though we still haven't got the revised docs into the distribution yet...
Make sure you're accessing the latest stuff, online at or you can now view or download printable pdfs for offline use.

Announce / CDP Documentation available as printable PDFs
« on: April 04, 2017, 06:45:20 PM »
The CDP reference documentation (excluding tutorials) has now been converted into printable PDF format and can be accessed here:

This page has links to download the PDF docs as well as the HTML docs as zip files, and also to view individual PDFs online. There is a link to the online HTML docs, which is also duplicated in the menu (CDP > Online Documentation > CDP Docs Home Page).

(Various charts and a couple of papers were already online as PDFs and are included within the HTML zip.)

General Board / Re: TMP folder causing crashes in Soundshaper
« on: November 03, 2016, 10:35:23 PM »
Sounds good. It's quite possible that the scripting for a particular class of processes has a minor fault -- you'll appreciate that because of the sheer size of CDP, a bug might go undetected in tests.  Another (more likely?) possibility is CDP's own reaction to certain inputs: lengths, levels, number of windows, even frequency ranges. (A simple example is FILTER VARIBANK - a wonderful program if you do the work to ensure no harmonic will crash the Nyquist boundary.) Some comments in this forum about defective documentation have to be seen against this background. 

Anyway, do report any specific malfunction and we can get it sorted.

General Board / Re: TMP folder causing crashes in Soundshaper
« on: October 24, 2016, 10:21:16 AM »
Thanks for your replies.  The count sound should be OK. The warning message "<filename> not found" is just Soundshaper's message that the CDP program appears not to have worked. For most processes, a CDP error message will also normally be displayed, provided there is one.  Roomverb is working on my Win10 machine, both with mono and stereo inputs, and it does produce error messages (e.g. for room size= -1).

Have you checked the paths in Settings, as I mentioned above?  -- especially the temp folder and more importantly that the CDP programs folder is correct? Also that you actually have rmverb.exe in there? (note the spelling, not roomverb). [I know these checks sound obvious but they're the cause of most problems that have arisen in the past.]

It is possible to set up a terminal (command window) in Windows to run either single command lines or a batch file, including the one Soundshaper assembles (e.g. ~A_1.bat in your rmverb example; this should be in your TEMP folder.)  For the command line, the Soundshaper batch files currently name the in/outfiles in a non-friendly way (e.g. rmverb  %2_%3.wav  %n%_%o%.wav 1 0.5 0.5 0 0 0 5),  but you can amend this to something more obvious like count.wav (in) and countvb.wav (out). (You can't run these batch files "as is", unfortunately, without knowing the arguments that are being passed to the batch.)

There is more than one way of setting up a CDP terminal, but mine is to copy CMD.exe from the Windows folder to the TEMP file and then write and run a simple batch file (CDP.bat) which I also place in the TEMP folder:

REM cdp.bat for Release 7.0
echo off
PATH E:\CDP\cdpr7\_cdp\_cdprogs
echo ***********************   COMPOSERS   DESKTOP   PROJECT   **********************

The PATH statement should lead to your CDP programs folder; mine is on drive E:, but yours may be somewhere else. In fact this folder can be anywhere unless you're running Soundloom, which expects the directory structure \_cdp\_cdprogs.

To run this, launch the terminal from the taskbar (right-click on the CMD.exe icon and select Pin to Taskbar) and type "CDP" (for "CDP.bat").

Back to your specific issues, I'd still like to know if VIBRATO runs OK or not! Also, I feel you may be better pursuing this directly with me by e-mail ( I'll be happy to post the solution here when we find it: there is one!

Pages: 1 2 [3] 4 5