Composers Desktop Project Forum

Hi Aila, I still don't seem to have received your email. The current email address can be found on the Contacts page at www.soundshaper.net. Looking forward to getting this issue fixed! Robert

Hi Aila,
Could you send me an example of a file that doesn't work? (Email can be found at soundshaper.net). Also, can you send me a note of the path of your CDP programs.   I need to test this for myself with an actual file.

Thanks,
Robert

Hi Aila, Please see my reply to a similar thread under "PC Installation": Topic: cant import files.

Regarding bass.dll, it simply has to be in the same folder as Soundshaper.exe and the installation puts it there. I'm sorry you had an issue with this and I'm glad your re-installation seems to have fixed it. The Bass library is 3rd-party and it's possible we may need to ship a more up-to-date version, but I've not had problems with it to date. I'd be interested to hear from any others who've had a problem with Bass.

Regarding the copy issue, if there's a fundamental problem, I'd like to get to the bottom of it and fix it, but as I show in the other thread, the command line is very straighforward so I think it will be something else - either incompatible file types or spaces in the file path. How are you "exporting" from Audacity to Soundshaper? I would tend to export from Audacity to some folder and then drag that file into Soundshaper - I don't know of a more direct way.

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.

"Soundshaper works very fine on WINESKIN port for MAC"
This could be very important for MAC users - I looked up Wineskin, but found different versions and I'm not sure which to download. Any help you can give on this, and how to use etc., would be hugely appreciated. 

The PSOW (FOF) programs require a pitch-trace breakpoint file extracted using PTOBRK WITHZEROS.  And that requires a pitch file (.frq) extracted from a frequency analysis file (.ana), using REPITCH GETPITCH 1.  This is all better put in a little script (Windows CMD batch file or MacOS bash shell script).

Here are two similar scripts: the first kindly supplied by Richard Dobson for bash, and my own batch file (PC) based on Soundshaper. Both make use of arguments supplied on the commandline - particularly the infile and outfile names. Bash scripts have variables $1, $2 and so on, referring to the first, second etc. arguments; the equivalent in CMD batch files is %1, %2, etc.   Both scripts assume a mono input sound.

First, Richard's bash script frqtotext: note the usage "frqtotxt insndfile outtextfile", where outtextfile is the name of the pitch-trace file.

#!/bin/bash
echo frqtotxt.sh - shell script to prepare pitch-brkpnt-data file for
echo                use with a FOF-source file: lengths must match.
if [ $# -ne 2 ]
    then
        echo usage: frqtotxt insndfile outtextfile
        exit 1
fi
echo
echo pvoc anal 1 $1 infile.ana
pvoc anal 1 $1 infile.ana
echo repitch getpitch 1 infile.ana infilepchdummy.aiff infile.frq
repitch getpitch 1 infile.ana infilepchdummy.aiff infile.frq
echo ptobrk withzeros infile.frq $2 20
ptobrk withzeros infile.frq $2 20
echo Delete \(temporary\) files no longer needed:
echo rm infile.ana
rm infile.ana
echo rm infilepchdummy.aiff
rm infilepchdummy.aiff
echo rm infile.frq
rm infile.frq

Now the BAT version, which adds parameter values for the application PSOW STRETCH. In this example the file suffixes are in the script, so would not be supplied on the commandline:

REM %1 is input wav (just the name without .wav); %2 is the output wav (also without .wav)
REM %3 is amount of stretch; %4 is no. of grains
echo ***** PSOW STRETCH BATCH SCRIPT (PC) *****
echo off
REM  Convert wav to ana
pvoc anal 1 %1.wav %1.ana -c1024 -o3
REM Extract pitch
repitch getpitch 1 %1.ana %1pch.ana %1.frq 
REM erase unwanted pitch file             
erase %1pch.ana   
REM Create pitch-trace text file                                   
ptobrk withzeros %1.frq %1.pch 20   
REM Stretch the input sound                     
psow stretch %1.wav %2.wav %1.pch %3 %4   
REM Erase intermediate files...             
if exist %1.ana erase %1.ana                             
if exist %1.frq erase %1.frq                             
if exist %1.brk erase %1.brk
REM Optionally play the output
if exist %2.wav paplay -i %2.wav 

A typical commandline for this might be fofstretch my mystr 2.0 20. For test purposes, put the script in the same folder as the input file.
 

Thanks for your bug report. The parameter pages are clearly not loading for some reason. Not sure at this stage whether this is genuinely a Windows 11 problem or not. I'll test the program on Win11 and report back.