We had a project meeting at noon today to consider where we were and
what was needed.  The discussions were detailed and often esoteric and
not necessarily useful for other than those directly involved.
However we thought some progress report might be useful.  Bottom line
is that we have been busy over the holiday season!

As previously announced here progress has been significant in separate
compilation/replaceable instruments although we still have some memory
leaks and rough edges.  Similarly the sample-accurate starting and
stopping of note-events is progressing well.  Since the earlier
messages on this list we have made a good start on testing, and have
identified a couple of issues which are now fixed.  More testing and
checking is needed.

The unannounced work mainly relates to the orchestra language; we will
explain that in due course.  We are also looking at score language
changes, backward compatible of course.  There is a (shortish) list of
changes/corrections we would like to make but we feel that we can now
dare to give a timetable:

All current main coding is expected to be completed by the end of this
month, so we can have a beta version available in February, and a
first release candidate at the end of February.  With such major
changes we must expect there to be issues brought up, but we plan an
alpha version in March with a release date in April.

At present we are still in a "computer science" mode, but we would
like people to test come end of January.  In addition I will be
contacting a few opcode authors seeking help over some more
complicated changes.

As ever the Sourceforge csound6 git is readable if you are really
curious, but it is certainly not usable as it stands, often swamped
with debugging messages etc.

The timetable is realistic with just a shade of optimism.  However to
fill the gap we will be releasing 5.19 next week mainly to fix bugs
since last August.

And Happy New Year to you all
==John ffitch


Feb 2013 -- beta version
March 2013 -- first release candidate
April 2013 -- full release

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122712
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thanks for the updates John, and to everyone involved in this amazing
work. I can't wait to sink my teeth in Csound 6!

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122712
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi John,

Thanks for the update. Interesting things ahead! I'll have to hurry up If I want to clean up the channel interfaces!

Do you have a transcript of the meeting? I'm interested in the details.

Also, I'm happy to see that opcodes are now sample accurate, but it makes me wonder if there could be a way to do this not for every opcode, as this puts the onus on plugin writers to get it right, but in the engine itself, so that plugins opcodes are kept as simple as possible. It also seems to me that this causes a lot of code duplication. If this facility was in the engine, you could also turn it off to increase performance if you needed to by adding event jitter. What do you think?

Cheers,
Andres