Good questions...

CsoundVST works in Cubase SX, Orion PRO, and Fruity Loops, so it probably
works in most hosts.

Hosts have no way to receive automation parameters from CsoundVST at this
time; they can of course send any MIDI to CsoundVST and the orc can do what
it wants with it.

CsoundVST does not at this time load VST plugins, although this obviously
is a desirable feature and I may do it at some point. If I did, it would be
a plugin opcode adapter that would work in any plugin-capable version of
Csound, including canonical Csound.

More than one instance: not in 4.23, will be yes (when?) in 5.0. I am
working on csound5 and when I get the API and all the opcodes working, I
will migrate CsoundVST to csound5. I'm not sure how much work to finish the
multi-instancing capability (John Fitch has already done considerable work
here).

Midi out? Used to have it, will put it back at some point.


Original Message:
-----------------
From: Josep M Comajuncosas Nebot jcomajuncosas@wanadoo.es
Date: Wed, 31 Dec 2003 11:11:36 +0100
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:3857] RE: midi in csound5


Also, at what level CsoundVST integrates with existing VST hosts?
Is it possible by the host to know the automatization parameters? No
idea how it is done, but it would be very comfortable...it should
reconfigure when one reedits the orchestra hmm...

Also, is it possible to load VST instruments and effects? More than one
Csound instance? MIDI-out plugins for algorithmic generation? (no idea
if they exist or not!).

I'm not a VST user as you may notice...

Josep M Comajuncosas     


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