Yes to both. loris.h is for the Loris opcodes, not loris as such, which I
have customized for Csound 5 (the original source is for 4.23). 

We need the Python stuff if we want to actually use Loris, since the Csound
opcodes are only for resynthesis, not for analysis. The Python stuff
provides a quite usable interface to the analysis features of Loris.

Original Message:
-----------------
From: steven yi stevenyi@csounds.com
Date: Thu, 23 Sep 2004 01:00:53 -0700
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:5349] Loris Opcodes


Hi Michael and All,

Any reason why the SConstruct file is searching for:

configure.CheckHeader("Opcodes/Loris/src/loris.h")

and not:

configure.CheckHeader("loris.h")

?  And any reason why we need to require that the Loris opcode also be a 
python module?  I'd like to alter the SConstruct file and the loris 
opcode to remove any dependence on python so that it can be compiled 
just as a standalone Opcode library to csound so I can have it usable 
here on Linux.

steven


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .

Hi Michael,

gogins@pipeline.com wrote:

>Yes to both. loris.h is for the Loris opcodes, not loris as such, which I
>have customized for Csound 5 (the original source is for 4.23). 
>  
>

I have no Opcodes/Loris/src folder so I'm assuming you have it set up 
such that you need to copy the whole Loris src folder into the 
Opcodes/Loris directory, yes?   I've built the loris opcodes before for 
4.23 and at that time I simply linked with the compiled library and it 
had worked fine for me then.  I guess I don't understand what you're 
saying here.

>We need the Python stuff if we want to actually use Loris, since the Csound
>opcodes are only for resynthesis, not for analysis. The Python stuff
>provides a quite usable interface to the analysis features of Loris.
>  
>
Loris (1.2.0 at least) comes with a stand-alone executable, 
loris_analyze.  It gets built in the loris/utils directory.  Any reason 
we can't assume the end user has access to that?  If loris is to be used 
in the same way as the other analysis/resynthesis tools in csound, it 
makes sense to me to use the commandline tool rather than to require to 
write a python script. 

steven