My goals would be (in decreasing order of importance):

1. Complete multi-threading of instrument instances and/or opcodes.

2. Change "engine" code from C to C++.

3. Better GUI front end, drop others.

4. Sample-accurate scheduling.

Things I have experimented with personally and like, that may be new to Csound designers:

1. Lua would be embedded in Csound, orchestra code could be written in Lua, when the Lua executes it wires up the existing kind of DSP graph. Ultimately, this would make it possible to write both compositions and orchestras in the same high-level language. Note: this is independent of the new parser. It could use, supplement, or replace the parser.

2. Javascript API, would enable embedding Csound in Web pages.

2b. Alternatively, a Java applet with embedded Csound shared libraries would also enable embedding Csound in Web pages.

3. Full "directed acyclical graph" type DSP graph, in place of instrument list/opcode list type graph.

Regards,
Mike

-----Original Message-----
>From: Victor Lazzarini 
>Sent: Oct 21, 2008 10:28 AM
>To: Developer discussions 
>Subject: Re: [Cs-dev] Version 6? ( was Re: Sample accurate k-rate was Re:Questions about musmon/insert)
>
>yes, exactly: clear and hopefully achievable goals.
>
>Regards
>
>Victor
>At 15:23 21/10/2008, you wrote:
>>Hi Victor,
>>
>>This sounds good to me.  I think we should lay out a clear plan of
>>what goals we want to achieve for Cs6, discuss until we iron out
>>exactly what we will commit to for a 6.0, then go for it!
>>
>>steven
>>
>>
>>On Tue, Oct 21, 2008 at 3:03 AM, Victor Lazzarini
>> wrote:
>> > I am wondering here whether we should start working on some
>> > possible structural changes (Version 6?) alongside the upgrades
>> > to Csound 5 (I am suggesting this because perhaps none here might
>> > have the stomach for another 4 year freeze).
>> >
>> > In other words: no major structural changes to Csound 5, but
>> > bugfixes, new opcodes,
>> > minor changes with 2 -3 yearly releases, as we have been doing.
>> >
>> > Alongside it, a 'bleeding edge' Csound 6.00 alpha, using only the new
>> > parser,  the
>> > current opcodes, a minimal API and space for radical changes. Some of
>> > us could then concentrate on that, while others work mostly on keeping
>> > and upgrading 5.
>> >
>> > Regards
>> >
>> > Victor
>> >
>> > At 09:34 21/10/2008, you wrote:
>> >>Problem with varying block size is that some opcodes make calculations
>> >>at init time what assumes fixed ksmps.  Not investigated closely but I
>> >>would be suspicious.  This would be a major change, and makes my
>> >>worries about counting time in samples seem rather trivial.
>> >>==John ffitch
>> >>
>> >>-------------------------------------------------------------------------
>> >>This SF.Net email is sponsored by the Moblin Your Move 
>> Developer's challenge
>> >>Build the coolest Linux based applications with Moblin SDK & win 
>> great prizes
>> >>Grand prize is a trip for two to an Open Source event anywhere in the world
>> >>http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> >>_______________________________________________
>> >>Csound-devel mailing list
>> >>Csound-devel@lists.sourceforge.net
>> >>https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >
>> > Victor Lazzarini
>> > Music Technology Laboratory
>> > Music Department
>> > National University of Ireland, Maynooth
>> >
>> >
>> > -------------------------------------------------------------------------
>> > This SF.Net email is sponsored by the Moblin Your Move 
>> Developer's challenge
>> > Build the coolest Linux based applications with Moblin SDK & win 
>> great prizes
>> > Grand prize is a trip for two to an Open Source event anywhere in the world
>> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> > _______________________________________________
>> > Csound-devel mailing list
>> > Csound-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >
>>
>>-------------------------------------------------------------------------
>>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
>>Build the coolest Linux based applications with Moblin SDK & win great prizes
>>Grand prize is a trip for two to an Open Source event anywhere in the world
>>http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>_______________________________________________
>>Csound-devel mailing list
>>Csound-devel@lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>Victor Lazzarini
>Music Technology Laboratory
>Music Department
>National University of Ireland, Maynooth 
>
>
>-------------------------------------------------------------------------
>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
>Build the coolest Linux based applications with Moblin SDK & win great prizes
>Grand prize is a trip for two to an Open Source event anywhere in the world
>http://moblin-contest.org/redirect.php?banner_id=100&url=/
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel




-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Michael Gogins wrote:
...
> Things I have experimented with personally and like, that may be new
> to Csound designers:
> 
> 1. Lua would be embedded in Csound, orchestra code could be written
> in Lua, when the Lua executes it wires up the existing kind of DSP
> graph. Ultimately, this would make it possible to write both
> compositions and orchestras in the same high-level language. Note:
> this is independent of the new parser. It could use, supplement, or
> replace the parser.

This is very interesting and would be very powerfull! I think the best
approach would be to export the DSP graph (orchestra syntax tree) stuff
to the API. And then a Lua-Csound would simply be a separate project,
linking to csound. Personally I'd instantly begin working on a
Nasal-Csound frontend. And a GTK orchestra gui. etc...

-- 
/Jonatan         [ http://kymatica.com ]

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net