Ardour 3.0 alpha 4 is here with a mixture of bug and packaging fixes. Pick up the packages:
- Linux, 32 bit: http://ardour.org/files/Ardour_32bit-3.0alpha4_9292-dbg.tar
- Linux, 64 bit: http://ardour.org/files/Ardour_64bit-3.0alpha4_9292-dbg.tar
Another day, another alpha release. And yes, the URLs do not end in ".bz2" anymore. See below for why ...
- 64 bit Linux: http://ardour.org/files/Ardour_64bit-3.0alpha3_9210-dbg.tar
- 32 bit Linux: http://ardour.org/files/Ardour_32bit-3.0alpha3_9210-dbg.tar
Changes since alpha 2
- OSC control now included
- MIDI binding maps now included (and usable)
- Package now has an installer, and a README file.
The installer will put the package into /opt and will attempt to put a link to it on your desktop. The uninstall script (also placed in /opt will remove both the package and the desktop link.
- name changed to 3.0alpha3
- 32 bit linux: http://ardour.org/files/Ardour_x86-3.0alpha1_9197-dbg.tar.bz2
- 64 bit linux: http://ardour.org/files/Ardour_x86_64-3.0alpha1_9197-dbg.tar.bz2
Changes since alpha 1
- "Light" GUI theme now included (no more crashing if you switch to use it)
- Control surfaces now discovered correctly (not yet OSC, that will be in alpha 3)
- fixed crash when saving MIDI region automation
- MIDI note display now uses "scientific notation" (http://en.wikipedia.org/wiki/Scientific_pitch_notation
- a couple of build system improvements and fixes
- MIDI hardware ports have slightly prettier names (no more alsa_pcm: prefix)
More will be written about this feature once its closer to completion. For now, let's just note that it replaces the old 2D panner in Ardour 2.X with code based on VBAP (Vector Base Amplitude Panning). Here's a boring screenshot of the panner:
Lincoln Spiteri did some excellent work adding several new editing features which link into his non-layered mode. The general idea here is a workflow that doesn't rely on crossfades and generally avoids region overlaps. However, these editing operations are useful whether you use this track mode or not.
The latest release of JACK includes a new feature called "JACK Session" which allows the creation of "session manager" applications that can snapshot an entire JACK session, and then restart them en masse at a later time. If you're using Ardour in combination with some external software synth or FX application, JACK Session allows you to store the state of all the JACK applications at once, and then later, restart the exact same setup to continue working smoothly.
Working with a track that has many overdubs can sometimes be a little confusing because its not always entirely clear how the overdubs are all layered with respect to each other. Although there are other methods of moving particular regions to the top of an overlapping set, and although Ardour also has playlists to let you manage takes a bit more efficiently than just continually overdubbing, there are times when being able to clearly see all regions in a track without any overlaps is reassuring and potentially useful.
The information displayed in the track list within the right-hand side notebook of the editor window has been expanded to provide an at-a-glance summary of track/bus status. Because each track takes up just a single line in the list, its possible to display information (and control status) for many more tracks than many be visible in the main part of the editor window.
On the left side of the track list is a set of indicators/buttons that show the following status for each track/bus:
Ardour's ability to import external media files remains essentially unchanged in version 3.0, but thanks to work by Sakari Bergen, an entirely new kind of import is now possible: importing specific material from another session.
Session->Import From Session ..., this process is driven via a dialog that allows to select an existing session file or snapshot (basically any file ending in ".ardour"). It then presents a list of elements that can be imported: Regions, Tracks, Playlists, Locations, and the tempo map.
One long-standing complaint from users in Ardour 2.X was the impossibility of moving track automation data when dragging regions. This behaviour came from a very early assessment of workflow when Ardour was first being developed, and I freely admit that I was wrong about this design.