Ardour 3.2 released - Video comes to Ardour

    Über-developer Robin Gareus has worked for a couple of years
    to add video support to Ardour, and with this release, we are
    pleased to finally enable it. In addition there are a couple
    of new features (including the ability to chain MIDI
    processing plugins) and the usual assorted list of bug fixes.
    As usual, you can fetch the update
    from <a href="/download">the download page</a>.

Video Support

screenshot of an ardour session showing video timeline and video monitor window

The integration of a video timeline and video monitoring into Ardour allows for convenient audio mixing and editing to video (i.e. soundtracks, music videos, TV post production etc.)

    The new functionality allows users to:
      <li> Import a single video and optionally extract the soundtrack from it.
      <li> Provide a Video-monitor window, or full-screen display, of the imported video in sync with any of the available ardour timecode sources.
      <li> Display a frame-by-frame (thumbnail) timeline of the video.
      <li> Time-offset the video.
      <li> Lock audio-regions to the video: Move audio-regions with the video at video-frame granularity.
      <li> Export the video, cut start/end, add blank frames and/or mux it with the soundtrack of the current-session.
    Furthermore, the setup is modular and can be configured in different ways, including:
      <li>One machine: all video decoding, video monitoring and Ardour audio
      <li>Two machines: separate video-monitor and Ardour
      <li>Three machines: separate video-server (for timeline decoding and file-archive), dedicated video-monitor and Ardour
    Video support in Ardour does <strong>not</strong>:
      <li>allow for more than one video to be loaded at a time.
      <li>provide video editing capabilities

  <h2>Other New Features and UI Changes</h2>
      <li> chain together LV2 plugins that accept and output MIDI data
      <li> OSC access to send gain parameters (via
        <code>/ardour/route/send/gainabs rid sid gain</code> and
        <code>/ardour/route/send/gaindb rid sid gaindB</code>)
      <li> window management (layering and related issues) overhauled to work better on both platforms and with more window managers
      <li> horizontal scrolling of the timeline is now done with shift-wheel and track height adjustment is done using alt-wheel (matches OS X conventions)
      <li> German and French translations improved
      <li> Allow a pre-existing selection to override region grouping if the clicked-on region is part of that selection
      <li> Plugin editing tweaked:
          <li>Always show plugin's own UI (if available) on double-click
          <li>Alt+double-click -> show 'generic controls' (GUI built by Ardour)
          <li>Context-menu offers both choices.
          <li>Use Tooltip for to make it discoverable.

  <h2>Bug Fixes</h2>
      <li> some licenses fixes in source code files
      <li> properly handle closing of various file descriptors, to fix issues with LinuxDSP plugins and xjadeo
      <li> fix AudioUnit GUI window sizing
      <li> improve relationship between ArdourDialog and Splash on OS X
      <li> hack up AU GUI support to handle AUSampler resizing better. 
      <li> fix operation of right-click on selected MIDI note to bring up the note editor. this is still not really right long term, but it is better than displaying the channel selector
      <li> fix crashes and session file corruption caused by not zeroing text buffers passed to VST plugins (from Mixbus)
      <li> fix crash on export if no master bus is present in the session
      <li> On OS X, use "hw.physicalcpu" to get a more accurate CPU count (the previously used "hw.ncpu" count includes hyperthreading cpus)
      <li> Text in warning window for memory limit not displayed in full.
      <li> fix jack session filename (colons are invalid)
      <li> when using a MIDI keyboard for step entry of MIDI data, use the note length set in the step entry dialog
      <li> Remove special handling of session range in export. Fixes things when the session range is renamed.
      <li> Fix loading of old sessions' previously-used export timespans
      <li> Various LV2 plugin handling fixes
          <li>skip LV2 ports on GUI according to port-properties: notOnGUI and reportsLatency
          <li>honor LV2 rsz:minimumSize for Atom Event buffers
          <li>properly clean up LV2 world
          <li>lilv_port_get() for LV bufsize query requires new lilv
          <li>lilv-backwards compatible min buffer-size implementation
      <li> fix memory leaks and compiler warnings in LXVST code
      <li> fix an unusual problem in some LinuxVST plugins by disabling symbol export
      <li> when a track has audio and MIDI output, display an audio fader rather than a MIDI fader
        (this is a display change only - the fader has effect on all MIDI and audio data
        passing though it regardless of the type of fader shown)
      <li> prepare font-styling meter labels
      <li> decrease size and weight of midi-velocity - make '127' fit,...
      <li> use correct quoting in OS X startup script (allows passing of arguments on the command line)
      <li> add test for writability of /usr/local/lib in OS X startup script (notifies user about an issue created by Audacity)
      <li> save and restore Generic MIDI threshold/smoothing value
      <li> fix crash when using internal edit mouse modes to drag a non-MIDI region

    Robin Gareus, Adrian Knoth, John Oliver, Sakari Bergen, Colin Fletcher, Paul Davis
    Translation work by: Robin Gloster (de) and jpeg129 (fr)

Amazing! What video file types are supported?


I envy you Linux users…

This is fantastic, thanks so much to everybody that worked on it :slight_smile:

this is fantastic news!!! :slight_smile:

thats the cool factor i was looking for… cheers

A really exciting update, thanks “uber-developer” Gareus, and all other contributors!

On my copy of 3.2 (built from revision 3.2-upstream) MIDI smoothing values aren’t being saved. Is there a special way I need to make them be saved and restored, or should I report a bug?

this is already reported as a bug. i tested my fix for this, and it was saved.

@Paul great that it’s already solved!

@samtuke: the bad news is that it was fixed before 3.2 was released …

@Paul In that case I will try creating and saving a new session to see if the bug only affects old saves

awesome news keep it up!

Looking forward to trying this out. Xjadeo has always worked well for me in the past, this integration sounds like it will make the process even easier. Also, this update was a featured article on this morning’s RedShark newsletter email.