> Personally, I prefer having vstplug in an indefinite-length instrument, that
> outputs constantly whatever is sent by the plugin, and the possibilty of a
> different instrument (to trigger notes with vstnote) that can be called either
> by schedkwhen, or score statements. This also ensures reverb tails or long note
> decays are always there regardless of the duration of the note generating the
> sound. It also facilitates polyphony.

I was thinking of suggesting that because that is exactly how I have my 
monosynths implemented. There are three csound instruments per 
monosynth, a sound generator that is always on, a control instrument 
that gets turned on and off by the score and sends flags to the sound 
generator, and a patch instrument that is used to tweak the patch on the 
fly ( it works with tables that the sound generator reads from ). Once 
you get over the additional extra coding and having to keep track of 
flags it works really well. I'm sure a similar approach could be adopted 
for csound vstplugs, and once we know what the status is for linux ( 
I've never used a vst plug in linux ) I'd be happy to try it out and 
post the code if it works well.

Great work guys! If we get OSC going with vst plugs Csound is going to 
start seeing a lot more users. = )

Iain

Personally, I prefer having vstplug in an indefinite-length instrument, that
outputs constantly whatever is sent by the plugin, and the possibilty of a
different instrument (to trigger notes with vstnote) that can be called either
by schedkwhen, or score statements. This also ensures reverb tails or long note
decays are always there regardless of the duration of the note generating the
sound. It also facilitates polyphony.

Andres

Maybe having both possibilities would be nice, and so use a separate opcode,
maybe vstout2 for use in a separate instrument from vstnote, and vst out for the
current use. Do you think there would be conflicts? If there are, how about
vstnote2/vstout2?
Or maybe that's complicating something that should be simple?

Andres

No worries - Csound isn't anywhere near complicated enough yet!
  :-)

Richard Dobson


acabrera@teleset.com.co wrote:
> Maybe having both possibilities would be nice, and so use a separate opcode,
> maybe vstout2 for use in a separate instrument from vstnote, and vst out for the
> current use. Do you think there would be conflicts? If there are, how about
> vstnote2/vstout2?
> Or maybe that's complicating something that should be simple?
> 
> Andres
> 
> 
>