Regarding licensing:

My plan is to exclude all non free software (which means CsoundVST, vst4cs, and the STK C++ opcodes in stk.dll) from the binary installers on SourceForge. However, these components will still be possible to build from Csound CVS sources. But first, the developer will have to download the VST STK from Steinberg and the STK sources from CCRMA and copy them to the Csound tree. The Csound SConstruct file will then build these components. It will also still be possible to build a Windows installer that includes these components.

As I understand it, taking these steps will bring Csound into confirmity with SourceForge licensing policy. And it will mean that the standard binary distributions of Csound 5 can contain all the same components on all supported platforms.

Of course, I will continue to use vst4cs because I can build it myself quite easily. But I will regret no longer making vst4cs available by default, as I think it significantly extends the power of Csound by making it very easy to use such wonderful plugins as the Pianoteq.

Regarding CsoundVST:

Up until the very latest release, there was a bug in CsoundVST's GUI. As a consequence of this bug, CsoundVST worked in Cubase, the host I develop for, but it did NOT work with many other hosts. However, I have identified and fixed this bug. I have tested CsoundVST with Sonar 6. 

So, you may wish to test the very latest release of CsoundVST.

Hope this helps,
Mike

-----Original Message-----
>From: rasputin 
>Sent: Jul 27, 2007 1:03 PM
>To: csound-devel@lists.sourceforge.net
>Subject: Re: [Cs-dev] Next Release
>
>
>1 Is the next release going to exclude things like STK opcodes due to
>licensing questions?
>
>2 I've been very interested in the idea of using CsoundVST as a plug in, but
>I haven't had much luck. If it's of any use / interest, I could try
>CsoundVST as a VSTi in Ableton Live, Sonar 5, Cantabile 1.2, Project 5, etc.
>I've tried in all of those and I have only got CsoundVST to work as a VST in
>Live, and within it it seems unstable and reports 100% CPU usage even when
>audio is no processed through it. Trying to use it in the other hosts causes
>crashes, hangs, etc. This would be in a Windows 2000 SP4 environment...
>
>Adios,
>
>...r...
>
>
>Fine with me.
>
>My refactoring of VST SDK related things will be complete in a few days, I
>think. I have removed all VST SDK files from Csound CVS, and am in the midst
>of porting CsoundVST, vst4cs, and ScoreGen from VST SDK version 2.3 to
>version 2.4 (the current version). Coding is complete, and I am now
>debugging.
>
>I would like to see a Debian package completed for this next release.
>
>I would appreciate a list of "to dos" or a wish list for the next release.
>
>Regards,
>Mike
>
>-- 
>View this message in context: http://www.nabble.com/Next-Release-tf4156092.html#a11833065
>Sent from the Csound - Dev mailing list archive at Nabble.com.
>
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc.
>Still grepping through log files to find problems?  Stop.
>Now Search log events and configuration files using AJAX and a browser.
>Download your FREE copy of Splunk now >>  http://get.splunk.com/
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel




-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net