Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
General Board / FOF Strecht Breakpoint Pitch
« Last post by Marcelo Carneiro on October 31, 2023, 04:08:15 AM »
Hi. I don't know how to creat a breakpoint pitch for FOF Strecht program. Do I have to analyse/extract the audio file pitch from some tool and create a txt file from it? Which tool is that?
Thank you
22
Mac installation / Re: CDPv8 and M1
« Last post by rwdobson 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.
23
Announce / CDP Release 8
« Last post by rwdobson 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
24
Mac installation / Re: CDPv8 and M1
« Last post by pmj on October 24, 2023, 01:36:17 PM »
Hi Seán

I've had a look at 'ssfunc.h' and there's this section:

#define MSBFIRST        (1)
#define LSBFIRST        (1)
/* RWD extended set of symbols ! Now works for Mac universal Binary build */
#if defined(__I86__) || defined(_X86_) || defined(__x86_64) || defined(__i386__) || defined(__i486__) || defined(_IBMR2)
#undef MSBFIRST
#elif defined(M68000) || defined(__sgi) || defined (__POWERPC__)
#undef LSBFIRST
#else
#error  "Unknown byte order for this processor"
#endif

#if defined(MSBFIRST) && defined(LSBFIRST)
#error  "Internal: can't be both MSB and LSB"
#endif

What would I need to change that to (if that's the correct bit...?)

There is a homebrew for portaudio here:

https://formulae.brew.sh/formula/portaudio
25
Mac installation / Re: CDPv8 and M1
« Last post by Seán on October 19, 2023, 08:01:56 AM »
Hello pmj,

I tried building last Spring on an M2 and this was the first problem I encountered. This was luckily a simple fix. In 'ssfunc.h', there is an if/then clause somewhere which is referring to the byte order for the processor. You need to change this to force the byte order to 'LSBFIRST' for the ARM processor.

This got me past this error but the next problem was with portaudio. I was unable to install portaudio on the M2. Well, I thought I did, it seemed to build fine, but I could not point the CDP make files towards it no matter what I tried. If you manage to get the portaudio portion working I would love to know how! There is no Homebrew etc for portaudio as far as I know.

All the best,
Seán
26
Mac installation / Re: Going to use the terminal in OSX
« Last post by sleestack on October 07, 2023, 10:27:39 PM »
I’m enjoying using it in terminal. Only thing missing I guess is a little breakpoint app.
Hopefully I’ll continue using it this way.  I’ll keep u posted on my progress.
27
Mac installation / Re: Going to use the terminal in OSX
« Last post by Robert Fraser on October 02, 2023, 02:06:28 PM »
You're right, Frank, the old email is gone, at least for now. (I posted a notice about this I think.) My web-host wanted money for each email address, formerly free. Please use ensemble-software at hotmail.com . 
Thanks, Robert     
28
PC Installation / Re: Missing Folder - InvertPch?
« Last post by Robert Fraser on October 02, 2023, 01:52:10 PM »
I've posted a general follow-up called "Data Files in Soundshaper". A little more on InvertPch, though:

• There appears to be a bug when processing stereo files. The script will need revision and I'll look into that.
• The original CDP InvertPch works with extracted pitch-data files (.frq). These are then combined with a formant file (.for) for re-synthesis.
  Soundshaper's "Invert pitch contour" (not the "Alternative method") does this all within one script, extracting and altering the pitch data and then resynthesising using a formant file taken from the original sound. (The lower-level method is still available via the PitchData menu.)
• I ran a test using a simple speech file of four words, three of which are clearly around MIDI 55 (tenor G3) while number 3 dips down a semitone.
  I used a map file of -1 11 and 1 -11 and an ABOUT value of 55 (ie invert around G3) and got a fairly convincing inversion of the sound an octave higher with the semitone shift going up instead of down (G4 and Ab4).
• A different ABOUT value (60) gave a similar result transposed up to E5/F5: I'm not sure I understand the logic of the inversion here (I didn't write the program!).
• The "Alternative method" uses the Release 8 (forthcoming) SPECFNU 15. This processes formant values directly. To my ears this would be less useful - more muddy.
• Overall, playing with formant and/or pitch can only degrade the original sound quality in some way. For example, altering pitch only "works" to the extent that the new frequencies are also present in the formant file it's combined with. (For this purpose, you might consider transposing the original sound and extracting that formant file.)
• I tried extracting the source's pitch as a text file and displaying that in the Graph Editor, the idea being that the display might tell you the pitch content. It probably does, but it looked over-detailed and I trusted my ear and a nearby keyboard better!
29
General Board / Data files in Soundshaper
« Last post by Robert Fraser on October 02, 2023, 01:48:48 PM »
This post is in response to a query about datafiles in Soundshaper (see "Missing Folder - InvertPch?" , Oct 1 2023).

Not being a realtime system, CDP works with (and is dominated by) files: source sound files (or other types), processed files to save, automation via breakpoint text files, and more specialised data files most of which are described in the documentation (see the link to File Formats from any reference Program Group, e.g. BLUR).

When a data file option is selected in Soundshaper's parameter page, a text box appears for the filename (instead of a control for a fixed value). This is filled in with a default value of the Process Name and a Filename; the Process Name is given as a subfolder of the user's Text Data folder. If an actual file exists, it is displayed as text in the Data Edit Panel (to the right of the page). Many parameters have such files - usually very basic templates - especially breakpoints, mainly so that these can be edited in the Graph Editor.

For more specialist data, a file might not always be supplied, so the Data Edit box is empty (for the user to fill in) and the Process Name subfolder may not exist either. This may seem like an anomaly, but it allows you to fill in suitable data and click SAVE to save this to the default location from where it will be recalled automatically next time. Having a standard folder for each process also allows you to save your own datafiles there for easy recall, although an alternative is to save these to a project folder of your choice.

When datafiles are amended, the SAVE CHANGES button is activated to save the data to a temporary file. These temp files are an important aspect of Sounshaper's process chains (shown on the patch grid); to re-edit or re-run the process it must have a specific datafile for that particular operation. (You might have used the same process with different values elsewhere in the patch.) So don't be surprised if your default file changes from e.g. \MagicProcess\scrunch.brk to something like ~A_1\scrunch.brk, or ~X_1\scrunch.brk for a preview.

When patches or presets are saved, the temp files actually used are saved with the patch or preset, for future recall.
30
Mac installation / Re: Going to use the terminal in OSX
« Last post by Robert Fraser on October 02, 2023, 10:58:14 AM »
I'm afraid life (preparing for CDP8) got in the way here too! No further progress on updating the Creative Sound Design tutorials, I'm afraid, but I should be able to complete this task from late October. I can post a notice to the Forum when done.
Pages: 1 2 [3] 4 5 ... 10