Ardour 5.1 released

Ardour 5.1 is primarily a bug fix release that corrects a number of issues (some notable, some minor) that were discovered after 5.0 had been released. There are a few new features and some improvements in the GUI, Lua and OSC support. Most users will want to upgrade to 5.1 as soon as possible.



  • Trimming regions with the mouse is now possible again, without changing program settings or hitting a 1 pixel wide strip.
  • Fixed bug with the a-reverb plugin's all-pass filters causing poor quality sound.
  • Do not alter the length of audio-locked MIDI regions when tempo map is changed, or when they are moved.
  • Fix crash when using plugins that (a) have internal latency (b) request musical time information.
  • The Linux installer now correctly handles spaces in the value of XDG_DESKTOP_DIR (so that, for example, "Área de Trabalho" will work).
  • Correctly notify plugins about musical time and tempo map changes.
  • On Linux, make Window Manager close/delete button (the "X" in most window manager window decorations) work for various dialogs.
  • Undo/redo is now prohibited while actively recording, to avoid creating bizarre condition.
  • Linking of aux send panners to track panners now behaves as intended.
  • Entering brush-drag mode (by pressing the "b" key) no longer remains in effect until program close.
  • Fix crash at exit if key bindings editor was open.
  • Fix crash when using video with non-integer aspect ratio in a locale that uses comma as the decimal point character.
  • Fix state restore in LV2 plugins (potential crash or deadlock).
  • Tempo marker movement now snaps to the future grid, not the current one (fixes jittering tempo movement when snapping with long accelerando/ritardando sections).

New Features and Improvements

  • New plugin: a-fluidsynth. Wraps the Fluidsynth SoundFont2 synthesis engine as a new sample player. Load SF2 sample libraries and play!
  • Region normalization can now use RMS analysis.
  • toggle-location-at-playhead.
  • Tweak keyboard shortcut modifier definitions to avoid overlaps between different kinds of functionality.
  • Allow first-move-direction constrained dragging of MIDI notes.
  • Group, automation state buttons in track headers and strips are now dropdowns.
  • Report quarter note rather than beat position to all plugins (reflecting a long-lived weakness in most DAWs and plugins that Ardour does not have but needs to work with).
  • Make many buttons that trigger menus behave more consistently with respect to press/release behaviour.
  • Ardour does not participate in "App Nap" on OS X.
  • Extending an empty selection (Shift-click) now selects the clicked region (similar behaviour to most other sane software of many kinds).
  • Duplicate tracks/busses dialog now has an "Insertion Point" selector to control where the new tracks/busses are placed.
  • Update GUI correctly when trimming a MIDI region changes its position.
  • Dropdown popup menus are now positioned much more appropriately.
  • Numerous small layout details in the GUI tweaked and improved.


  • Add new Lua APIs covering the following functionality:
    • Track coloring and ordering.
    • Session configuration.
    • Stripable (base class of all Tracks, Busses and VCAs).
    • Monitor Section.
  • Add track properties example script.

OSC Support

  • Add value feedback to main strip fader and and input trim control.
  • Control/setup GUI redesigned and extended, including preset loading and remote port setting (for TouchOSC and other crippled OSC controllers).

Known Outstanding Issues

Using Ardour on OS X with multiple monitors can result in dialogs being displayed on the wrong monitor when reloading a session.

Using Ardour on OS X and using dialogs results in the dialogs floating above all other windows on the screen, even if Ardour is not the "front" application.

Fixes for both these issues will be forthcoming in 5.2.


Nathan Stewart, Robin Gareus, Nick Mainsbridge, Paul Davis, Damien Zammit, John Emmas, Julien Rivaud, Tim Mayberry.

That was fast – always good to see how on top of bugs you guys are.

And a-fluidsynth is a great idea!

A-fluidsynth it is what wasn’t enough for me earlier.
Whether a-linuxsampler is planned?

khomkovm: I doubt it, though you can see what Paul says. Fluidsynth is designed to be integrated into other programs, LinuxSampler… not so much. It’s own LV2 plugin is barely usable for a lot of people. It would be a lot more work to integrate it.

How to switch instuments of SF2 bank through a-fluidsynth?
By default play instrument №1 which I can switch in virtualsampler, but in midi track play № 1 anyway.

By default a-fluidsynth assigns the first 16 programs of the .sf2 to the first 16 MIDI channels. You can use MIDI bank-select and program select to switch them.

In Ardour: On a MIDI region right click > Region > MIDI > Insert Patch change. or simply record them using a MIDI keyboard.

PS. if you set the Model in the track-header to “Generic > General MIDI” the names (CC and bank/programs) will match with e.g. FluidR3_GM.sf2 or CrisisGeneralMidi.sf2

There are no plans to integrate linuxsampler. It’s not even possible because LS is not GPL licensed. There is sfzero (a library to parse and load SFZ files) but it depends on JUCE to some extent and it also does not support all the “opcodes” that sfz defines.

Besides, a proper x-platform standalone LV2 plugin for SFZ (which can be bundled with Ardour) would be more useful at this point in time. a-fluidsynth is mainly a side-effect of allowing lua-scripts to use libfluidsynth.

Thanks. It is actually very convenient.
In general a lot of things became very convenient.