My suggestion is not to mirror the files unless you can do this 
automatically and transparently, such that whenever the SourceForge files 
are updated, the csounds.com files also are automatically updated. If that 
is not the case, then simply redirect downloaders to the appropriate 
SourceForge file release.

As for new features, in my view the features of greatest interest to 
MUSICIANS are:

-- The new opcodes of course, especially the fluid opcodes and the vst4cs 
opcodes (if someone can verify that they still work), but there are many and 
they should all be mentioned.

-- Improved real-time performance, including the ability to stop and restart 
a running instance of Csound.

-- The ability to run Csound as a VST plugin on Windows.

-- Improved ability to write algorithms to compose pieces: either in the 
Csound orchestra language, or in Python, Java, tcl, or LISP. When more user 
contributions in this vein show up, Csound should become competitive with 
SuperCollider as an integrated environment for both composition and 
synthesis.

-- The tcl shells and the use of CsoundVST as a Python shell.

-- A great deal of invaluable cleanup and debugging by Istvan, jpff, and 
others that make Csound more reliable.

-- A greatly improved and more correct manual.

-- Last but not least, installers that mean musicians can just USE Csound 
and do not have to build it from scratch with oodles of libraries to 
configure!

I think the features of greatest interest to DEVELOPERS would be:

-- Csound has become a proper loadable module with a well-defined API, 
exposed in C, C++, Python, LISP, and even Lua. This makes it much easier to 
embed Csound in other software as a sound synthesis engine.

-- Csound in turn has its own plugin architecture so that it is now much 
easier to embed _other_ software in Csound, such as plugin opcodes and 
drivers.

-- The multiple instantiability of Csound means that multiple instances of 
Csound can co-exist in the same program.


----- Original Message ----- 
From: "David Akbari" 
To: 
Sent: Tuesday, January 31, 2006 6:46 PM
Subject: [Cs-dev] Presentation of Csound5 on cSounds.com


> Hello gentlemen,
>
> The purpose of this email is to humbly ask suggestions / requests et al 
> for how the pending release of Csound5 should appear on cSounds.com.
>
> As you can probably see, the current status of cSounds.com attempts to 
> gear users at Csound 4, as it is the "current official release". Since 
> this will be exponentially less the case up until release, my question is 
> how and in what ways should Csound5 for all platforms be presented at 
> cSounds.com ?
>
> I am aware of Victor's installer for Mac OS X, Michael's Installer for 
> Windows / Istvan's .zip archives, and John ffitch's Linux installer + 
> Istvan's architecture specific gzipped tarballs.
>
> If Anthony could email the list or get at me privately concerning the 
> status of OS 9 I would really appreciate it as it is because of him that I 
> was able to get a small network of legacy Macintosh computers to enjoy the 
> fruits of Csound5. I hope this joy can be afforded to others through 
> cSounds.com.
>
> --> General Questions:
>
> 1) What files should be downloaded and mirrored / hosted on cSounds.com in 
> addition to SourceForge ? I would like this type of redundancy in case 
> either cSounds.com or SourceForge is temporarily unavailable for whatever 
> reason, in which case users can go to whichever available resource is 
> accessible.
>
> 2) What things about Csound5 do you, as developers feel is significant to 
> the Csound community at large pending the release of version 5 ? What 
> information should they be receiving that you feel is important ?
>
> 3) What frontends / extra tools are people using with the advent of 
> Csound5 ? Surely there are many more university projects in the same vein 
> as Cabel that would be extremely useful for end users. Any undergraduate / 
> graduate students doing Csound related work can also be highlighted - in 
> fact Dr. B has discussed the idea of having a "Csounder of the Week/Month" 
> what do you guys think about this feature ? In order to implement it 
> correctly we would need but not limited to:
>
> * Picture
> * Bio
> * Short piece audio / .csd file
> * Commentary / link to aux site
>
> 4) The Csound People page is woefully out of date. I would appreciate 
> users reporting any broken links they find as well as any additions they 
> feel should be there to this list or the general Csound list. This page is 
> in dire need of revision.
>
> 5) Any other information you think others should know ! Also comments are 
> **ALWAYS** welcome and appreciated concerning the INTERFACE of the website 
> and the accessibility of all your hard work. Suggestions on a preferred 
> resolution ? Right now it is optimized to >= 800x600 pixels although I can 
> see it causes some minor problems on browsers rendering at 640x480. 
> Although I am very much interested in compatibility with coarse 
> resolution, what is a good maximum to shoot for ?
>
>
> Csound is the ultimate realization of computer music software because of 
> the talent and hard work of developers such as yourselves. The community 
> benefits greatly from all of your contributions; you should be proud. 
> Please help me to spread the work you have worked so hard and for so long 
> on. It will undoubtedly bring joy to many people - I will personally try 
> my best to make sure it does so to as many people as possible.
>
> TIA,
> -David
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log 
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> 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. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Wonderful. Thank you, Michael. Your separation between the goals of  
target audiences is most helpful!

