I do plan to have a new version of CsoundVST based on csound5. But this
will require more thought. I would like to see the csound5 sources very
cleaned up in comparison with 4.23. The API itself probably requires more
work, and more input from other users and potential users.

The cross-platform nature of Csound makes all these changes take a lot more
time than they otherwise would. I don't have the resources to test my
contributions on every platform, so I have to be careful and depend on
other people to check things out on the Mac, etc.


Original Message:
-----------------
From: steven steven@kunstmusik.com
Date: 13 Aug 2003 00:24:15 -0400
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:3061] Re: CsoundVST


Hi Michael,

I just checked it out, but am on Linux so won't be able to try out until
later.  Just curious though: are you planning to put these changes into
the Csound5 source tree as well?  

Lookin' forward to checkin' it out!
steven


On Tue, 2003-08-12 at 22:42, Michael Gogins wrote:
> I have committed to the Csound CVS tree on SourceForge a number of Dev-C++
> projects for Windows.
> 
> csound/Csound.dev builds the Csound API as a static mingw library.
> 
> csound/CsoundConsole.dev builds CsoundConsole, a console version of Csound
> that should be identical in version to the canonical build, implemented by
> linking with the Csound API.
> 
> csound/CsoundVST/CsoundVST.dev builds CsoundVST using the Csound API
> library.
> 
> csound/CsoundVSTWin/CsoundVSTWin.dev builds CsoundVSTWin, a standalone
> version of CsoundVST.
> 
> csound/pyrun/PyRun.dev builds a mingw version of the Python runtime shared
> library, which is required by CsoundVST.
> 
> Functionally, CsoundVST and CsoundVSTWin are identical. Both are based on
> the Csound API, and both incorporate Python scripting for the operation of
> Csound, for algorithmic composition, and so on. There is not as yet any
> Python opcode in the orchestra.
> 
> The CsoundVST code includes two C++ classes, CppSound which provides a C++
> wrapper for the Csound API, and CsoundFile, which reads, stores, and
writes
> Csound orc, sco, csd, and MIDI files. The Python interface is generated by
> running SWIG on CppSound.hpp and CsoundFile.hpp. CsoundVST instantiates an
> instance of CppSound in Python, and retrieves the instance pointer to
> interface with VST. CsoundVSTWin simply instantiates an instance of
> CsoundVST and runs it in a top-level window.
> 
> Prerequisites and build procedures are outlined in CsoundVST/index. Note
> that the VST SDK must be separately downloaded by you from Steinberg at
the
> site specified in the CsoundVST/index.htm file.
> 
> In addition to this new code, I have committed some minor changes to the
> Csound sources proper that I found necessary to get CsoundVST working. I
do
> not believe these changes will change the behavior of Csound or cause
> problems for the canonical build. If problems do arise, please let me know
> immediately so that we can arrive at a mutually satisfactory solution.
> 
> ===========================================
> Michael Gogins
> gogins at pipeline period com
> Irreducible Productions
> Silence, a language for programming music and sound
> Available at http://www.csounds.com
> ===========================================


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