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 - rwdobson

Pages: [1] 2 3 ... 5
1
Mac installation / Re: soundloomE file damaged
« on: November 26, 2023, 11:06:43 PM »
This is the usual Gatekeeper response to a non-signed app downloaded from the bet. The solution is described in the README file: run the Terminal command:

xattr -rc /path/to/soundloomE.app

The best and recommended approach is to run xattr on the whole cdpr8 directory inside the Disk image. This will process everything, including soundloomE.app.
 

2
Mac installation / Re: CDPv8 and M1
« on: October 30, 2023, 11:06:55 AM »
The messages here have all pointed to the correct place in the code, sffuncs.h. This issue in fact raises an interesting "strategic" question which I have been pondering: are big-endian platforms now effectively dead? if so, all that code can be eliminated (including a lot of dependent code in sfsys) and let it assume the host machine will always be little-endian. This would be an problem however if anyone hopes to build for a cherished PowerPC machine such as an old G5.

In the meantime, the solution needs to use a symbol that is also used in the relevant CMakeLists.txt file. On the Mac the simplest solution would be to add || defined(MAC) in the sffuncs.h line, as that is used in all the CMakeLists.txt files throughout CDP. If supporting big-endian platforms remains important, some new symbol can be defined such as __ARM64, to be used in both places.

Those building CDP8 from source from Github may like to consider posting questions such as this (which are not about "installation" issues as such) directly via the Github message system. I will receive these immediately through email, and can respond accordingly. This  doesn't require anyone to be "registered" as a developer. I have already answered quite a few queries this way.

3
Announce / CDP Release 8
« on: October 27, 2023, 03:40:20 PM »
We are proud to announce CDP's 8th software release, with over 80 new processes written by composer Trevor Wishart. 

Release 8 adds to the CDP's toolset especially in the manipulation of formants, wavecycle distortion, segmentation and repetition, plus new multichannel processes and synthesis functions.

The CDP system is a comprehensive sound design toolkit of over 450 processes. Developed over 35 years, it covers almost every aspect of sound transformation, including many that may be unfamiliar or are presented from an original or compositional viewpoint.

CDP is not a real-time system or a suite of plugins, but transforms sound-files (or their spectral equivalents) to create new sonic material.

CDP is released under a Creative Commons/LGPL licence as free software for MacOS, Windows and Linux, with sources available on GitHub.

Further details,downloads,workshops,tutorials and more can be found at the CDP website:

 https://composersdesktop.com/

Richard Dobson

4
Mac installation / Re: CDPv8 and M1
« on: March 13, 2023, 06:52:25 PM »
Hi Natasha,

yes indeed, we are very close to being able to announce Release 8 along with full packages for Mac and PC. We have had several reports of success building CDP (including R8) from source. We have made a lot of code updates recently, mostly to eliminate compiler warnings, but catching a few minor bugs as well.  At present, the Github resource is still to be regarded technically as "Beta".

With regard to existing installers (v 7.1.1), again we have had good reports of successes there on M1. Being a download and not having an official Apple certificate, the "Gatekeeper" system prevents opening, but there is a standard solution which we have documented.

I have just posted the latest beta build of the CDP programs for Mac here:

http://www.rwdobson.com/MacR8-13-03-23.zip

It is compiled for Intel machines (unfortunately CDP does not have access to an M1-based Mac), but I am assured that the new M1 "rosetta" system works as expected and all the programs will run.  Documentation preparation is at an advanced stage, but not ready for release yet. We will publish it at the same time we announce the full CDPR8 release.

Richard Dobson

5
General Board / Re: SFEDIT CUTMANY
« on: June 27, 2022, 12:34:30 PM »
I have tested this with the same OS version (and both 2016 build and the latest build) and not been able to reproduce the problem. It would be helpful to have example command lines and data file to reproduce as closely as possible. Test reports from other users would be welcome too!

Richard Dobson

6
The idiomatic way to do this is to use the shell scripting facilities. It is a good idea to read up on shell commands (and practice a little before committing to anything serious). Simple commands can be done directly at the prompt, but most of the time you will want to create a text file for your script. Here is an example to copy files to a named subdirectory:

#!/bin/bash
# usage  copyfiles.sh outdir
# copies wave files in current directory to same names in directory outdir
# outdir will be created if not present
# copysfx must be in system PATH

if [ -z $1 ]; then
  echo "usage: ./copyfiles.sh outdir"
  echo "outdir will be created if it does not exist."
  echo
  exit
fi

if [ $1 == "." ]; then
echo "can't copy files into same directory!"
echo
exit
fi

if [ ! -d $1 ]; then
    mkdir $1
fi

for filename in *.wav
do
   copysfx $filename $1/$filename
done

7
General Board / Re: newtex newtex problem with parameters
« on: July 13, 2020, 06:35:59 PM »
The final argument (36) needs the -s flag, and then the documentation example works (it is a Mode 3 example, not Mode 1). So this should work with your input file:

