Hi All,

I hadn't seen it announced, but CDP 7 is now available:

http://www.composersdesktop.com/cdpsystem.html

Source released under LGPL. Very exciting!

steven

Ditto. At the moment the sources are only set up for Windows (MinGW) and 
OS X; I have barely started work on Linux, which we have not hitherto 
supported; and as my small Linux laptop is 64bit, which we have also 
hitherto not had to deal with, it is not quite a case of typing "make" 
and waiting. Also, only when I have got that working and more or less 
tested (150 programs now!) will I ponder which "proper" build system to 
use for it all.

There is a user forum set up for it now, hosted by Simon Kunath:

http://unstablesound.net/cdpforum/

Richard Dobson




On 21/02/2014 17:12, jpff@cs.bath.ac.uk wrote:
> I ought to declare an interest, as a Director of CDP Ltd. - a Social
> Enterprise
>
> Tutorial material is available on dream.cs.bath.ac.uk/CDP and the CDP
> website www.composersdesktop.com/?
>
> ==John ff
>
> Quoting Steven Yi :
>
>> Hi All,
>>
>> I hadn't seen it announced, but CDP 7 is now available:
>>
>> http://www.composersdesktop.com/cdpsystem.html
>>
>> Source released under LGPL. Very exciting!
>>
>> steven
>
>
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>             https://sourceforge.net/p/csound/tickets/
> csound5:
>             https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>
>

This is very nice, thank you very much. A quick question: any reason why the Makefiles build for i386 and not x86_64?
On 21 Feb 2014, at 17:28, Richard Dobson  wrote:

> Ditto. At the moment the sources are only set up for Windows (MinGW) and OS X; I have barely started work on Linux, which we have not hitherto supported; and as my small Linux laptop is 64bit, which we have also hitherto not had to deal with, it is not quite a case of typing "make" and waiting. Also, only when I have got that working and more or less tested (150 programs now!) will I ponder which "proper" build system to use for it all.
> 
> There is a user forum set up for it now, hosted by Simon Kunath:
> 
> http://unstablesound.net/cdpforum/
> 
> Richard Dobson
> 
> 
> 
> 
> On 21/02/2014 17:12, jpff@cs.bath.ac.uk wrote:
>> I ought to declare an interest, as a Director of CDP Ltd. - a Social
>> Enterprise
>> 
>> Tutorial material is available on dream.cs.bath.ac.uk/CDP and the CDP
>> website www.composersdesktop.com/?
>> 
>> ==John ff
>> 
>> Quoting Steven Yi :
>> 
>>> Hi All,
>>> 
>>> I hadn't seen it announced, but CDP 7 is now available:
>>> 
>>> http://www.composersdesktop.com/cdpsystem.html
>>> 
>>> Source released under LGPL. Very exciting!
>>> 
>>> steven
>> 
>> 
>> 
>> 
>> Send bugs reports to the Sourceforge bug trackers
>> csound6:
>>            https://sourceforge.net/p/csound/tickets/
>> csound5:
>>            https://sourceforge.net/p/csound/bugs/
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>> 
>> 
>> 
> 
> 
> 
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>           https://sourceforge.net/p/csound/tickets/
> csound5:
>           https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 
> 

Hi John,

I tried to go to:

http://dream.cs.bath.ac.uk/CDP/

but got a 403 Access Forbidden message.  I tried some other links from
the dream home page but also got some errors.

Thanks!
steven

On Fri, Feb 21, 2014 at 12:12 PM,   wrote:
> I ought to declare an interest, as a Director of CDP Ltd. - a Social
> Enterprise
>
> Tutorial material is available on dream.cs.bath.ac.uk/CDP and the CDP
> website www.composersdesktop.com/?
>
> ==John ff
>
> Quoting Steven Yi :
>
>> Hi All,
>>
>> I hadn't seen it announced, but CDP 7 is now available:
>>
>> http://www.composersdesktop.com/cdpsystem.html
>>
>> Source released under LGPL. Very exciting!
>>
>> steven
>
>
>

