We had a meeting on Friday to review progress, and I am pleased to be
able to say that things are going well.

We already reported on the sample-accurate option (still in testing),
and separate compilation and replacement of instruments. This report is
about the other things.

We have re-written quantities of code to improve efficiency and to avoid
potential licence problems, and completed work on an asynchronous
I/O scheme.  There is a "real-time" mode using this and other things
which should remove glitches etc on instrument startup and smooth
performance.  In a similar vein the whole group of scheduling opcodes
have been reworked to remove duplication.

Work has almost been completed on arrays of variables, and indeed
multiple dimensional arrays.  This still needs a lot of testing and of
course documentation, but it will form a significant language
improvement.  In addition a few things like += syntax have been added
already. 

Work is in progress to make the multicore variant use less memory and
the new design has significantly less overheads.  Some improved
semantic analysis supports this, and a large internal change (150
files or so were changed) should allow for more precision in
parallelism as time allows.  Target is to get this working by mid
February.

Outstanding work is testing and more testing, followed by testing...

There is a small list of outstanding work (like revising strings in
the score, and revising the API) and a few items we would like to do,
but we will not delay release for them.

Targets are an alpha version mid February with a beta or release
candidate about Feb28.  The main potential delays are in sufficient
testing.  

And just to confirm, backward compatability of orchestras and score is
still embedded in all the changes.  All your previous pieces should
still just work, but there are new things to try.

==John ffitch

Fantasitc, fantastic, fantastic!

Big bow to all of the developers!

To test and use csound6, I have noticed there is csound6-git repository in 
sourceforge... Is there any any helping documentation about building and the 
language changes?

best!

tarmo


On Saturday, February 02, 2013 08:24:42 PM john ffitch wrote:
> We had a meeting on Friday to review progress, and I am pleased to be
> able to say that things are going well.
> 
> We already reported on the sample-accurate option (still in testing),
> and separate compilation and replacement of instruments. This report is
> about the other things.
> 
> We have re-written quantities of code to improve efficiency and to avoid
> potential licence problems, and completed work on an asynchronous
> I/O scheme.  There is a "real-time" mode using this and other things
> which should remove glitches etc on instrument startup and smooth
> performance.  In a similar vein the whole group of scheduling opcodes
> have been reworked to remove duplication.
> 
> Work has almost been completed on arrays of variables, and indeed
> multiple dimensional arrays.  This still needs a lot of testing and of
> course documentation, but it will form a significant language
> improvement.  In addition a few things like += syntax have been added
> already.
> 
> Work is in progress to make the multicore variant use less memory and
> the new design has significantly less overheads.  Some improved
> semantic analysis supports this, and a large internal change (150
> files or so were changed) should allow for more precision in
> parallelism as time allows.  Target is to get this working by mid
> February.
> 
> Outstanding work is testing and more testing, followed by testing...
> 
> There is a small list of outstanding work (like revising strings in
> the score, and revising the API) and a few items we would like to do,
> but we will not delay release for them.
> 
> Targets are an alpha version mid February with a beta or release
> candidate about Feb28.  The main potential delays are in sufficient
> testing.
> 
> And just to confirm, backward compatability of orchestras and score is
> still embedded in all the changes.  All your previous pieces should
> still just work, but there are new things to try.
> 
> ==John ffitch
> 
> 
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"

thanks for this report, john. i am happy to help in testing. very 
curious in particular about the arrays and the real-time mode.

	joachim


Am 02.02.2013 21:24, schrieb john ffitch:
> We had a meeting on Friday to review progress, and I am pleased to be
> able to say that things are going well.
>
> We already reported on the sample-accurate option (still in testing),
> and separate compilation and replacement of instruments. This report is
> about the other things.
>
> We have re-written quantities of code to improve efficiency and to avoid
> potential licence problems, and completed work on an asynchronous
> I/O scheme.  There is a "real-time" mode using this and other things
> which should remove glitches etc on instrument startup and smooth
> performance.  In a similar vein the whole group of scheduling opcodes
> have been reworked to remove duplication.
>
> Work has almost been completed on arrays of variables, and indeed
> multiple dimensional arrays.  This still needs a lot of testing and of
> course documentation, but it will form a significant language
> improvement.  In addition a few things like += syntax have been added
> already.
>
> Work is in progress to make the multicore variant use less memory and
> the new design has significantly less overheads.  Some improved
> semantic analysis supports this, and a large internal change (150
> files or so were changed) should allow for more precision in
> parallelism as time allows.  Target is to get this working by mid
> February.
>
> Outstanding work is testing and more testing, followed by testing...
>
> There is a small list of outstanding work (like revising strings in
> the score, and revising the API) and a few items we would like to do,
> but we will not delay release for them.
>
> Targets are an alpha version mid February with a beta or release
> candidate about Feb28.  The main potential delays are in sufficient
> testing.
>
> And just to confirm, backward compatability of orchestras and score is
> still embedded in all the changes.  All your previous pieces should
> still just work, but there are new things to try.
>
> ==John ffitch
>
>
> Send bugs reports to the Sourceforge bug tracker
>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>

This is quite wonderful news. Many thanks to all the developers of Csound. I don't know how I would manage without this wonderful tool.

-Lou Cohen

On Feb 2, 2013, at 3:24 PM, john ffitch  wrote:

> We had a meeting on Friday to review progress, and I am pleased to be
> able to say that things are going well.
> 
> We already reported on the sample-accurate option (still in testing),
> and separate compilation and replacement of instruments. This report is
> about the other things.
> 
> We have re-written quantities of code to improve efficiency and to avoid
> potential licence problems, and completed work on an asynchronous
> I/O scheme.  There is a "real-time" mode using this and other things
> which should remove glitches etc on instrument startup and smooth
> performance.  In a similar vein the whole group of scheduling opcodes
> have been reworked to remove duplication.
> 
> Work has almost been completed on arrays of variables, and indeed
> multiple dimensional arrays.  This still needs a lot of testing and of
> course documentation, but it will form a significant language
> improvement.  In addition a few things like += syntax have been added
> already. 
> 
> Work is in progress to make the multicore variant use less memory and
> the new design has significantly less overheads.  Some improved
> semantic analysis supports this, and a large internal change (150
> files or so were changed) should allow for more precision in
> parallelism as time allows.  Target is to get this working by mid
> February.
> 
> Outstanding work is testing and more testing, followed by testing...
> 
> There is a small list of outstanding work (like revising strings in
> the score, and revising the API) and a few items we would like to do,
> but we will not delay release for them.
> 
> Targets are an alpha version mid February with a beta or release
> candidate about Feb28.  The main potential delays are in sufficient
> testing.  
> 
> And just to confirm, backward compatability of orchestras and score is
> still embedded in all the changes.  All your previous pieces should
> still just work, but there are new things to try.
> 
> ==John ffitch
> 
> 
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 

Lou Cohen
www.jolc.net
www.opensound.org

hello

On 02/02/13 21:05, Louis Cohen wrote:
> This is quite wonderful news. Many thanks to all the developers of Csound. I don't know how I would manage without this wonderful tool.

i want to say the same, but i guess i'll introduce a few variations:

This is  wonderful news. Many thanks to all the developers of 
Csound. I don't know how I would manage without this  tool.

-- 
\js [http://or8.net/~johns] (let (listen t) ())