Log in
Log in

or
News

Ardour v2.7

Enlarge
Add this product to
  • My former gear
  • My current gear
  • My wishlist
Ardour Ardour
Images
1/1
News Ardour Ardour

The public release of Ardour v2.7 is now available.


For the first time, this includes public versions for Mac OS X (Intel and PPC) as well as the usual source tarball. This release is dominated by dramatic improvements in Mac OS X GUI performance and startup time, but it also contains a lot of significant bug fixes. Ardour also accumulated quite a lot of nice new features since 2.6.1.

Features:

  • Overall dramatic improvements in OS X GUI performance.
  • New action to rotate editor/mixer window stacking.
  • New action to cycle through mouse modes.
  • Plugin windows can now have keyboard focus locked to them.
  • Add missing extensions to exported files based on selected file type.
  • Loop/Range ruler now visible by default.
  • Default crossfade is now –3dB cut.
  • Crossfade presets changed to include –6dB cut and two S-curves (icons sadly not changed yet).
  • New support for Wiimote control (experimental, disabled by default and not currently possible on OS X).
  • Selected tracks are always visible when scrolling through with select-next-track or select-previous-track.
  • Skip non-active and hidden tracks with select-previous-track and select-next-track.
  • Several new tooltips all over the place and better tooltip colors.
  • On OS X, Button2 can be emulated with Ctrl-Option-Button1.
  • Busses are never auto-connected to physical inputs.
  • Unmodified clicking in canvas rulers now sets playhead position, similar to existing behaviour in the “real” rulers. Use Ctrl- (Linux) or Command (OS X)-click/drag for new markers/ranges.
  • Crossfade-editor specific keybindings: space => play xfade, left-arrow => play fade out, ctrl-left-arrow => dry fade out, right-arrow => play fade in, ctrl-right-arrow => dry fade in.
  • Drag-n-Drop from OS X Finder now more reliable but no longer supports MP3 or AAC (will be reverted in the future).
  • Start position and Sync position clocks added popup region editor.
  • Better stay-on-top behaviour for certain windows.
  • LV2 port notification fix for GUI updating.
  • New German translation.
  • New post-export nag screen.
  • Per-track OSC control of solo/mute/rec-enable and gain.

Fixes:

  • Removed suggestion that users can save while disconnected from JACK.
  • Corrected reversed handling of “show-editor-mixer” state on startup.
  • Fixed crasher caused by changing gain with transport stopped & panner bypassed.
  • Correct reverse logic for making h/w monitoring available given h/w capabilities.
  • Fix confusing relabelling of plugin bypass button.
  • Prevent double registration of ALSA sequencer ports.
  • Correctly initialize JACK timeout parameter when starting JACK.
  • Ignore triple-clicks on mute/solo/rec-enable button.
  • Momentary solo/mute now works.
  • Fix serious error when calculating interpolated Curve values (will cause tiny, almost certainly undetectable changes in automation and fade curves, but may also remove clicks).
  • Fix quoting in TOC files wrap PBD::Thread… signals in a mutex to avoid crashing during startup as multiple threads “emit” the signal.
  • Make comboboxes a little bigger on X11.
  • B|B|T clocks measuring duration now use zero-based values.
  • New regions created by AudioFilters (Reverse/TimeFX/Transpose) inherit all relevant settings of their ancestor.
  • Fix for incorrect reading of fade out curve under a few circumstances.
  • Catch exceptions while loading AudioUnits.
  • Correct some glitches with playhead motion when looping/reversing.
  • Fix failure when opening a session by double-clicking the session file icon (OS X).
  • Fix loss of “current dialog” tracking when exiting a dialog via a button (could cause crash on next Ctrl-w).
  • Detect no-installed-JACK on OS X to avoid silent crashes for new users.


Development


  • GTK/OSX patch now in SVN.
  • Check build host for broken mutex-based glib atomic ops.
  • Two versions of clearlooks now in SVN – older, for X11 (crisp!), and newer for OS X (faster!).