This is all very exciting. :)  I've thought for a while it would be
nice to create some CDP kind of SoundObjects in Blue. Having the
source available is a big deal to me, and it's great that there's a
large amount of documentation.
For build systems, my vote is for CMake myself. :)

Congratulations on the release and thanks all who are involved with CDP!
steven

On Fri, Feb 21, 2014 at 12:28 PM, Richard Dobson
 wrote:
> Ditto. At the moment the sources are only set up for Windows (MinGW) and OS
> X; I have barely started work on Linux, which we have not hitherto
> supported; and as my small Linux laptop is 64bit, which we have also
> hitherto not had to deal with, it is not quite a case of typing "make" and
> waiting. Also, only when I have got that working and more or less tested
> (150 programs now!) will I ponder which "proper" build system to use for it
> all.
>
> There is a user forum set up for it now, hosted by Simon Kunath:
>
> http://unstablesound.net/cdpforum/
>
> Richard Dobson
>
>
>
>
>
> On 21/02/2014 17:12, jpff@cs.bath.ac.uk wrote:
>>
>> I ought to declare an interest, as a Director of CDP Ltd. - a Social
>> Enterprise
>>
>> Tutorial material is available on dream.cs.bath.ac.uk/CDP and the CDP
>> website www.composersdesktop.com/?
>>
>> ==John ff
>>
>> Quoting Steven Yi :
>>
>>> Hi All,
>>>
>>> I hadn't seen it announced, but CDP 7 is now available:
>>>
>>> http://www.composersdesktop.com/cdpsystem.html
>>>
>>> Source released under LGPL. Very exciting!
>>>
>>> steven
>>
>>
>>
>>
>>
>> Send bugs reports to the Sourceforge bug trackers
>> csound6:
>>             https://sourceforge.net/p/csound/tickets/
>> csound5:
>>             https://sourceforge.net/p/csound/bugs/
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>>
>
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>            https://sourceforge.net/p/csound/tickets/
> csound5:
>            https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>

Very simple - we/I have not had the kit to build and test on a 64bit
architecture (except now I have the loan of a MacBook so I can start to
do just that; starting also on building for Linux 64bit, and already
finding that some things are wrong, mainly in sfsys, much of the code of
which is legacy from the Atari days), so the only safe thing at present
is to specify i386 only. So consider that "work in progress". Once I can 
be sure I have sfsys working OK in 64bit, the rest ~should~ fall into 
place fairly quickly.

Richard Dobson




On 21/02/2014 20:47, Victor Lazzarini wrote:
> This is very nice, thank you very much. A quick question: any reason
> why the Makefiles build for i386 and not x86_64? On 21 Feb 2014, at
> 17:28, Richard Dobson  wrote:
>
>> Ditto. At the moment the sources are only set up for Windows
>> (MinGW) and OS X; I have barely started work on Linux, which we
>> have not hitherto supported; and as my small Linux laptop is 64bit,
>> which we have also hitherto not had to deal with, it is not quite a
>> case of typing "make" and waiting. Also, only when I have got that
>> working and more or less tested (150 programs now!) will I ponder
>> which "proper" build system to use for it all.
>>
>> There is a user forum set up for it now, hosted by Simon Kunath:
>>
>> http://unstablesound.net/cdpforum/
>>
>> Richard Dobson

\\the files are there linked from CDP home.  Just no index file
==John ff

On 02/21/2014 11:22 AM, Steven Yi wrote:
> Hi All,
>
> I hadn't seen it announced, but CDP 7 is now available:
>
> http://www.composersdesktop.com/cdpsystem.html
>
> Source released under LGPL. Very exciting!
>

I've started to muck around with its makefiles to see what I'd need to 
do in order to compile it for Linux. So far the term "non-trivial" comes 
to mind. :)

