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,
No email has come through yet (but sometimes these things are slow).
You've given me the path of your temp folder. I would like to check your CDP programs folder (go to Options | Settings, it should be listed there).
I'm not happy that the temp path has a space in it - could you not rename the \CDP ss\ bit to \CDPss\ ?
Also, your temp folder seems to be using OneDrive - for good reasons no doubt -  but I hope that's not slowing things down if it's syncing to the cloud. That might be the root of the problem.
Thanks,
Robert

I have sent you the soundfile in an email

I hope that it's these you meant,
CDP programs:
C:\Users\kostp\OneDrive\Desktop\Cdp ss\Temp

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 Robert
i've tried the things mentioned in your previous response, however i still cant get it to work. It  still writes "failed to copy new source file" and then "File doesn't exist".

The way i get the files from Audacity to Soundshaper, is in the same way as you mention in your reply.

A small extra observation regarding spaces in names - Soundshaper does in fact support importing source files with a space in the name and a source folder also with a space in the name. (I've just tested this.)  However, I would recommend that the Temp folder should NOT have any spaces in its name.

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.

I recently downloaded Soundshaper 6. After i had it installed in 2 days i wouldn't open because of "Missing/cant find Bass.ddl files" which i find very odd since the files where in the same folder as the program itself.

i tried reinstalling Soundshaper. this helped partly, now i am able to open it, if i open it directly from the folder i have it in, but it still wont open if drag the program out of the folder. Now there's just another problem. when trying to get soundfiles (Wav. 16bit 44k hz; export from Audacity) into Soundshaper, both when "importing them" and when dragging them, it first shows a message saying "failed to copy new source file" and then "File doesnt exist".

Any guesses to what might be going on?

Hiya everyone. I've been trying to install CDP today and run into a few issues. Once moving the cdpr8 folder into my home directory, running cdp8install.command gives me this message:

x@x's-MacBook-Air ~ % /Users/x/cdpr8/cdp8install.command ; exit;
CDP Install script: Mode 1.
CDP Install script ERROR: unable to create new .bash_profile.

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

[Process completed]

Just in case you're wondering, I've replaced any username information with an 'x'.

I've tried a few fixes to this:
In the Manual Configuration document, it states that, after typing 'env' into a new Terminal, 'If PATH already includes the above CDP path,   we are good to go'. When I type env into a terminal, the correct path does indeed appear, yet I'm clearly not 'good to go'. Regardless of this, I tested out creating my own .bash_profile file as via the Manual Config doc. Depending on where I install the .bash_profile file in my home directory, the 'ls -la' command also displays it, yet the installation command still doesn't work, and the error message remains the same.

Any ideas as to why this might be? Thanks

Hi besb1n,  I'm sorry I didn't discover this thread until today. I'm assuming the issue is with Soundshaper on the PC.

Soundshaper uses the CDP function copysfx (rather than Windows copy) to copy your source sound to the temp. folder - typically to a file named ~A_0.wav.  Copysfx supports a wide number of formats and once copied, CDP processes will nornally support the given format (e.g. 16-bit .wav, 32-bit float etc.) It doesn't support .mp3 or .flac though.

However, copysfx runs in Windows' Command Processor which imposes its own constraints. Here are a few things you can test for:

1. Make sure there are no spaces in the source and temp file paths. That applies to both the file name and the file folder.
2. Both the file name and file folder names should conform to ASCII standards - characters like é, ç and ö are not supported (though they may be in Windows).
3. Check the path for CDP programs. The default is \_cdp\_cdprogs within your CDP base folder such as C:\CDPR8.
   Select Options | Settings (or F5) to see the path assigned to CDP Programs and check it is correct.
4. Occasionally with this problem, we've found the user file had a format that copysfx didn't support, though this seems unlikely if no files will copy.
5. For both 3. and 4., try running copysfx directly in the Command Processor:
   Type the name of the drive if different from the one in the prompt, then type cd <folder_name> (put in the name of the source folder. You can copy and paste this from Windows Explorer.) This makes your source folder the current one.
  Then type copysfx <source_filename> ~A_0.wav and see if it works.
6. You can also take a look at the batch file which runs copysfx. It should be in your Temp. folder, called ~A_0.bat and should contain a line like:
   copysfx %1 "E:\SOUNDS\TMP\~A_0.wav"
  (E:\SOUNDS\TMP\ is my own temp folder on this PC. %1 refers to the source file name, which the program substitutes for this variable.)

If none of the above reveal anything useful, we may need to look at a typical file that fails, and the batch file running copysfx, and a screenshot of your settings. You can send these to me via email.