Be the first to post a comment about this news item

    Viewers of this article also read...

    cookies
    We are using cookies!

    Yes, Audiofanzine is using cookies. Since the last thing that we want is disturbing your diet with too much fat or too much sugar, you'll be glad to learn that we made them ourselves with fresh, organic and fair ingredients, and with a perfect nutritional balance. What this means is that the data we store in them is used to enhance your use of our website as well as improve your user experience on our pages and show you personalised ads (learn more). To configure your cookie preferences, click here.

    We did not wait for a law to make us respect our members and visitors' privacy. The cookies that we use are only meant to improve your experience on our website.

    Our cookies
    Cookies not subject to consent
    These are cookies that guarantee the proper functioning of Audiofanzine and allow its optimization. The website cannot function properly without these cookies. Example: cookies that help you stay logged in from page to page or that help customizing your usage of the website (dark mode or filters).
    Audience analysis (Google Analytics)
    We are using Google Analytics in order to better understand the use that our visitors make of our website in an attempt to improve it.
    Advertising (Google Ads)
    This information allows us to show you personalized advertisements thanks to which Audiofanzine is financed. By unchecking this box you will still have advertisements but they may be less interesting :) We are using Google Ad Manager to display part of our ads, or tools integrated to our own CMS for the rest. We are likely to display advertisements from our own platform, from Google Advertising Products or from Adform.
    Marketing (Meta Pixel)

    On our websites, we use the Meta Pixel. The Meta Pixel is a remarketing pixel implemented on our websites that allows us to target you directly via the Meta Network by serving ads to visitors of our websites when they visit the social networks Facebook and Instagram. The meta pixel are code snippets which are able to identify your browser type via the browser ID - the individual fingerprint of your browser - and to recognise that you have visited our websites and what exactly you have looked at on our websites. When you visit our websites, the pixel establishes a direct connection to Meta's servers. Meta is able to identify you by your browser ID, as this is linked to other data about you stored by Meta on your Facebook or Instagram user account. Meta then delivers individualised ads from us on Facebook or on Instagram that are tailored to your needs.

    We ourselves are not in a position to identify you personally via the meta pixel, as apart from your browser ID no other data is stored with us via the pixel.

    For more information about the Meta Pixel, the details of data processing via this service and Meta's privacy policy, please visit Meta Privacy Policy - How Meta collects and uses user data for Facebook and Meta Privacy Policy - How Meta collects and uses user data for Instagram.

    Meta Platforms Ireland Ltd. is a subsidiary of Meta Platforms, Inc. based in the USA. It cannot be ruled out that your data collected by Facebook will also be transmitted to the USA.


    We did not wait for a law to make us respect our members and visitors' privacy. The cookies that we use are only meant to improve your experience on our website.

    Our cookies
    Cookies not subject to consent

    These are cookies that guarantee the proper functioning of Audiofanzine. The website cannot function properly without these cookies. Examples: cookies that help you stay logged in from page to page or that help customizing your usage of the website (dark mode or filters).

    Audience analysis (Google Analytics)

    We are using Google Analytics in order to better understand the use that our visitors make of our website in an attempt to improve it. When this parameter is activated, no personal information is sent to Google and the IP addresses are anonymized.

    Advertising (Google Ads)

    This information allows us to show you personalized advertisements thanks to which Audiofanzine is financed. By unchecking this box you will still have advertisements but they may be less interesting :) We are using Google Ad Manager to display part of our ads, or tools integrated to our own CMS for the rest. We are likely to display advertisements from our own platform, from Google Advertising Products or from Adform.

    Marketing (Meta Pixel)

    On our websites, we use the Meta Pixel. The Meta Pixel is a remarketing pixel implemented on our websites that allows us to target you directly via the Meta Network by serving ads to visitors of our websites when they visit the social networks Facebook and Instagram. The meta pixel are code snippets which are able to identify your browser type via the browser ID - the individual fingerprint of your browser - and to recognise that you have visited our websites and what exactly you have looked at on our websites. When you visit our websites, the pixel establishes a direct connection to Meta's servers. Meta is able to identify you by your browser ID, as this is linked to other data about you stored by Meta on your Facebook or Instagram user account. Meta then delivers individualised ads from us on Facebook or on Instagram that are tailored to your needs.

    We ourselves are not in a position to identify you personally via the meta pixel, as apart from your browser ID no other data is stored with us via the pixel.

    For more information about the Meta Pixel, the details of data processing via this service and Meta's privacy policy, please visit Meta Privacy Policy - How Meta collects and uses user data for Facebook and Meta Privacy Policy - How Meta collects and uses user data for Instagram.

    Meta Platforms Ireland Ltd. is a subsidiary of Meta Platforms, Inc. based in the USA. It cannot be ruled out that your data collected by Facebook will also be transmitted to the USA.


    You can find more details on data protection in our privacy policy.
    You can also find information about how Google uses personal data by following this link.