Currently I'm looking at the Windows mingw makefile and attempting to 
build libsfsys (fpos_t is giving me fits). Any advice would be 
appreciated, and if there's already a Linux CDP project underway I'll be 
happy to stop my efforts and help out with the other or wait until a set 
of makefiles appears.

At any rate, major thanks to the CDP team !

Best,

dp

I would think the OSX makefiles would be closer to what you need.

Victor
On 24 Feb 2014, at 11:37, Dave Phillips  wrote:

> 
> On 02/21/2014 11:22 AM, Steven Yi wrote:
>> Hi All,
>> 
>> I hadn't seen it announced, but CDP 7 is now available:
>> 
>> http://www.composersdesktop.com/cdpsystem.html
>> 
>> Source released under LGPL. Very exciting!
>> 
> 
> I've started to muck around with its makefiles to see what I'd need to do in order to compile it for Linux. So far the term "non-trivial" comes to mind. :)
> 
> Currently I'm looking at the Windows mingw makefile and attempting to build libsfsys (fpos_t is giving me fits). Any advice would be appreciated, and if there's already a Linux CDP project underway I'll be happy to stop my efforts and help out with the other or wait until a set of makefiles appears.
> 
> At any rate, major thanks to the CDP team !
> 
> Best,
> 
> dp
> 
> 
> 
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>           https://sourceforge.net/p/csound/tickets/
> csound5:
>           https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 
> 

On 02/24/2014 06:58 AM, Victor Lazzarini wrote:
> I would think the OSX makefiles would be closer to what you need.
>
> Victor

Doh. Of course. I'll look at them this morning.

Best,

dp






> On 24 Feb 2014, at 11:37, Dave Phillips  wrote:
>
>> On 02/21/2014 11:22 AM, Steven Yi wrote:
>>> Hi All,
>>>
>>> I hadn't seen it announced, but CDP 7 is now available:
>>>
>>> http://www.composersdesktop.com/cdpsystem.html
>>>
>>> Source released under LGPL. Very exciting!
>>>
>> I've started to muck around with its makefiles to see what I'd need to do in order to compile it for Linux. So far the term "non-trivial" comes to mind. :)
>>
>> Currently I'm looking at the Windows mingw makefile and attempting to build libsfsys (fpos_t is giving me fits). Any advice would be appreciated, and if there's already a Linux CDP project underway I'll be happy to stop my efforts and help out with the other or wait until a set of makefiles appears.
>>
>> At any rate, major thanks to the CDP team !
>>
>> Best,
>>
>> dp
>>
>>
>>
>> Send bugs reports to the Sourceforge bug trackers
>> csound6:
>>            https://sourceforge.net/p/csound/tickets/
>> csound5:
>>            https://sourceforge.net/p/csound/bugs/
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>>
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>              https://sourceforge.net/p/csound/tickets/
> csound5:
>              https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
>

Yes it is - but I am working on it and making good progress. I would 
suggest just waiting a while, if you can. sfsys especially is even more 
than usually opaque, so I would not recommend someone new to it making 
changes**. So much of the code is "legacy", much dating back to the 
Atari days, with lots of casual use of "long" which needs to be "int" on 
64bit platforms - which has been the sticking point, not having a 64bit 
Win or Mac platform to build and test on.

So yes, the plan is (in the first instance) to crate a new set of 
makefiles, with code fixes where required. e.g. the fpos_t stuff in 
sfsys (to handle up to 4GB soundfiles) is/was incomplete, in the sense 
being of work-in-progress (no-op under 32bit Win and Mac), but as of 
yesterday I had it all built and working under initial tests (including 
sfsys therefore). Needless to say an automated search and replace for 
'long' will not quite do it, so this will take a little while, but I am 
working on it right now.  Only when it can build and run on all the 
architectures people expect these days (incl 64bit Windows, which 
neither of my oldish machines can be upgraded to), will it be time to 
crate a "proper" make system using CMake or whichever. And so on.

So, "watch this space" etc.

