Composers Desktop Project Forum

Attempting to build on linux from the latest source on github.

I've tried building following the instructions in the building.txt file. When I run the final 'make' command it fails at 99% with an error that it can't find pa_ringbuffer:
src/CDP8/dev/externals/paprogs/paplay/paplay.c:75:10: fatal error: pa_ringbuffer.h: No such file or directory
   75 | #include "pa_ringbuffer.h"


I am very noobish with cmake, but I had a look in the CMakeLists.txt file and it has this, which contains the folder where the pa_ringbuffer.h file is (..portaudio/src/common):
include_directories(../../include ../include ../portaudio/include ../portaudio/src/common /usr/local/include)

Anyone know why it's complaining it can't find it? I've also tried copying it into one of the other folders (../include) and it still says it can't find it.
Any ideas?

i cant import any .wav files. i get an error message "Failed to copy new source file." then "File does not exist."

tried changing my temp folder but it didnt do anything. any help would be appreciated.

Hello,
You may have already found this -

https://www.composersdesktop.com/pdf/tvinfopgnew.pdf

I think Archer has used TV quite a bit, I'll ask.

is there a tutorial for learning tabula vigilans?

Dear Robert,
I was not able to send a screenshot with detailed error message cause apparently the image embedding on the forum did not work, I'm sending you a mail.
Thanks again,
Alessandro

Quote from: Robert Fraser on May 06, 2024, 05:20:20 PM
When you mentioned the "SETUP PROBLEM" message, it's a pity you didn't list the apparently missing folders. The message means that the value (folder-name) assigned to each of these listed folders is invalid - the folder does not exist.  Several of them are read in from the textfile Soundshaper.cfg - I'm wondering if your student copied an old Soundshaper.cfg file from somewhere and the program is looking for the wrong folders? (It's impossible to tell without the list of missing directories.)  However the one that could be faulty here is actually a fixed one: namely Soundshaper's \BAT sub-folder. If that were wrong for any reason, Soundshaper couldn't read the CmdData file and therefore the parameter pages would show junk instead of proper labels or ranges, exactly as you report.

Quote from: Robert Fraser on May 04, 2024, 05:49:28 PM
"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.

Dear Robert! I'm actually very happy too being able to port Soundshaper 6 to MacOs (ARM Based!!!) using Wineskin! I still think it's non optimal compared to a native Mac version because, given the concept and structure of wineskin bottle I still can't figure out how to connect a browser or pdf reader to open help directly from Soundshaper.
Anyway here the build I did on my ARM M2 Mac : (In another machine I have builds for Mac Intel, if you need I can send)

https://ln5.sync.com/dl/696565420/c7k9sk2b-94x6e6v6-iimcqf3z-9dgh85xg

I'm using this version of Wineskin:

https://github.com/Gcenx/WineskinServer
that I install via Homebrew

Let me know If I can give further assistance,
Alessandro

When you mentioned the "SETUP PROBLEM" message, it's a pity you didn't list the apparently missing folders. The message means that the value (folder-name) assigned to each of these listed folders is invalid - the folder does not exist.  Several of them are read in from the textfile Soundshaper.cfg - I'm wondering if your student copied an old Soundshaper.cfg file from somewhere and the program is looking for the wrong folders? (It's impossible to tell without the list of missing directories.)  However the one that could be faulty here is actually a fixed one: namely Soundshaper's \BAT sub-folder. If that were wrong for any reason, Soundshaper couldn't read the CmdData file and therefore the parameter pages would show junk instead of proper labels or ranges, exactly as you report.

"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. 

Addendum:
In the bash script above, .aiff should ideally be .wav nowadays (infilepchdummy.wav) and CDP is also advocating the use of PVOCEX instead of .ana for freq. analysis files  - i.e. "infile.pvx" instead of "infile.ana".  Pvx ensures compatibility with CSOUND; .ana still works though and is used in Soundshaper, which doesn't support .pvx yet.

For the PC version, check that you have the replacement REPITCH.exe (see post under the "Announce" category).

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.