-David

On Jan 31, 2006, at 7:16 PM, Michael Gogins wrote:

> My suggestion is not to mirror the files unless you can do this  
> automatically and transparently, such that whenever the SourceForge  
> files are updated, the csounds.com files also are automatically  
> updated. If that is not the case, then simply redirect downloaders to  
> the appropriate SourceForge file release.
>
> As for new features, in my view the features of greatest interest to  
> MUSICIANS are:
>
> -- The new opcodes of course, especially the fluid opcodes and the  
> vst4cs opcodes (if someone can verify that they still work), but there  
> are many and they should all be mentioned.
>
> -- Improved real-time performance, including the ability to stop and  
> restart a running instance of Csound.
>
> -- The ability to run Csound as a VST plugin on Windows.
>
> -- Improved ability to write algorithms to compose pieces: either in  
> the Csound orchestra language, or in Python, Java, tcl, or LISP. When  
> more user contributions in this vein show up, Csound should become  
> competitive with SuperCollider as an integrated environment for both  
> composition and synthesis.
>
> -- The tcl shells and the use of CsoundVST as a Python shell.
>
> -- A great deal of invaluable cleanup and debugging by Istvan, jpff,  
> and others that make Csound more reliable.
>
> -- A greatly improved and more correct manual.
>
> -- Last but not least, installers that mean musicians can just USE  
> Csound and do not have to build it from scratch with oodles of  
> libraries to configure!
>
> I think the features of greatest interest to DEVELOPERS would be:
>
> -- Csound has become a proper loadable module with a well-defined API,  
> exposed in C, C++, Python, LISP, and even Lua. This makes it much  
> easier to embed Csound in other software as a sound synthesis engine.
>
> -- Csound in turn has its own plugin architecture so that it is now  
> much easier to embed _other_ software in Csound, such as plugin  
> opcodes and drivers.
>
> -- The multiple instantiability of Csound means that multiple  
> instances of Csound can co-exist in the same program.
>
>
> ----- Original Message ----- From: "David Akbari" 
> To: 
> Sent: Tuesday, January 31, 2006 6:46 PM
> Subject: [Cs-dev] Presentation of Csound5 on cSounds.com
>
>
>> Hello gentlemen,
>>
>> The purpose of this email is to humbly ask suggestions / requests et  
>> al for how the pending release of Csound5 should appear on  
>> cSounds.com.
>>
>> As you can probably see, the current status of cSounds.com attempts  
>> to gear users at Csound 4, as it is the "current official release".  
>> Since this will be exponentially less the case up until release, my  
>> question is how and in what ways should Csound5 for all platforms be  
>> presented at cSounds.com ?
>>
>> I am aware of Victor's installer for Mac OS X, Michael's Installer  
>> for Windows / Istvan's .zip archives, and John ffitch's Linux  
>> installer + Istvan's architecture specific gzipped tarballs.
>>
>> If Anthony could email the list or get at me privately concerning the  
>> status of OS 9 I would really appreciate it as it is because of him  
>> that I was able to get a small network of legacy Macintosh computers  
>> to enjoy the fruits of Csound5. I hope this joy can be afforded to  
>> others through cSounds.com.
>>
>> --> General Questions:
>>
>> 1) What files should be downloaded and mirrored / hosted on  
>> cSounds.com in addition to SourceForge ? I would like this type of  
>> redundancy in case either cSounds.com or SourceForge is temporarily  
>> unavailable for whatever reason, in which case users can go to  
>> whichever available resource is accessible.
>>
>> 2) What things about Csound5 do you, as developers feel is  
>> significant to the Csound community at large pending the release of  
>> version 5 ? What information should they be receiving that you feel  
>> is important ?
>>
>> 3) What frontends / extra tools are people using with the advent of  
>> Csound5 ? Surely there are many more university projects in the same  
>> vein as Cabel that would be extremely useful for end users. Any  
>> undergraduate / graduate students doing Csound related work can also  
>> be highlighted - in fact Dr. B has discussed the idea of having a  
>> "Csounder of the Week/Month" what do you guys think about this  
>> feature ? In order to implement it correctly we would need but not  
>> limited to:
>>
>> * Picture
>> * Bio
>> * Short piece audio / .csd file
>> * Commentary / link to aux site
>>
>> 4) The Csound People page is woefully out of date. I would appreciate  
>> users reporting any broken links they find as well as any additions  
>> they feel should be there to this list or the general Csound list.  
>> This page is in dire need of revision.
>>
>> 5) Any other information you think others should know ! Also comments  
>> are **ALWAYS** welcome and appreciated concerning the INTERFACE of  
>> the website and the accessibility of all your hard work. Suggestions  
>> on a preferred resolution ? Right now it is optimized to >= 800x600  
>> pixels although I can see it causes some minor problems on browsers  
>> rendering at 640x480. Although I am very much interested in  
>> compatibility with coarse resolution, what is a good maximum to shoot  
>> for ?
>>
>>
>> Csound is the ultimate realization of computer music software because  
>> of the talent and hard work of developers such as yourselves. The  
>> community benefits greatly from all of your contributions; you should  
>> be proud. Please help me to spread the work you have worked so hard  
>> and for so long on. It will undoubtedly bring joy to many people - I  
>> will personally try my best to make sure it does so to as many people  
>> as possible.
>>
>> TIA,
>> -David
>>
>>
>>
>> -------------------------------------------------------
>> This SF.net email is sponsored by: Splunk Inc. Do you grep through  
>> log files
>> for problems?  Stop!  Download the new AJAX search engine that makes
>> searching your log files as easy as surfing the  web.  DOWNLOAD  
>> SPLUNK!
>> http://sel.as-us.falkag.net/sel? 
>> cmd=lnk&kid=103432&bid=230486&dat=121642
>> _______________________________________________
>> 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. Do you grep through log  
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel? 
> cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> 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. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I tested today:
vstinit, vstprogset, vstparamget/set, vstmidiout, vstnote, vstaudio/g,
they all still work with Csound version 5.00.0rc2 beta (double samples) Jan 15 2006.