It may take that much longer again to get Soundloom running on Linux 
(partly because it was not designed for small screens like my laptop!), 
not least as I am low on the tcltk learning curve; but possibly the 
proto-typical Linux user will eschew such things anyway and stick to the 
good old command line?


** to answer the obvious question - we need our own custom soundfile 
library (rather than just using libsndfile) as we have a large number of 
"custom" CDP file types for analysis data; and one of the jobs on my 
deep TODO list is creating some new file formats for it all. Believe it 
or not, CDP sfsys (etc) does not (yet) even support PVOCEX!

Richard Dobson


On 24/02/2014 11:37, Dave Phillips wrote:
>
> On 02/21/2014 11:22 AM, Steven Yi wrote:
>> Hi All,
>>
>> I hadn't seen it announced, but CDP 7 is now available:
>>
>> http://www.composersdesktop.com/cdpsystem.html
>>
>> Source released under LGPL. Very exciting!
>>
>
> I've started to muck around with its makefiles to see what I'd need to
> do in order to compile it for Linux. So far the term "non-trivial" comes
> to mind. :)
>
> Currently I'm looking at the Windows mingw makefile and attempting to
> build libsfsys (fpos_t is giving me fits). Any advice would be
> appreciated, and if there's already a Linux CDP project underway I'll be
> happy to stop my efforts and help out with the other or wait until a set
> of makefiles appears.
>
> At any rate, major thanks to the CDP team !
>
> Best,
>
> dp
>
>

On 02/24/2014 07:27 AM, Richard Dobson wrote:

> Yes it is - but I am working on it and making good progress. I would 
> suggest just waiting a while, if you can. sfsys especially is even 
> more than usually opaque, so I would not recommend someone new to it 
> making changes**. So much of the code is "legacy", much dating back to 
> the Atari days, with lots of casual use of "long" which needs to be 
> "int" on 64bit platforms - which has been the sticking point, not 
> having a 64bit Win or Mac platform to build and test on.

Thanks for that update, Richard. I'll cool my jets here, but please let 
me know if I can be of any assistance. No problem waiting, I'm in no 
hurry. I have my hands full these days.


>
> So yes, the plan is (in the first instance) to crate a new set of 
> makefiles, with code fixes where required. e.g. the fpos_t stuff in 
> sfsys (to handle up to 4GB soundfiles) is/was incomplete, in the sense 
> being of work-in-progress (no-op under 32bit Win and Mac), but as of 
> yesterday I had it all built and working under initial tests 
> (including sfsys therefore). Needless to say an automated search and 
> replace for 'long' will not quite do it, so this will take a little 
> while, but I am working on it right now. Only when it can build and 
> run on all the architectures people expect these days (incl 64bit 
> Windows, which neither of my oldish machines can be upgraded to), will 
> it be time to crate a "proper" make system using CMake or whichever. 
> And so on.
>
> So, "watch this space" etc.
>

I will be watching. CDP for Linux is a very exciting prospect.

> It may take that much longer again to get Soundloom running on Linux 
> (partly because it was not designed for small screens like my 
> laptop!), not least as I am low on the tcltk learning curve; but 
> possibly the proto-typical Linux user will eschew such things anyway 
> and stick to the good old command line?
>

Well, GUIs are nice at times. I ran SoundShaper Lite under Wine the 
other day, it could certainly help organize a composition. However, for 
analysis/resynthesis and other tricky stuff the CLI is just fine for me.

Again, thank you for the update.

Best,

dp



