Composers Desktop Project Forum

uge:
Thanks for the feedback. Really glad to know Soundshaper is still working in Parallels.

Hi James,

The normal order for most CDP programs is: infile outfile params, where the first parameter in this case is the datafile.
However, the program's usage (duplicated in the CDP documentation) is given as: infile datafile outfile etc.
If you change this to the normal order, the program should work (I think), i.e.:
  newmorph newmorph2 2 temp-w1.ana temp-morphed1.ana temp-pk2.txt 0 12 1 8

I've tested this with various files on the commandline.
However, while investigating this I hit a problem of my own, which is the persistent error message:
  ERROR: end of interpolation is beyond end of one of soundfiles.
Given that my start and end times were well within the limits of the ONLY soundfile, this doesn't make any sense.

Anyway, I hope the above commandline works for you. We'll change the documentation when every mode has been tested.

Robert




 

I recently bought a new PC with Windows 10 and had some fun (?) with administrator problems. I already had a version of Soundshaper on a disk I'd transferred from the old computer, and also imported a new build from another PC to the C drive. Neither would run or even close down as they weren't allowed to over-write various textfiles: "access is denied"!

The solution seems to be to tick a box called "Run as administrator". You have to create a shortcut to the .exe, right-click on the shortcut icon for its "properties", then from the pre-selected Shortcut tab choose Advanced, then tick "Run as administrator". This works, but produces an annoying User Account Control window every time you run the program.

Somehow I've created two shortcuts for the new version: one has "Run as administrator" and opens with the User Account Control (and fails otherwise), but the other (on the desktop) starts perfectly without "Run as administrator" being selected.

If anyone can explain this conundrum, I'd be grateful.

Access Violation has been fixed in the latest version 5.07, now available for download.

I'll look into the aspects of Create Envelope File. (Pity that was not a separate thread and I would have caught it before releasing 5.07. Too bad.)

The Access Violation affecting Texture Grouped (and Decorate) has been pinned down and fixed. I'll need to do many more tests to confirm this and will issue a replacement .exe as soon a possible.   

In the end, it wasn't anything to do with Texture Grouped. I assumed the data was being read in wrongly or parameter-related objects (like slider ranges) were being re-defined at the wrong time. No, it was re-writing the page title. So I put this later and all was well.  Just the sort of geeky Windoze-type of problem I do programming for. Or not.   

And why did it affect only Texture?
-- No idea. Computers are magic. Sometimes they behave like magic too.

I've tracked down where the A.V. occurs, but not why. It's something to do with the initial display of the parameter page when it's re-visited to edit the parameters. The weird thing is it doesn't do it every time -- but every OTHER time, consistently.

However, this gives a workaround: click CANCEL to leave the parameter page and try again (double-click the cell again). This seems to work. A third edit will give another A.V. but the 4th should be OK and so on. You will also get one when you exit the program.

In my searches through the code, I found a different serious bug affecting all processes with >10 parameters, mainly TEXTURE and GRAIN. I've issued an interim .exe correcting this (5.06).

Meanwhile I'll continue to look for the cause of the A.V. You're correct, rotagrad, that the bug also affects TEXTURE DECORATE.  But the same workaround seems to work. Maybe whatever these two have in common will give a clue...

Sonora, Thanks for getting in touch by email and thanks for your patience.

Unfortunately, the problems are still unresolved (at 8 Apr.). The program was not reading the CDP programs folder correctly from the configuration file, despite the fact that the file was correct and the folder was there. It was also not shutting down correctly. Both of these issues need further investigation, though neither has arisen in other installations, as far as I know. While we were exchanging emails, you reported that you had installed Soundshaper successfully on another Win10 computer. I have also tested it recently on 3 Win10 64-bit machines, one Win10 32-bit, one Win7 64-bit and one Win7 32-bit.

The problem may have something to do with the fact that Soundshaper is a 32-bit program running, in this case, on 64-bit Windows. Having said that, Windows automatically runs such programs using its built-in emulator WOW64, so in theory issues should not arise. You also tried running it in Win7 mode, without success. Re-building Soundshaper in native 64-bit would be possible, but could require a lot of work -- I'll look into this.

We will continue to communicate and experiment with other solutions and report back to the forum if we solve the problems.