<HTML>
Excellent <BR>
<BR>
This is great news.. As expressed before I would love to assist with the alpa testing of the MIDI functionality..(especially clock functions). <BR>
I'm checking in with the Gentoo Pro-Audio list to see how I can run concurrent versions... but probably need some basic instructions on how to compile different branches from SVN..... (which would probably be outside the ebuild system unless I start writing my own).. so any pointers to documents would be great.. <BR>
<BR>
Unfortunately the last couple of months I haven't been able to help due to recording, gig promotion and family commitments. However, things should settle down towards the end of January, so I'll be on board... <BR>
<BR>
cheers<BR>
<BR>
Allan<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<B>On Fri Dec 12 7:40 , Paul Davis <PAUL@LINUXAUDIOSYSTEMS.COM>sent:<BR>
<BR>
</B>
<BLOCKQUOTE style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #f5f5f5 2px solid; MARGIN-RIGHT: 0px"><BR>
Ardour 2.7.1 is now feature frozen. No new features will be added to the<BR>
2.0-ongoing branch of the program, with the following exceptions:<BR>
<BR>
1) support for saving & loading AU plugin settings<BR>
2) (re)use Apple's ExtAudioFile library to allow MP3 and AAC <BR>
handling on OS X<BR>
3) minor features that are implemented in 3.0 and can be back-ported<BR>
to 2.0-ongoing with no code changes<BR>
<BR>
If you are a user with an idea for a new feature, please it in Mantis,<BR>
but do not expect to see it appear in any 2.X release. It is not<BR>
impossible that it may do so, but your expectations of this should be<BR>
low.<BR>
<BR>
Why is this happening?<BR>
----------------------<BR>
<BR>
The release of 3.0 has been delayed for far too long, primarily by a<BR>
lack of developer hours devoted to advancing its current condition. The<BR>
pressure to get the OS X and SAE versions released led to both myself<BR>
and Nick Mainsbridge (along with other developers possibly following<BR>
both their own itches and our lead) focusing on the 2.0-ongoing branch.<BR>
<BR>
This needs to stop, and almost all developer attention to ardour should<BR>
be directed towards 3.0. The plan is roughly as follows:<BR>
<BR>
1) Paul finishes up the merge of 2.0-ongoing changes from <BR>
rev 3890 to rev 4299 into the 3.0 branch<BR>
2) All hands on deck to start finding bugs in the *audio* <BR>
part of 3.0. This should include Ardour developers<BR>
and our leading beta testers, as well as anybody else<BR>
who wants to join in. The focus will not be on de-novo<BR>
criticisms of Ardour's audio functionality - we just<BR>
need to get 3.0 to function as well as 2.7.1 does in<BR>
the audio realm. <BR>
3) Once the bug-finding and -fixing is done, I will lead the<BR>
effort up to a half-dozen substantive features<BR>
to Ardour 3.0's audio side. These will include:<BR>
<BR>
* the new "matrix" IO selector<BR>
* the long-promised overhaul of bus architecture<BR>
* the ability to work on 2.X sessions without<BR>
making them unusable by 2.X ardour versions<BR>
<BR>
4) While this work goes on, anybody who wants to work on MIDI,<BR>
either as an alpha-tester or as a developer is welcome<BR>
to do so.<BR>
<BR>
5) When (3) is "complete", I would like to collect together<BR>
information gathered in step (4), and do a comprehensive<BR>
review & proposal of how the current MIDI editing interface<BR>
functions. We need to gather together user experience and<BR>
make sure that the first official release of 3.0 is capable<BR>
of being easily used to do relatively easy MIDI tasks.<BR>
<BR>
6) Release 3.0<BR>
<BR>
Once an initial version of 3.0 is released, it will be time for some<BR>
more drastic changes to the codebase. This will likely include things<BR>
like replacing edit groups with named track selections, changes to the<BR>
playlist structures to support linked (soft-copy) regions, region<BR>
grouping, new GUI handling of sends, and last but not least, the<BR>
addition of a language for MIDI manipulation, allowing MIDI "filters" to<BR>
be trivially written by people without C++ backgrounds.<BR>
<BR>
--p<BR>
<BR>
_______________________________________________<BR>
Ardour-Users mailing list<BR>
<A href="javascript:top.opencompose('ardour-users@lists.ardour.org','','','')">ardour-users@lists.ardour.org</A><BR>
<A href="parse.pl?redirect=http%3A%2F%2Flists.ardour.org%2Flistinfo.cgi%2Fardour-users-ardour.org" target=_blank><SPAN style="COLOR: #ff0000">http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org</SPAN></A><BR>
)<BR>
</BLOCKQUOTE></HTML>
<BR>