My testing have been basic usage, sending note on and off, changing programs and parameters.

I've noticed one odd thing:
If I try to load a non-existent vst plugin, csound segfaults.

Also, I have problems getting M-Tron to play more than one voice at a time (polyphonic). This seems strange, as I get normal polyphonic behaviour with other vst instruments, and M-Tron does have polyphony when I use it in Cubase. I'm clueless as to why it works differently in csound than in cubase, after trying to make it work for some hours now. This might very well be something strange in the part of M-Tron, as they (G-media) seem to have their own way of doing things... e.g. you can't send program changes to M-tron, but they have set up one of the parameter inputs to act as a program/bank change.

Oeyvind


> From: Istvan Varga [istvan_v@fibermail.hu]
> Sent: 2006-02-01 15:15:26 CET
> To: csound-devel@lists.sourceforge.net
> Subject: Re: [Cs-dev] Presentation of Csound5 on cSounds.com
> 
> On Wednesday 01 February 2006 01:16, Michael Gogins wrote:
> 
> > -- The new opcodes of course, especially the fluid opcodes and the vst4cs 
> > opcodes (if someone can verify that they still work)
> 
> The fluid opcodes should work (I think any problems still there are more
> likely to be bugs/limitations in FluidSynth itself), but the manual and
> examples seem to be somewhat out of date.
> 
> I did not try vst4cs, but it was recently reported by Oeyvind Brandtsegg
> that it does work at least to some extent.
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>