>
> ** to answer the obvious question - we need our own custom soundfile 
> library (rather than just using libsndfile) as we have a large number 
> of "custom" CDP file types for analysis data; and one of the jobs on 
> my deep TODO list is creating some new file formats for it all. 
> Believe it or not, CDP sfsys (etc) does not (yet) even support PVOCEX!
>
> Richard Dobson
>
>
> On 24/02/2014 11:37, Dave Phillips wrote:
>>
>> On 02/21/2014 11:22 AM, Steven Yi wrote:
>>> Hi All,
>>>
>>> I hadn't seen it announced, but CDP 7 is now available:
>>>
>>> http://www.composersdesktop.com/cdpsystem.html
>>>
>>> Source released under LGPL. Very exciting!
>>>
>>
>> I've started to muck around with its makefiles to see what I'd need to
>> do in order to compile it for Linux. So far the term "non-trivial" comes
>> to mind. :)
>>
>> Currently I'm looking at the Windows mingw makefile and attempting to
>> build libsfsys (fpos_t is giving me fits). Any advice would be
>> appreciated, and if there's already a Linux CDP project underway I'll be
>> happy to stop my efforts and help out with the other or wait until a set
>> of makefiles appears.
>>
>> At any rate, major thanks to the CDP team !
>>
>> Best,
>>
>> dp
>>
>>
>
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>            https://sourceforge.net/p/csound/tickets/
> csound5:
>            https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body 
> "unsubscribe csound"
>
>
>

I found the links on the CDP site, thanks!

On Sat, Feb 22, 2014 at 3:18 PM, jpff  wrote:
> \\the files are there linked from CDP home.  Just no index file
> ==John ff
>
>
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>            https://sourceforge.net/p/csound/tickets/
> csound5:
>            https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>

