That is fantastic. Hey Michael, I was thinking about your PD/OSC opcode 
idea. It occured to me that it would be really really cool if there was 
some way one could use a csoundapi external in PD to control csound. 
Being able to make a gui with midi control in PD and having it actually 
send csoundAPI events/calls as it's interface to csound would be such a 
great way to make quick controllers for csound. It would allow easy 
prototyping for layouts and designs that one might implement later in 
wxPython or fltk. This would be especially cool if it still allowed one 
to set the csound priority level higher than the PD controller. Just a 
thought!

Iain
( Just got vnc working so I can play with Boa and fltk from work, woo hoo! )

> Great Michael! You beat me to it! Now vstplugg is working just how I 
> like it! You really took vst4cs to a place I could never have taken it 
> by myself in this decade....
> 
> Michael Gogins wrote:
> 
>> This is to announce the availability of a new file release (zip file) of
>> Csound 5 and CsoundVST, built with mingw for Windows, at
>>
>> http://sourceforge.net/projects/csound
>>
>> In addition to a number of bug fixes, this release contains Andres 
>> Cabrera's
>> vst4cs opcodes, with some additional work by me. These opcodes enable the
>> use of VST plugin effects and synthesizers within Csound on Windows. The
>> opcodes include:
>>
>> vstinit -- Loads a plugin
>> vstplug, vstplugg -- Returns a plugin's output
>> vstout -- Sends MIDI data to a plugin
>> vstpsend and vstpret -- Send automation data to and from the plugin
>> vstnote -- Sends a MIDI note with definite duration
>> vstinfo -- Outputs the Parameter and Program names for a plugin
>> vstbload-- Loads an .fxb Bank
>> vstedit -- Opens the GUI editor for the plugin, when available
>>
>> vstplug handles audio from within an instrument that also contains the
>> vstnote or vstout opcode, and vstplugg (vstplug global) handles audio 
>> from
>> any number of instruments that contain the vstnote or vstout opcode 
>> without
>> any vstplug opcode. The former is used to simplify coding, and the 
>> latter is
>> used if the plugin generates audio that persists beyond the duration 
>> of the
>> notes, e.g. reverb tails.
>>
>>
>>  
>>
> 
> 

This is to announce the availability of a new file release (zip file) of
Csound 5 and CsoundVST, built with mingw for Windows, at

http://sourceforge.net/projects/csound

In addition to a number of bug fixes, this release contains Andres Cabrera's
vst4cs opcodes, with some additional work by me. These opcodes enable the
use of VST plugin effects and synthesizers within Csound on Windows. The
opcodes include:

vstinit -- Loads a plugin
vstplug, vstplugg -- Returns a plugin's output
vstout -- Sends MIDI data to a plugin
vstpsend and vstpret -- Send automation data to and from the plugin
vstnote -- Sends a MIDI note with definite duration
vstinfo -- Outputs the Parameter and Program names for a plugin
vstbload-- Loads an .fxb Bank
vstedit -- Opens the GUI editor for the plugin, when available

vstplug handles audio from within an instrument that also contains the
vstnote or vstout opcode, and vstplugg (vstplug global) handles audio from
any number of instruments that contain the vstnote or vstout opcode without
any vstplug opcode. The former is used to simplify coding, and the latter is
used if the plugin generates audio that persists beyond the duration of the
notes, e.g. reverb tails.

Hi,

Having a look at Portaudio+ASIO+mingw, I noticed all tests were working 
except the ones that use blocking mode. I got the following reply from 
Ross Bencina:

Ross Bencina wrote:

As far as I know, the blocking read/write calls are as yet unimplemented for
the ASIO host api, so I'll assume that you're not trying to use ASIO for
these tests.

So, since this is neither working for ASIO on Windows or for Core Audio 
OS X, would it be a good idea to switch to callback instead of blocking? 
Just an idea...

Great Michael! You beat me to it! Now vstplugg is working just how I 
like it! You really took vst4cs to a place I could never have taken it 
by myself in this decade....

