It's not going to be easy. PD was not designed to be used this way. I am
not sure it can be done without either (a) using only OSC, or (b) writing
new externals to facilitate the job plus writing a new PD main loop for the
plugin.

Now that I think it about, I think perhaps the pdpatch opcode would run PD
in a separate thread using PD's normal sys_main function, and the pdmidi,
pdnote, pdain, and pdaout opcodes would use OSC. Rather indirect but much
simpler than trying to get more direct...

Original Message:
-----------------
From: Andres Cabrera acabrera@teleset.com.co
Date: Sun, 18 Jul 2004 11:25:36 -0500
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:5017] Re: vst4cs


Thanks Michael. Uncommenting the code is a good idea, less files to 
distribute. I'll update my cvs just in case, and try vstnote again.
PD inside Csound! Amazing if it can be done!

gogins@pipeline.com wrote:

>I have just now committed fxbank.h and .cpp -- sorry about the omission.
>The VST SDK is not required, as I uncommented the vstfxstore.h code in
>fxbank.h. vstnote is working for me, why not for you? I will look into the
>idle call.
>
>Your vst4cs project has inspired me to attempt a PD proxy opcode for
>Csound, pd4cs. It will enable PD patches to run as opcodes in Csound. I
>have only just begun working on this.
>
>  
>


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