Trying to solve a bug with importing audio, I spent the last couple of days adding a new feature to Ardour 3 that many people have been asked about for quite some time. Historically, Ardour has always stored the names of the audio files in one of two ways. One would indicate that the file lived inside the session, and the other indicated that it lived outside, somewhere else in your computer's filesystem. This meant that if you ever moved the location of the external files, Ardour wouldn't be able to find them at startup, and if you wanted the session to work, you'd need to hand edit the session file.
Well, now this is no longer true. Ardour will use a search path for all the files (audio & MIDI) that it needs for the session, and if it can't find them as it loads the session, it will ask you where to look for them. You can also edit the search path from the session properties dialog.
Just another reason for us to hurry up with the first alpha release of Ardour3, coming soon.
Linux audio documentarian (as well as swell guitar player, teacher, CSound wrangler and all around nice guy) Dave Phillips has written a very nice article for Linux Journal that describes "the ecology of Ardour", and covers a number of "off-screen" developments and collaborations that some readers might not be aware. Thanks to Dave for the nice article.
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!
(this announcement comes from John Emmas, developer of ArdourXchange)
Owners of Harrison's Mixbus can now obtain a very cheap copy of ArdourXchange if they act quickly. Throughout July 2010 AxC will be on sale for just $20 (US) - that's less than half its normal retail price.
Listed below are URLs for websites that have arranged for people to come to this forum and post links to their sites, even though their sites are totally unrelated to Ardour, audio engineering or anything remotely related to what this site is about. Quite a few of them are probably scams as well. This post will be updated and their names will be added. Google is quite good at indexing ardour.org. You spam our site, we add your URL here.
- 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.
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 ....