I would like to see the following changes in future versions of Csound, roughly in decreasing order of importance:

-- Get Csound 5 into Linux distributions in place of 4.23.

-- Get Csound 5 into Common Music as a native output stream.

-- Distribute only one Csound GUI. It should contain a Csound editor with syntax highlighting. The main question for me is should it have dialog boxes for settting all command line options, or just a text field for entering the options manually, or also have some buttons for common combinations of options? (e.g. real-time, CD quality soundfile, high-resolution soundfile). The other GUIs should not be distributed although they could remain in CVS or as separate distributions, if anyone wants to maintain them (I don't).

-- Create better examples with a high WOW factor.

-- Move the Silence algorithmic composition classes out of CsoundVST and into csnd, as they are quite cross-platform in nature, and provide a tutorial for using them.

-- Change the CSOUND structure to a proper C++ class. This would make it much easier both to extend, and to maintain, Csound and the Csound API. It would not make Csound slower.

-- Improve the Csound API documentation.

-- When the parser works, remove the non-parser code.

-- Provide an option for running instrument instances in separate threads from a thread pool. This might require synchronizing access to global objects such as function tables, input and output queues and buffers, etc. In a year or so, when 4 CPUs are common, this will greatly speed up rendering.

-- Upgrade the VST implementation to the latest VST SDK from Steinberg.


Regards,
Mike

-----Original Message-----
>From: Steven Yi 
>Sent: Jan 10, 2007 11:45 AM
>To: Developer discussions 
>Subject: [Cs-dev] Status Update Request
>
>Hi All,
>
>It being a new year I thought I'd query the list to see what everyone
>thought about Csound's current status as well as seeing about things
>we would all like to achieve with where to take Csound.
>
>Regarding the current release of Csound, I think that the fix that
>Anthony suggested and that I checked in regarding paths on Windows
>seems like it should get out to the public as quickly as possible and
>I'd like to request that at least a new Windows build be released and
>better if a new release all around was to happen.  I don't think it
>would have to be a major point release, just a minor mostly bug fix
>release so maybe 5.04.1.  It seems that the bug has caused a number of
>problems for people either using the GUI's or API.  Any thoughts?
>
>Also, I don't remember the status of the problem David Akbari posted
>about and if that was ever resolved.
>
>Regarding where Csound is going, I realized that in the past when
>there was heated ranting by a user or users that it often spurred a
>lot of quick (if stressful!) changes.  Rather than waiting for a
>heated rant, shall we poll the main list for user thoughts on where
>they see deficiencies in the current Csound releases?
>
>As for personal work, I've taken a long break from the new parser but
>I think will resume work on that next week.  Rather than continue to
>work on that in a separate branch I'd like to integrate that back into
>the HEAD branch as well as do as I mentioned a month or so ago, which
>is to set up two layers of options to use: one in SConstruct that
>would build in the new parser or not, and second a commandline flag to
>enable using the new parser.  Both of those would default to no,
>meaning if you just checked out from CVS and didn't turn on to build
>the parser, nothing would change for you.  Even if you built with the
>new parser, it wouldn't be used unless explicitly told to via
>commandline, so again nothing would change for normal usage.  The code
>is encapsulated into its own files so does not affect the current use
>of Csound even when compiled in, so I think this is very safe to
>integrate.  If everyone is okay with this, I'll go ahead on Monday to
>integrate and start working from there.
>
>Thanks!
>steven
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share your
>opinions on IT & business topics through brief surveys - and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel




-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Michael Gogins wrote:

> -- Change the CSOUND structure to a proper C++ class. This would make
> it much easier both to extend, and to maintain, Csound and the Csound
> API. It would not make Csound slower.

Creating bindings for other high level languages is usually far easier
when wrapping C than when wrapping C++.

MY personal favourite among the high level languages is Ocaml. I am in
the prcoess of creating a binding for libsndfile and its really not
very difficult. I have also looked into wrapping a C++ library and
found that to be a complete nightmare, so much so that I probably
won't pursure it any futher.

Erik
-- 
+-----------------------------------------------------------+
  Erik de Castro Lopo
+-----------------------------------------------------------+
"The question of whether a computer can think is no more interesting 
than the question of whether a submarine can swim." -- edsger dijkstra

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

The one GUI should absolutely have tabs and buttons to choose  
settings and command-line options.  (as preferences)

On Jan 10, 2007, at 1:19 PM, Michael Gogins wrote:

> I would like to see the following changes in future versions of  
> Csound, roughly in decreasing order of importance:
>
> -- Get Csound 5 into Linux distributions in place of 4.23.
>
> -- Get Csound 5 into Common Music as a native output stream.
>
> -- Distribute only one Csound GUI. It should contain a Csound  
> editor with syntax highlighting. The main question for me is should  
> it have dialog boxes for settting all command line options, or just  
> a text field for entering the options manually, or also have some  
> buttons for common combinations of options? (e.g. real-time, CD  
> quality soundfile, high-resolution soundfile). The other GUIs  
> should not be distributed although they could remain in CVS or as  
> separate distributions, if anyone wants to maintain them (I don't).
>
> -- Create better examples with a high WOW factor.
>
> -- Move the Silence algorithmic composition classes out of  
> CsoundVST and into csnd, as they are quite cross-platform in  
> nature, and provide a tutorial for using them.
>
> -- Change the CSOUND structure to a proper C++ class. This would  
> make it much easier both to extend, and to maintain, Csound and the  
> Csound API. It would not make Csound slower.
>
> -- Improve the Csound API documentation.
>
> -- When the parser works, remove the non-parser code.
>
> -- Provide an option for running instrument instances in separate  
> threads from a thread pool. This might require synchronizing access  
> to global objects such as function tables, input and output queues  
> and buffers, etc. In a year or so, when 4 CPUs are common, this  
> will greatly speed up rendering.
>
> -- Upgrade the VST implementation to the latest VST SDK from  
> Steinberg.
>
>
> Regards,
> Mike
>
> -----Original Message-----
>> From: Steven Yi 
>> Sent: Jan 10, 2007 11:45 AM
>> To: Developer discussions 
>> Subject: [Cs-dev] Status Update Request
>>
>> Hi All,
>>
>> It being a new year I thought I'd query the list to see what everyone
>> thought about Csound's current status as well as seeing about things
>> we would all like to achieve with where to take Csound.
>>
>> Regarding the current release of Csound, I think that the fix that
>> Anthony suggested and that I checked in regarding paths on Windows
>> seems like it should get out to the public as quickly as possible and
>> I'd like to request that at least a new Windows build be released and
>> better if a new release all around was to happen.  I don't think it
>> would have to be a major point release, just a minor mostly bug fix
>> release so maybe 5.04.1.  It seems that the bug has caused a  
>> number of
>> problems for people either using the GUI's or API.  Any thoughts?
>>
>> Also, I don't remember the status of the problem David Akbari posted
>> about and if that was ever resolved.
>>
>> Regarding where Csound is going, I realized that in the past when
>> there was heated ranting by a user or users that it often spurred a
>> lot of quick (if stressful!) changes.  Rather than waiting for a
>> heated rant, shall we poll the main list for user thoughts on where
>> they see deficiencies in the current Csound releases?
>>
>> As for personal work, I've taken a long break from the new parser but
>> I think will resume work on that next week.  Rather than continue to
>> work on that in a separate branch I'd like to integrate that back  
>> into
>> the HEAD branch as well as do as I mentioned a month or so ago, which
>> is to set up two layers of options to use: one in SConstruct that
>> would build in the new parser or not, and second a commandline  
>> flag to
>> enable using the new parser.  Both of those would default to no,
>> meaning if you just checked out from CVS and didn't turn on to build
>> the parser, nothing would change for you.  Even if you built with the
>> new parser, it wouldn't be used unless explicitly told to via
>> commandline, so again nothing would change for normal usage.  The  
>> code
>> is encapsulated into its own files so does not affect the current use
>> of Csound even when compiled in, so I think this is very safe to
>> integrate.  If everyone is okay with this, I'll go ahead on Monday to
>> integrate and start working from there.
>>
>> Thanks!
>> steven
>>
>> --------------------------------------------------------------------- 
>> ----
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to  
>> share your
>> opinions on IT & business topics through brief surveys - and earn  
>> cash
>> http://www.techsay.com/default.php? 
>> page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>
>
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net