Ardour 3.5.143 released

Continuing on with our cycle of monthly releases, 3.5.143 is a bug fix release that comes out while other major development work continues on in the background. It fixes a handful of major bugs, notably with MIDI Clock, Generic MIDI control and Mackie Control support. You'll also find monitoring source control in the meter bridge, a new K12/RMS meter type, and more than a dozen other bug fixes.

As usual you can download it from the usual place, and as usual subscribers get this update without cost. Thanks to everyone for their support (and encouragement).

Once again, the OS X release situation has still not improved, though a demo 64 bit copy of 3.4 is available (fully featured except that is has does not have the video timeline, no saving or restoring of plugin settings, and no plugin presets).

Functional Bug Fixes

  • fix continuous send of MIDI start/position/stop messages introduced by mistake in last release
  • deliver MIDI clock position messages when stopped (e.g. when locating)
  • Mackie Control support now saves & restores port connections
  • fix feedback for Generic MIDI control support

New Features

  • allow (optional) In/Disk monitoring button in Meter Bridge
  • add K12/RMS meter type


  • When editing a clock value in "Samples" mode, treat an empty edit as a no-op.
  • Distinguish Save-as and Snapshot dialog windows
  • Metering: reset time-axis peak when meter-point changes
  • Fix for toolbar master-meter w/o master bus and/or detached toolbar
  • Fix a crash during export when using 8 bit format
  • Various minor fixups for the Audio/MIDI setup dialog
  • Fix up a bunch of confusion regarding the size/capacity/allocation of audio & midi buffers
  • Don't run MIDI clock "tick" if session is silent (e.g. due to a locate)
  • Load VST plugins using version > 2.4 but print a warning for each one (they may simply not work)
  • Recognize ppc64, ppc, s390x, s390 CPUs, default to 'none' instead of i686 (which tries to build with SSE and fails on non-x86 architectures).
  • Distinguish flags influencing optimization (overridable) from those necessary for building (e.g. for using SSE).
  • Fix a bug where memset was being used to fill a gain buffer with 1.0
  • Compare region names case-sensitively
  • Compare plugin/creator/category names UTF8-aware
  • LV2 plugins: adjust LV2 ringbuffer size according to LV2:resize-port
  • LV2 plugins: increase scratch buffer size to request port minimum size
  • rsynth.lv2: fix octave, and fix note off+on within same synth cycle
  • Midi Clock: fix wrong calculation of loop error, and fix bandwidth to 2/60 for best results
  • Mackie Control: fix various subtle problems when changing devices


Nils Philippsen, Robin Gareus, Hans Baier, Sakari Bergen, Paul Davis

Thanks a lot ! Best wishes for the coming Days…

the jackosX link :

Brilliant stuff - esp. the mackie control port connection recall.

However, on my bcf2000 in mackie mode, it doesn’t restore the fader positions on load of a project (sets them to zero) with no apparent feedback even when i start play. When I use the bank controls on the bcf to move across the channel sets, it suddenly comes to life and restores the positions and then responds to feedback with movement of the motorised faders.

Tried restoring back to 3.5.130 from git and checked, the fader positions are loaded on start and feedback is sent immediately IF the playback head is in the middle of the project. If the playback head is at the beginning of the project, no feedback is sent back.

Will file a bug report on this.

3.5.143 somehow distorted one of my firewire soundcards. I tried to restart both computer and soundcards in sequence but nothing helped so I downgraded and that corrected it.
I’ll stay with 3.5.74 for now.

Bug reports on the forums will be ignored. That is the way it is, has been and always will be.

Of course, the ones in the bug tracker are not getting a lot of love right now either :frowning:

Great in this update: sync operations through midi now run fine. Thanks!

Hey, Paul: I take it that the OSX version doesn’t write/save plug-in automations either (haven’t figured it out and the manual page on automations is blank)? Any idea when there might be a release that unlocks some plug-in features ( I’ll pay :slight_smile: )? Very glad to have switched to Ardour. Keep up the great work.

the OS X demo version will save and use automation values. It will not save/restore presets.