Michael Gogins wrote:

>This is to announce the availability of a new file release (zip file) of
>Csound 5 and CsoundVST, built with mingw for Windows, at
>
>http://sourceforge.net/projects/csound
>
>In addition to a number of bug fixes, this release contains Andres Cabrera's
>vst4cs opcodes, with some additional work by me. These opcodes enable the
>use of VST plugin effects and synthesizers within Csound on Windows. The
>opcodes include:
>
>vstinit -- Loads a plugin
>vstplug, vstplugg -- Returns a plugin's output
>vstout -- Sends MIDI data to a plugin
>vstpsend and vstpret -- Send automation data to and from the plugin
>vstnote -- Sends a MIDI note with definite duration
>vstinfo -- Outputs the Parameter and Program names for a plugin
>vstbload-- Loads an .fxb Bank
>vstedit -- Opens the GUI editor for the plugin, when available
>
>vstplug handles audio from within an instrument that also contains the
>vstnote or vstout opcode, and vstplugg (vstplug global) handles audio from
>any number of instruments that contain the vstnote or vstout opcode without
>any vstplug opcode. The former is used to simplify coding, and the latter is
>used if the plugin generates audio that persists beyond the duration of the
>notes, e.g. reverb tails.
>
>
>  
>

this is how the csound~ object for max/msp works.  supposedly the pd
csound~ object is emulating it but not loading csound library, just
communicating via pipes.

dont know how similar max and pd api is, but if you are interested,
the source code for the csound~ max external is here:

http://csounds.com/matt/csound~/csound~src.sit

-m




On Mon, 19 Jul 2004, iain duncan wrote:

>
> That is fantastic. Hey Michael, I was thinking about your PD/OSC opcode
> idea. It occured to me that it would be really really cool if there was
> some way one could use a csoundapi external in PD to control csound.
> Being able to make a gui with midi control in PD and having it actually
> send csoundAPI events/calls as it's interface to csound would be such a
> great way to make quick controllers for csound. It would allow easy
> prototyping for layouts and designs that one might implement later in
> wxPython or fltk. This would be especially cool if it still allowed one
> to set the csound priority level higher than the PD controller. Just a
> thought!
>
> Iain
> ( Just got vnc working so I can play with Boa and fltk from work, woo hoo! )
>
> > Great Michael! You beat me to it! Now vstplugg is working just how I
> > like it! You really took vst4cs to a place I could never have taken it
> > by myself in this decade....
> >
> > Michael Gogins wrote:
> >
> >> This is to announce the availability of a new file release (zip file) of
> >> Csound 5 and CsoundVST, built with mingw for Windows, at
> >>
> >> http://sourceforge.net/projects/csound
> >>
> >> In addition to a number of bug fixes, this release contains Andres
> >> Cabrera's
> >> vst4cs opcodes, with some additional work by me. These opcodes enable the
> >> use of VST plugin effects and synthesizers within Csound on Windows. The
> >> opcodes include:
> >>
> >> vstinit -- Loads a plugin
> >> vstplug, vstplugg -- Returns a plugin's output
> >> vstout -- Sends MIDI data to a plugin
> >> vstpsend and vstpret -- Send automation data to and from the plugin
> >> vstnote -- Sends a MIDI note with definite duration
> >> vstinfo -- Outputs the Parameter and Program names for a plugin
> >> vstbload-- Loads an .fxb Bank
> >> vstedit -- Opens the GUI editor for the plugin, when available
> >>
> >> vstplug handles audio from within an instrument that also contains the
> >> vstnote or vstout opcode, and vstplugg (vstplug global) handles audio
> >> from
> >> any number of instruments that contain the vstnote or vstout opcode
> >> without
> >> any vstplug opcode. The former is used to simplify coding, and the
> >> latter is
> >> used if the plugin generates audio that persists beyond the duration
> >> of the
> >> notes, e.g. reverb tails.
> >>
> >>
> >>
> >>
> >
> >
>
>