| Example command line:
csound --opcode-lib=c:/cvs/CVSROOT/bin/Soundfonts.dll -RWdfo filename.wav
filename.orc filename.sco
Look at the Soundfonts opcode in Csound CVS to see how an opcode can be
written as a plugin.
============================================
Michael Gogins
gogins at pipeline period com
Irreducible Productions
CsoundVST, an extended version of Csound for programming music and sound
Available at http://sourceforge.net/projects/csound/
============================================
----- Original Message -----
From: "Alex Norman"
To: "Csound Developers Discussion List"
Sent: Thursday, December 18, 2003 3:27 PM
Subject: [CSOUND-DEV:3806] loading plugins
> Hello,
> I'm developing some opcodes that will allow for ATS data to be used in
> Csound. Actually most of the development is done, I've just got to
> test them more. I'm attempting to make my opcodes load as plug-ins so
> they'll be forward compatible with Csound5 but I cannot find any
> documentation and the web based search function for this list is
> very difficult to navigate.
>
> So, I looked at the OSClib and metro code to see what is done there and
> have added what I think is needed (the stuff that loads my info into
> OENTRY like at the bottom of OSC-sock.c).
> But I don't know how to Load the plug-ins (my own or the OSClib or metro)
> plug-ins.
>
> Is this something that I specify in the orc? or an argument that I
> pass to Csound? or should all plug-ins be in a specific directory?
>
> Thanks,
> Alex Norman
> University of Washington
> |