What's been going on with Ardour?
Mar 19, 2010, 15:34 (0 Talkback[s])
WEBINAR: On-demand Event
Replace Oracle with the NoSQL Engagement Database: Why and how leading companies are making the switch REGISTER >
"There hasn't been much news posted here for a while, so I
thought it was appropriate to update subscribers and other
supporters of my work on Ardour on what has been going on.
Development efforts have ben split (about 60:40) between Ardour 3.0
and continuing work on the 2.X series, both to fix bugs and to
support the continuing improvement of Mixbus.
"3.0 has been through some incredibly deep changes over the last
2-3 months, some of which I'm reluctant to describe because they
involve arcane details of programming and would bore those of you
who choose not to track the changes via the commit mailing list.
One exciting (and deep) change has been the move towards having the
Ardour history list just record changes to things like Playlists,
rather than recording their before and after state. This might seem
like an obvious way to do things, and indeed, its been in the "todo
sometime" list for ages. But as usual Carl H. jumped in and got the
ball rolling, and it became so clearly the right approach that I
took over and flushed most of the old approach away. The result is
that the history list now takes up a lot less memory - with big
sessions or sessions that have hundreds or more regions in a track,
the impact is very dramatic."