That's a reasonable division of labor, but you haven't answered my
questions about how we are going to coordinate with the sources. 

To cooperate on this project, we both need to edit the same sources. We can
either email them back and forth, or we can use Csound 5 CVS at
SourceForge. Since I would like to see vst4cs become a standard part of the
Csound 5 distribution, I prefer the latter. What about you?

Original Message:
-----------------
From:  acabrera@teleset.com.co
Date: Mon, 12 Jul 2004 12:23:30 -0500
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:4917] RE: [Csnd] vst4cs 0.1alpha


Michael,

How about you get into the editor window stuff which involves
synchronization
and other stuff that might be hard for me, and I do the bank and preset
loading?
I was thinking along the lines of:

vstbload filename
vstbsave filename
vstpload filename
vstpsave filename

sound ok?

Andres


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

Micheal,
I emailed you off-list saying it was ok with me working together in cvs, John
has already added me, so it's all set.
I'm curious, have you managed to get vst4cs working on linux?

Andres

> I emailed you off-list saying it was ok with me working together in cvs,
> John
> has already added me, so it's all set.
> I'm curious, have you managed to get vst4cs working on linux?

That would be very cool to have a linux version of the same for linux plug 
ins. At any rate, this is a fantastic development in my opinion. This will go 
a huge way to making csound attractive to new users ( and experienced ones ) 
who want to be able to keep using any commercial plugins they own and are used 
to. 

Yay guys!
Iain