AATranslator is a Windows program that converts sessions created in one DAW (or video editor) into formats understood by others. It supports session formats used by ProTools, Nuendo, Cubase, PreSonus Studio One, Vegas, Reaper, Wavelab, Pyramix, AMS Audiofile, Fairlight, Waveframe, DAR, N-Track, Sadie, Soundscape and more.
We heard today that its support for Ardour is now complete (for the moment), meaning that it can both import and export to/from Ardour. Read on below for more details on what it can do ....
Although Ardour 2.8.9 no longer suffers from the subtle bug that caused the mute button(s) to no longer work by default, many users of Ardour will not see the situation change until they remove their
~/.ardour2/ardour.rc file. This probably contains default settings for mute like this:
<Option name="mute-affects-pre-fader" value="yes"/> <Option name="mute-affects-post-fader" value="yes"/> <Option name="mute-affects-control-outs" value="yes"/> <Option name="mute-affects-main-outs" value="yes"/>
If your version of this file has
value="no" for those options, you should either edit it by hand (its just a text file) so that it says
value="yes" instead or just remove the file entirely. Editing is preferable, but removing the file will not hurt. Note that the following values
y,Y,1,yes,Yes,YES are all equivalent to "yes" and similarly
n,N,0,no,No,NO are all equivalent to "no".
You should also check the file
/etc/ardour2/ardour_system.rc, or a related location if you installed Ardour somewhere non-standard) for the same issue, though it is less likely to be seen there. Do NOT remove this file - if it contains "no" as the settings for these options, you should edit the file.
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 ...
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. 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
People sometimes criticize a piece of software as being "unintuitive". In fact, its one of the most common complaints you'll hear whenever anyone starts using a new piece of software. Its often entirely justified too - its rare that a complex application manages to be obvious to every new user, or even most new users. Some software developers have a good track record here, Apple in particular, whose rules and guidelines for how to design user interfaces keeps on manage to churn out remarkably intuitive software. Well, it does as long the application is fairly simple and its scope is well defined. By the time you get to applications such as Final Cut Pro or Logic Pro, it would be hard to find anyone who found them "intuitive" in the same way that, say, iTunes or even Garageband is. Read more below ...