So, OK, there is now a Linux source download available (see 
http://www.unstablesound.net/cdp.html)

I have marked it as beta, as while everything tested so far (Suse 13.1 
64bit) has worked, I have not yet done "exhaustive" testing of 150+ 
programs, after implementing changes for a 64bit system. NB the source 
files are not interchangeable with the main (32bit) source set.

Near the top of my todo list is to update the PVOCEX demo programs here:
http://dream.cs.bath.ac.uk/researchdev/pvocex/pvocex.html

specifically "pvocex2", which can be used to create a stereo .pvx file - 
which the latest version of "pvplay" in the CDP system can now play.

Richard Dobson


On 24/02/2014 12:35, Dave Phillips wrote:
>
..
>
> Thanks for that update, Richard. I'll cool my jets here, but please let
> me know if I can be of any assistance. No problem waiting, I'm in no
> hurry. I have my hands full these days.
>

On 03/03/2014 04:55 AM, Richard Dobson wrote:
> So, OK, there is now a Linux source download available (see 
> http://www.unstablesound.net/cdp.html)

Wonderful news ! I've built and installed libaaio, now I have a question 
about the PortAudio requirement. The docs indicate the need for a static 
build. I don't foresee any serious problem building it, but I already 
have PA 19 and its devel package installed (in /usr) and of course the 
lib is shared. Will the static lib need to be installed in the CDP tree 
or system-wide (/usr/local) ? Not a major issue, I just want to avoid 
clashing libs.

>
> I have marked it as beta, as while everything tested so far (Suse 13.1 
> 64bit) has worked, I have not yet done "exhaustive" testing of 150+ 
> programs, after implementing changes for a 64bit system. NB the source 
> files are not interchangeable with the main (32bit) source set.
>

I'll build and test on Fedora 19 x86_64.

Thanks for the update, Richard. Very exciting ! :)

Best,

dp

On 03/03/2014 06:44 AM, Dave Phillips wrote:
>
> On 03/03/2014 04:55 AM, Richard Dobson wrote:
>> So, OK, there is now a Linux source download available (see 
>> http://www.unstablesound.net/cdp.html)
>
> Wonderful news ! I've built and installed libaaio, now I have a 
> question about the PortAudio requirement. The docs indicate the need 
> for a static build. I don't foresee any serious problem building it, 
> but I already have PA 19 and its devel package installed (in /usr) and 
> of course the lib is shared. Will the static lib need to be installed 
> in the CDP tree or system-wide (/usr/local) ? Not a major issue, I 
> just want to avoid clashing libs.
>

Never mind, I simply put the static libs in /usr/lib64 and changed the 
search line in makefile.sh. The programs are compiling as I write. :)

Best,

dp

On 03/03/2014 11:44, Dave Phillips wrote:
>
> On 03/03/2014 04:55 AM, Richard Dobson wrote:
>> So, OK, there is now a Linux source download available (see
>> http://www.unstablesound.net/cdp.html)
>
> Wonderful news ! I've built and installed libaaio, now I have a question
> about the PortAudio requirement. The docs indicate the need for a static
> build. I don't foresee any serious problem building it, but I already
> have PA 19 and its devel package installed (in /usr) and of course the
> lib is shared. Will the static lib need to be installed in the CDP tree
> or system-wide (/usr/local) ? Not a major issue, I just want to avoid
> clashing libs.
>

As designed it is a local copy inside the "paprogs" directory, and the 
makefiles look for it directly in portaudio/lib/.libs. This seemed the 
least impactful option. Clashing libs seems to be a real hazard, 
especially with portaudio (I managed to break a Linux installation of 
Audacity by casually doing "make install" on portaudio). As a static lib 
portaudio really adds very little to the size of an executable. With use 
of a non-standard shared library, things need to be "installed"; whereas 
with static linking things can simply be copied to anywhere; more 
convenient for command line programs.

Portaudio is still in a fairly constant state of development, and as it 
happens there are still things not quite right wrt Windows, with either 
configure.in or the generated Makefile needing manual tweaking for Mingw 
(and indeed ditto for OS X to set the architecture(s) etc). I supposed I 
should not be surprised that the linux build was the most trouble-free 
(except when driving the cheap onboard audio on my laptop!).

Richard Dobson

On 03/03/2014 07:18 AM, Dave Phillips wrote:
>
> On 03/03/2014 06:44 AM, Dave Phillips wrote:
>>
>> On 03/03/2014 04:55 AM, Richard Dobson wrote:
>>> So, OK, there is now a Linux source download available (see 
>>> http://www.unstablesound.net/cdp.html)
>>
>> Wonderful news ! I've built and installed libaaio, now I have a 
>> question about the PortAudio requirement. The docs indicate the need 
>> for a static build. I don't foresee any serious problem building it, 
>> but I already have PA 19 and its devel package installed (in /usr) 
>> and of course the lib is shared. Will the static lib need to be 
>> installed in the CDP tree or system-wide (/usr/local) ? Not a major 
>> issue, I just want to avoid clashing libs.
>>
>
> Never mind, I simply put the static libs in /usr/lib64 and changed the 
> search line in makefile.sh. The programs are compiling as I write. :)

Also discovered where the build expects to find the static lib, so I put 
the makefile back in its original condition. Again no problems with the 
build. No tests run yet, will do so today.

Best,

d

I have some problems with building.

/home/Hlolli/Downloads/CDPrelease7src/dev/externals/paprogs/paplay
gcc -O3  -Dlinux -Dunix -I../../include -I../portaudio/include -I../portaudio/src/common -L../../lib  -L../portaudio/lib/.libs -L../../lib -c paplay.c
paplay.c:60:18: fatal error: aaio.h: No such file or directory
 #include <aaio.h>

I build libaaio and moved it to /usr/local/lib/libaaio-0.3.1 Someting I'm forgetting?

I'm btw using fedora 20.

2014-03-03 14:12 GMT+00:00 Dave Phillips <dlphillips@woh.rr.com>:

On 03/03/2014 07:18 AM, Dave Phillips wrote:

On 03/03/2014 06:44 AM, Dave Phillips wrote:

On 03/03/2014 04:55 AM, Richard Dobson wrote:

So, OK, there is now a Linux source download available (see http://www.unstablesound.net/cdp.html)

Wonderful news ! I've built and installed libaaio, now I have a question about the PortAudio requirement. The docs indicate the need for a static build. I don't foresee any serious problem building it, but I already have PA 19 and its devel package installed (in /usr) and of course the lib is shared. Will the static lib need to be installed in the CDP tree or system-wide (/usr/local) ? Not a major issue, I just want to avoid clashing libs.

Never mind, I simply put the static libs in /usr/lib64 and changed the search line in makefile.sh. The programs are compiling as I write. :)

Also discovered where the build expects to find the static lib, so I put the makefile back in its original condition. Again no problems with the build. No tests run yet, will do so today.

Best,

d



Send bugs reports to the Sourceforge bug trackers
csound6:
           https://sourceforge.net/p/csound/tickets/
csound5:
           https://sourceforge.net/p/csound/bugs/
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

--
Hlöðver Sigurðsson

On 04/03/2014 17:19, Peter P. wrote:
..
>
> Hi Richard, and thanks for the big efforts porting cdp, dear list,
>
> just tried to run
>
>          ./pvoc anal 1 /tmp/some_mono_44k1_infile.wav
> /tmp/outfile.ana
>
> on Linux (Debian testing) and got it crashing throwing the error
> pasted below
>
> Is anyone else able to run pvoc?
>


I can't switch my laptop to Linux right now to check, but the first 
question is: do you have the environment variable CDP_SOUND_EXT (= wav) 
defined? It is needed for .ana analysis files (I have yet to add pvx 
support to the CDP system). Not having a linux installer as such, such 
things have to be done manually at the moment. The initial error message 
is consistent with that situation; and it is quite possible that under 
the scrutiny of debian testing, any resulting memory problem will 
trigger such a list of messages.


Feel free to email me offlist, I would not want to presume such things 
are particularly on topic for Csound!


Richard Dobson

On 04/03/2014 17:40, Hlöðver Sigurðsson wrote:
> Ok I did, make install wrong with aaio. Now everything went successful.
>
> I'm just exploring this program out of curiosity. Looks like I have to
> compile each program?
>
> "See the general CDP installation notes regarding manual setup for cdpr7"
>
>

That's the general idea. The essentials for most programs are the 
libraries "sfsys" and "cdp2k" (which the top level build script will do 
first anyway, or you can build each one manually); thereafter you can 
either run the whole script to build everything (doesn't take that long, 
really), or just pick out individual programs you are interested in (in 
which case, you can ignore the programs in "misc" as they are solely for 
use by Soundloom).

It is of course not a proper  build system such as might be based on 
CMake etc; I am sort of hoping the community will help decide which of 
the various such solutions to use, etc. I haven't got much beyond page 
one of "CMake for Dummies" yet.

Richard Dobson

On 04/03/2014 21:12, Hlöðver Sigurðsson wrote:
> One more basic question, and sorry if it sounds like I'm asking if the
> sky is blue, but are these audio tools to be used without GUI?
>

Yes, they are all command line programs. Use whatever shell your system 
supports (e.g Konsole). Don't double-click on any of the programs. If 
you type the program name by itself, it will print a usage message. This 
is where the documentation comes in (main docs are html, plus other 
stuff). Don't forget to add the path to the directory containing the 
programs to your system PATH, so you can access them from anywhere.

(that is, unless you decide to copy them all to /usr/local/bin!)

Richard Dobson

Also, I hit some problems porting Soundloom to Linux, so sadly there is 
no reliable GUI available for linux yet. Soundloom sort of works, a lot 
of the time, but depending on what you do, various tcltk window errors 
are popping up, so I haven't released it yet. It's one of the many areas 
of programming I am deeply inexpert in...

Richard Dobson

On 04/03/2014 21:12, Hlöðver Sigurðsson wrote:
..
>
> In the MacOs tutorial it shows GUI for filters, maybe not the same here
> for Linux?
>

On 04/03/2014 21:49, peiman khosravi wrote:
> soundloom doesn't seem to be working on mavericks either.
>
>

That's different - it should be! I have it running OK here. Presumably 
you have turned off the sandbox protection so it will be allowed to run? 
Might be better not to clog up this list with such things, do contact me 
offlist with details etc.

Richard Dobson

It may not be activated. You can check if the environment variable is 
installed and active by typing env in the shell: CDP_SOUND_EXT should be 
in the list somewhere. A usual procedure is to add the command to one or 
other of your profiles, e.g. ~/.bash_profile. You will probably need to 
log out an in again to activate it.

Richard Dobson



On 04/03/2014 22:14, Peter P. wrote:
>..
>
> Thank you! With CDP_SOUND_EXT=wav set,
>          ./pvoc anal 1 /tmp/somefile.wav /tmp/somefile.ana
> throws the same error included below for reference.
>
> All the best, Peter
>
> --------------------8<-----------------------------
>
> ERROR: INVALID DATA
> ERROR: Cannot open output file /tmp/somefile.ana
>
>

On 04/03/2014 23:02, Peter P. wrote:
..
> Thank you. I think it is activated:
>
> user@machine:~/CDPrelease7src/dev/Release$ set | grep CDP_SOUND_EXT
> CDP_SOUND_EXT=wav
>
> So bash reports this variable being set. Or did I misspell it? Or do I
> make another mistake? Thank you for your effort Richard,
>

Ok; if there is not already a file called somefile.ana (CDP programs are 
non-destructive), and there is not some unexpected permissions problem, 
then I am stumped. I have it working here on Suse 13.1, and have not 
witnessed this problem in any other circumstance than the missing 
environment variable. The only workaround I can suggest is to give the 
output file a .wav extension (since the .ana format actually uses the 
WAVE file format with a custom header chunk) and see if that solves the 
problem (if it runs, you can change the extension to .ana afterwards).

Richard Dobson

On 06/03/2014 02:07, Peter P. wrote:
> Dear Richard,
>
..
> Yes indeed! "./pvoc anal" and also other programs working with .ana files
> crash when they are launced with somefile.ana outfile names.
>
> The workaround you propose works. The file is written, and can be
> renamed from somefile.wav to somefile.ana
> I could even sstick to the .wav extension and have other programs use
> these files as valid input to transformations in the spectral domain.
>
> I am wondering if anyone else has or has no such problem on Linux.
>


This can only mean that somehow CDP_SOUND_EXT is not being found. Could 
you double-check this when you initially boot up the machine, or first 
launch a terminal session? You can install an environment variable 
within an open shell session too, just using the command line 'export 
CDP_SOUND_EXT=wav'; this will last until you close the shell, and will 
enable you to test if pvoc is actually picking it up.

Richard Dobson

On 03/04/2014 06:18 PM, Richard Dobson wrote:
> On 04/03/2014 23:02, Peter P. wrote:
> ..
>> Thank you. I think it is activated:
>>
>> user@machine:~/CDPrelease7src/dev/Release$ set | grep CDP_SOUND_EXT
>> CDP_SOUND_EXT=wav
>>
>> So bash reports this variable being set. Or did I misspell it? Or do I
>> make another mistake? Thank you for your effort Richard,
>>
>
> Ok; if there is not already a file called somefile.ana (CDP programs 
> are non-destructive), and there is not some unexpected permissions 
> problem, then I am stumped. I have it working here on Suse 13.1, and 
> have not witnessed this problem in any other circumstance than the 
> missing environment variable. The only workaround I can suggest is to 
> give the output file a .wav extension (since the .ana format actually 
> uses the WAVE file format with a custom header chunk) and see if that 
> solves the problem (if it runs, you can change the extension to .ana 
> afterwards).
>

Hi Richard, hi Peter,

I received the same error Peter got when I ran this command :

     ./pvoc anal 1 myfile.wav myfile.ana

I then followed Richard's advice for CDP_SOUND_EXT

     export CDP_SOUND_EXT=wav

And the problem was solved. This is on Fedora 19 x86_64.

Testing other parts of the system as well. Amazing tools, I'll be busy 
here for a very long time.

Any outlook on Soundshaper for Linux ? Once upon a time I knew some 
Tcl/Tk (Cecelia for Linux), don't know if I'd be of any help but would 
be happy to test.

Best,

dp