newtex newtex 3 perc1mono.wav perc1_tex.wav 30 4 3 0.1 0 0 1.5 0.35 -s36



8
General Board / Re: newtex newtex problem with parameters
« on: July 13, 2020, 03:03:04 PM »
Yes, it appears the documentation has some errors - we are looking into it. The example command line is missing the all-important "transposes" data text file, and has too many parameters - the final one for Mode 1 is "spacetype". The strange error message arises because (a foible of most modern operating systems!) a number such as "30" can be a legal file name; at the stage the message appears, it has not been opened to verify it is the right sort of data file.

9
General Board / Re: Soundloom on Linux
« on: May 24, 2020, 10:14:36 PM »
A port to Linux is in preparation, but will not be ready for a while yet, not least as recent updates (V17.0.4) need to be incorporated, and completing the update to the Mac version is also a priority. Only one developer (me) is involved in all this.  Note that for Linux users Soundloom would be supplied in source form (tcl files).  Enterprising users with some tcltk coding experience can download the current Windows sources from Trevor Wishart's Soundloom pages, and try it out (edit "sys.cdp" in _cdpenv to contain "LINUX" rather than "PC", and then you may need to modify any code that refers to programs with .exe extensions, so that the native Linux programs get called). However, despite the nominally cross-platform nature of tcltk, there are aspects that exploit Windows features and which have had to be significantly revised to suit the Mac. I expect a final Linux version of Soundloom to combine elements of both PC and Mac versions, one way or another.

10
General Board / Re: Phase Vocoder frame 0
« on: November 19, 2019, 10:22:09 AM »
In that particular pvoc implementation (Mark Dolson original author decades ago), the first frame in an analysis file is all-zeroes. Other implementations may skip that, but the arithmetic is the same. In the general case, all bin phases have to start from somewhere on the circle, so to speak, and the default choice is zero, just as it tends to be for any digital oscillator. since pvoc is based on the FFT, converting phase increments to frequency, each bin has a (default) centre frequency arranged linearly from DC to Nyquist.

In theory, any other starting phase could be used; one would expect this to be the same value for all bins, but there have been suggestions to start with randomised phases. Probably less useful for pvoc in analysis mode, but often a way to avoid extreme peak amplitude values when creating an oscillator bank. The Dolson pvoc code is certainly more difficult and opaque to read than others (some clever code involved to apply overlapped windowing while avoiding all memory movements); but the payoff is that it is significantly faster than other more "straight-forward" implementations.

11
General Board / Re: Can't start soundloom in mojave
« on: December 01, 2018, 12:14:51 PM »
I am glad you have got it working, but the permissions aspect is of concern.  We had so many permissions problems reported when users used third-party tools such as UnArchiver to unzip the distribution, that we have had to advise that users only use the native Apple utility (when you just double-click on the zipfile). I have yet to update to Mojave (I only have the one machine, and like to wait some weeks in case problems are reported). So it will be very helpful to know if you used the Apple utility, or a third-party tool.

12
General Board / Re: Uppercase .htm files in html documentation
« on: December 01, 2018, 12:08:17 PM »
Thanks for this - we are indeed getting a new distribution ready, with new html documentation by Robert Fraser, and all the file names will be in lower case.

13
perhaps use the "split" tool after grep, to pull out the duration field?

Re Windows, I suspect trying to use DOS (and maybe even powershell) will be a relatively unhappy experience. You might like to install minGW and the associated Msys shell, which gives you a bash shell and enough of the unix utilities to do most things. Any command you need that isn't provided already can probably be found on the net somewhere. but grep, cut, split etc are all there. I think Cygwin is much the same kind of thing, but I have no experience of that. I use minGW to build all the CDP programs for Windows.

14
Composition / Re: CDP and Renoise
« on: November 22, 2018, 10:54:30 PM »
What platform is this? You will need the latest/current 7.1 download of the programs. These avoid the need to install an environment variable, which could be the source of the problem. If you are on the Mac, there was also an error in compiling the release which meant that the program "housekeep" was incorrectly named "houskeep", and will need to be renamed. Sadly I do not have Renoise, so can't help with operational issues there - you would need to refer to the author of the Renoise CDP facility.

15
Mac installation / Re: Issues with Mojave
« on: November 22, 2018, 10:39:00 PM »
"Utilities" is the title towards the bottom of the Process panel ("Available Process menus"  - the list of processes to use); it should show from left to right 'SOUND INFO", "SPECTRAL INFO", "PITCH INFO" and "HOUSEKEEP". If the last is not shown, that means the program "houskeep" (or "houskeep.exe" on the PC) needs renaming. It is used by the CHANNELS process.

If it is shown, the problem lies elsewhere. At the risk of stating the obvious: if channel extraction is the first step in an Instrument, it expects at least a stereo infile, and will likely fail if the infile is mono.

There should be no need to reinstall Mojave - I am sure this is only a CDP/Soundloom issue.

Pages: [1] 2 3 ... 5