What to expect in Ardour2

The Ardour team has made many changes beyond just the switch from gtk1 to gtk2.

Here is an incomplete feature list:

  1. Control Surface Architecture The guys have cooked up a plugin architecture for supporting control surfaces. It started with the tranzport, but who knows what will be controlling Ardour next.
  2. OSC Support One of the first plugins written using the COSA was basic support for OSC transport control. It's not possible to control a lot of Ardour functionality using OSC, but you can run the transport and control track record-enable states with it. Tested over a transatlantic link, this functionality will grow rapidly.
  3. Redone Soundfile Browser/Importer We've done away with the seperate hierarchy Ardour maintained for soundfiles. Now, it just uses the filesystem. As part of the gtk2 port, it uses the new file dialog, and it looks great. The new Sfdb dialog has more options on how to import/embed the soundfile. It still has custom metadata fields for adding your own info to each file, of course.
  4. Saved Undo This was a Google Summer of Code project that made the cut to be in the Ardour2.0 release. (Don't worry, the other two projects, midi and win32 will be released eventually.) Saved undo lets you quit or close a session, and when you reopen the session, you can still undo actions you had made. This is a cool feature that most software doesn't have.
  5. UI revamped to better expose functionality: new toolbar, better menus This happened naturally during the gtk2 port as we were cleaning up code. More actions are in the menus so you don't have to remember obscure key commands. The toolbar has also been redesigned so that it presents more information and is more usable.
  6. Destructive Recording Older versions of Ardour and almost all other DAWs focus on the non-destructive aspects of using computers for recording. But sometimes, you want to use your hard drive the way you might have used a tape if you had been recording 10 years ago. Ardour now has optional tracks that work this way - every overdub overwrites any existing material, destroying it but also not using more disk space. This isn't likely to be much use to musicians, but the feature was specifically targetted at film post-production audio engineers.
  7. 64-bit soundformats: WAV64, CAF Ardour now allows its native audio files (the ones created when you record stuff with ardour) to be in any of several different formats, including two 64-bit ones (wav64 and CAF). By selecting a 64-bit format, you can record continuously for 29 billion hours if you have big enough disks. Support for traditional formats like WAV and BWF continues, of course.
  8. A Logo! Many thanks to Thorsten Wilms for designing our new logo and putting up with us through its many iterations. It's great.
  9. Subversion Not a change to Ardour, but Subversion's easy branching made Google's Summer of Code possible. We now have more developers with commit access than ever.
  10. New Website Also not a change to Ardour, but I thought it was big enough to impact the Ardour community. Forums have been a big boost to sharing music, tips, and support. Thanks to all the people who have taken a minute to answer someone's question.

It won’t be in Ardour2, but work in the MIDI branch is being done (by necessity) that will allow this.

Future release schedule isn’t planned, but some release soonish after 2.0 will have it.

It sounds very nice. Thank you for bringing us that killer app!

Anyway, what about Hans Fugal’s per-region plugins Google SoC project mentionned on http://www.ardour.org/node/237 ?
I would be a great feature IMO.

I’m glad you’re interested in region plugins too. There just wasn’t enough summer to get both saved undo and region plugins done. As we are in feature freeze now, it won’t be in the initial release of Ardour 2, but it’s still something I would like to implement.

  • Sidechain for plugins -

    As for plugins - will there be sidechains for plugins in Ardour2?

Ardour now tells me that this is a feature in future versions (but maybe I’ve mixed something up here).
It would be really really cool to be able to use one track as the controlsignal for a plugin for another track (for example let the bassdrum trigger the compression of the bass).

Thanks a lot! I keep looking forward for ardour2 and all the new great features!

I’d like to second the request for the ability to use multiple input plugins, especially since attempting to use one simply fails, without even the option to use the plugin with one input active. There are some plugins that provide inputs for CV, sidechain, etc. but can be used without them.

  • 2 little features -

Thanks for this great app. What I miss mostly in the recent version is:

  • A high definition control on mouse to set plugins parameters, automations etc. Like a Ctrl + click to drag with high definition…

-A faster browser on the editor window. That permits zooms and browsing by anything such as Click+(up-down=zoom in, out; left-right=see things to the left, right).

IMO Ardour is already very, very good. But this two features would make working on it even more dynamic and fast, maybe way way more.

excellent new Taybin… any ideas on an ETA?


Sorry, we’ve had a horrible track record with ETAs.

thanks admin

114.- A high definition control on mouse to set plugins parameters, automations etc. Like a Ctrl + click to drag with high definition…

video converter for mac

GTK+ it is written in C, but has bindings to many other popular programming languages such as C++, Python and C# among others. GTK+ is licensed under the GNU LGPL 2.1 allowing development of both free and proprietary software with bedroom furniture GTK+ without any license fees or royalties.