Ardour has long had the option to use a "Control Outs" bus, but this design was never very well thought out, nor really adequate for professional use. In Ardour 3.0, we have added a new "Monitor Section" that is modelled on the similarly-named component of many large-format mixing consoles. This provides an additional output pathway for use in situations where the main outs of Ardour do not connect to the monitors used for mixing, and also offers many useful features for this type of configuration:
Although Ardour has always used multiple processors, until release 3.0 it has only ever used a single processor to run the DSP of all tracks and busses. Starting with this release, Ardour will utilize any number of processors to process track/bus DSP. The number used is configurable via the following preferences setting:
Ardour 3.0 is nearing its first alpha release. As usual, it has been available via SVN for those who want to build it from source during the entire development process, but we are now approaching the point where more user feedback will be useful in finalizing 3.0 before an official release. Below is a (growing) list of new features in 3.0, with links to individual pages that discuss them in more detail.
Ardour 2.8.11 is now available. It contains only 1 change from 2.8.10, but its an important one:
- Do not prevent transport operations after an export (and potentially at other times)
All users are strongly recommended to upgrade. Remember that if you have a subscription or paid for an earlier 2.8 version, and were logged into ardour.org at that time, upgrades are free!
- keyboard presses and releases are now correctly sent to Ardour created plugin GUIs (e.g. for LADSPA plugins), making it possible to use the keyboard to set parameter values and define preset names.
Just a couple of days since 2.8.8, and Ardour 2.8.9 is here. Why? It turned out that the infamous mute bug (which caused the mute button to do nothing) was actually not fixed in 2.8.8 (or prior versions where this has been claimed). This has been one of the worst regressions of recent versions of Ardour, and I mistakenly blamed packagers and distributions for it. Thankfully ardour.org member the_CLA spent time with me on IRC and we finally proved to my satisfaction that the bug was really in Ardour. Its now fixed, hopefully forever. Two other smaller but important bug fixes are described below ....
Its June and Ardour 2.8.8 is finally here. Time for everyone to upgrade!
Although this is primarily a bug-fix release, some of the "bugs" fixed are so pervasive and significant that they could almost count as new features. In particular, automation editing has finally arrived at a place that people with experience on other DAWs may consider actually usable. Issues with alignment of new and existing recorded material are addressed too, and there are lots of other bug fixes for issues small and large (including 3 or 4 crashing bugs). Thanks to motivation provided by the Mixbus project, there are also yet more improvements to AudioUnit plugin handling on OS X. Anybody using Ardour 2.8.7 or earlier should upgrade to enjoy increased stability and better functionality. Read more below ...
- Smarter decision making when deciding which in/out configuration to choose when handling an AU plugin that has several.
- When exporting/bouncing/consolidating, tell AU plugins the new processing blocksize so they will actually run during the process. Yes, that means what you think it means.
- Remove use of std::locale() which is utterly and completely broken on OS X, and causes a program to crash if used with any actual national locale.
- Don't reconfigure I/O of AU plugins when they already have the correct I/O configuration
Updated Czech translation from Pavel Fric
Ben Loftis, Paul Davis, Pavel Fric