PD uses  32-bit floats (its own t_float).

>From the output below, I see that the problem is that
for some reason  the csd csdapi_demo.csd cannot be
compiled; this is generally because csdapi_demo.csd
was not found.

If you start PD anywhere but in the examples/csoundapi_tilde
directory, this will happen. That is because csoundapi looks
for
the csd in the current directory.

You can try csoundapi with any csd.
For instance, if you start PD, open a new patch and
then type in an object

csoundapi~ examples/trapped.csd

(provided you are in the top-level csound5 directory) a
new object will be created, load in trapped and if you
connect it to dac~ and start PD, you'll hear Rick
Boulanger's
piece.

Victor

> input channels = 2, output channels = 2
> input channels = 2, output channels = 2
> 1 devices in, 1 devices out
> tried
> C:\\utah\\opt\\pd-0.38-4-devel-2\\bin\\csoundapi~.dll and
> failed tried c:\\utah\\opt\\csound\\csoundapi~.dll and
> succeeded
>
> csoundapi~ 1.0
>  A PD csound class using the Csound 5.00 API
> (c) V Lazzarini, 2005
>
> csapi_demo.csd
> csoundapi~ warning: could not compile
> csoundapi.pd 4 0 39 3 (adc~->csoundapi~/csoundapi~)
> connection failed csoundapi.pd 4 1 39 3
> (adc~->csoundapi~/csoundapi~) connection failed
> csoundapi.pd 39 3 0 1 (csoundapi~/csoundapi~->dac~)
> connection failed csoundapi.pd 39 4 24 0
> (csoundapi~/csoundapi~->message) connection failed
> csoundapi~ run: 1 csoundapi~ warning: not compiled
>


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net