feed2list
feed2list wird zum 01.01.2019 seinen Dienst einstellen
Suchen und blättern in Linux · Opensource
   Suchtreffer: 92
website Blog - Ardour
Topics in the 'Blog' category Articles from the blog
feed text Ardour Web Forum Migration
Mon, 01 Oct 2018 14:16:08 +0000

@x42 wrote:

12 years ago the Ardour Forum was launched and there have been little to none infrastructure updates since. 12 years of Ardour online community. 12 years of web-evolution!

Brace yourself, because we have opted to perform a long overdue modernization and migrate the forum to discourse.org!

The most significant changes compared the previous forum are: support for dynamic notifications, a flat front-page with context and the page-less layout. Just keep scrolling down.

That barely scratches the surface though. There is plenty to discover and we hope you’ll feel right at home here with us!

However, we will leave you with some nostalgia from time to time:

  • User-accounts remain at https://community.ardour.org. This includes
    • Sign-on and password management
    • Download purchases, donation and subscriptions

All forum posts and comments have been migrated. You can even find the very first post of the then "The New Ardour Website" from early 2006 here :slight_smile:

There are certainly some loose-ends to be tied up to complete the migration. If you find some dangling links, or please don’t hesitate to let us know in the comments. You’re also more than welcome to leave feedback about this site, its organization and how we could improve it in the Feedback Section.

Let the discourse begin!

Posts: 19

Participants: 12

Read full topic


text Ardour Development Update
Fri, 01 Jun 2018 18:20:15 +0000

@paul wrote:

It's been a long time since the last release of Ardour, and there's still no schedule or even vague sense of when the next release might appear. I (Paul) felt that our users, and particularly our subscribers, deserved some information about what is and has been going on with development over the last 8 months. I had promised to do this back in December, and it is now long overdue.

The core developers of Ardour (myself and Robin Gareus, with help from Ben Loftis) have been involved in some major architectural redesigns of Ardour's internals. We didn't really plan on this as a distinct goal on its own, but rather these changes emerged out of the desire/need to add new functionality and fix fundamental issues with the program. In most cases, these changes don't have any particularly noticeable effect on the GUI (Grid/Snap changes are an exception). Nevertheless, they lay the ground work for more interesting and more visible changes, as well as new functionality in the future.

First, let me mention the long term "big picture" goals that we're working towards:

  • Improving workflow for all common operations, and many less common ones.
  • Integrating MIDI and audio as seamlessly as possible, so that users rarely need to consider the type of data they are working with. We'd like to extend this to automation data too.
  • Providing fast pathways to getting groove-centric sessions set up, with pattern generators and other related tools.
  • More use of "flexible" time aka timestretching throughout the editing process, if desired.
  • Fixing bugs.
  • Reducing complexity and increasing discoverability.

So far, we've done substantial work in these areas of Ardour's architecture:

Cue Monitoring

Ardour 5.12 allows you to monitor (listen) to either the input signal to a track, or the existing material on disk for the track, but not both. This is generally acceptable when working with audio, because overdubbing works the way most people expect it to. But when working with MIDI, it is less than ideal - many users expect to be able to use a MIDI controller (e.g. a keyboard) and generate new sound from the synthesizer in a track at the same time as listening to whatever has already been recorded for that track. Being able to listen to both the input signal and the existing recorded material is often called "cue monitoring", and this is now possible in the development code.

"Wet" Recording

As part of the changes for cue monitoring, the work involved in playback from disk and recording disk has been split into two "processors", which are the basic type of objects you can see in Ardour's mixer signal flow. Processors you already know include the gain fader, plugins, sends, inserts etc. Now, recording and playback are just processors too, which means that they can be reordered in the signal flow. This allows you to (optionally) record after one or more plugins, often referred to as a "wet recording" (dry recording means without any FX). We think that some users will find this side-effect of splitting up recording and playback to be quite powerful in some settings.

Varispeed

Splitting playback and recording into two processors per track led us to re-examine Ardour's mechanism for varispeed playback. This is used both by the shuttle control, and also when syncing to an external positional reference such as LTC or MTC. We decided to move this functionality into a total different "level" of the program internally, so that the core of the code no longer has to pay any attention to it at all. Varispeeding is applied to all data flowing in and out of the program, totally transparently to the rest of the program. This redesign makes a few new tricks possible, such as varispeed recording, and having MIDI synth output pitch-shift alongside disk-based audio. The quality of the resampling engine has gone up dramatically too, since we have switched from simple cubic interpolation to using Fons Adriansen's excellent zita-resample code.

Latency

Ardour has had plugin latency compensation dating back to almost the first release of the program. But that compensation was limited to tracks (not busses), and didn't cover other cases where latency is introduced into signal flow. Robin (Dr. Gareus to the rest of us) redesigned almost every aspect of the core of Ardour's processing code to now provide latency compensation everywhere. This isn't like some DAWs in which "more things now work". Latency is now compensated for no matter where it happens, completely and always.

Transport Control

The changes to support full latency compensation revealed some conceptual and implementation issues with the way transport control operates inside the code. Looping and starting/stopping become much more complex when taking latency fully into account. Fixing this has meant a redesign in which every processor in a track or bus is told precisely which part of the timeline it is expected to be working on, among several other deep and difficult changes.

Time

There is a lot of work to do on Ardour's MIDI workflow. But before that can happen, there are several subtle errors that are caused by the way released versions of Ardour have handled musical time. When you edit and move a MIDI note forward by a quarter note, that process would actually involve several conversions back and forth between time measured in samples and time measured in musical units, and the result is (often) small errors accumulating that lead to the note beginning and end being "wrong".

Changing this has been a mammoth task. Everything that has a position and/or a duration within the program - a rather common feature in an application partly there to place and edit things along a timeline - has needed to be tweaked to use the correct time units at the right time.

Tempo

One of the goals of the work on representing time has been to move towards more flexible tempo maps, specifically ones that do two things:

  • not regard musical (Bar|Beat|Tick) times as deterministic
  • flexibly follow human performance more easily

Users should be able to put the musical time 1|1|0 wherever they need to, and in fact may want to have more than one such time in a given session. They may also want to adjust where the 12th bar starts, or any other bar for that matter. There may be rubato sections where musical time (counting) effectively stops. We want to be able to offer automated analysis and human editing that can easily conform a tempo map to a human performance, so that later tempo map driven editing will fit it precisely.

This work has been ... is ... challenging.

Grid vs. Snap

In the released versions of Ardour, we noticed that users are often confused by the Grid. Sometimes the Grid appears to do nothing, and sometimes it does something unexpected. Furthermore, it required a lot of switching between grid modes: if you were snapping to 16th notes, then you had to switch the grid mode if you wanted to snap to a marker.

The "Grid" has been separated into 2 separate features: Snap and Grid.

When "Snap" is enabled, any mouse operation (like splitting or dragging a region) will be "resolved" to a snap target, if one is near. Snap targets can be any of: the nearest marker, the nearest region start/end, or the Grid. It is now possible to select multiple snap targets simultaneously. So, for example, you can choose to snap to both Markers and the Grid.

All snapping is now "magnetic"; and you can no longer snap to a target that is off-screen.

Finally, there is a new "snapped cursor" ( a blue line ) which indicates where the next mouse action will occur, if it isn’t directly under the mouse. This is particularly useful when splitting regions: the blue line indicates where the split will occur, if a snap is in effect. In the prior operation, a split could happen quite far from the mouse, if a snap target was applied.

When a "Grid" is selected, then vertical lines will appear on the editor canvas, extending down from the timeline ruler at the top of the editor. If Snap to Grid is enabled, then these lines will indicate the possible snap locations for your mouse actions.

In the released versions of Ardour, there is no connection between the zoom level in the editor and the grid. If the snap grid is set to Beats, then it may be quite unclear what snap is actually doing. If you were zoomed out, then the visual indication of individual beats might disappear, and yet you were still snapping to them. If you were zoomed in too close, then you might snap to a beat that is offscreen (and therefore invisible)

We've reworked this so that the grid always takes the visual zoom level into account, and the visual grid lines will be generated to sensibly match your current zoom level. For example: if you have a grid set to 16ths, but you are zoomed far out, then lines will only appear on bar lines. Inversely, if you've selected "bars" for the grid, but you zoom in very close, we won't draw the quarter- or 16th-note grid lines, because you didn’t request grid marks at that level.

All of these changes should result in a more consistent, "what you see is what you get" operation for Grid and Snap.

Posts: 30

Participants: 17

Read full topic


text Long Interview with Ardour Founder Paul Davis
Sat, 28 Apr 2018 23:55:01 +0000

@paul wrote:

Ardour founder Paul Davis sat down recently with Darwin Grosse of Cycling 74 (Max) to talk about the program, his own personal history, audio technology, software platforms and a whole lot more besides. It's roughly an hour long, and Paul reports that he was unusually satisfied with what he managed to say during this chat.

You can find it at Darwin's Art & Music & Technology podcast: https://artmusictech.libsyn.com/podcast-214-paul-davis-ardour

Quite possibly worth taking a listen to Darwin's chat with Andrew Belt of VCVRack too ... full list of episodes here: https://artmusictech.libsyn.com/

Posts: 3

Participants: 3

Read full topic


text Ardour and Money, early 2018 edition
Mon, 01 Jan 2018 21:59:22 +0000

@paul wrote:

As 2018 gets underway, it seems like the right time for an updated report on the financial state of the Ardour project. I still occasionally see people referencing articles from several years that give a misleading idea on how things work these days, and it would be good to put some current and accurate information out there.

The TL;DR Summary

Ardour's finances are good. The project produces a remarkable revenue stream for an open source project, though small by comparison with similar proprietary projects. More than 3000 subscribers mean that the month-to-month stable income is enough to keep Ardour's lead developer fully employed, and monthly surpluses from donations and single-paid-for copies also have enabled the project to distribute significant sums of money to other active developers.

A Brief Recap/History of Ardour & Money

When I started Ardour, I never had any intention from making money from it. However, changes in my own personal circumstances meant that by about 2007, I needed to earn an income again, and in 2008 that started thanks to the sponsorship of Solid State Logic. That ended less than a year later, and in 2009 I had a lot of valuable suggestions from Ardour users about how to get the program itself to generate a revenue stream. The original goal was to just ensure that I could continue to work full time on Ardour rather than seeking other employment. Inspired by Radiohead's release of "In Rainbows", I adopted a "pay tunnel" approach to Ardour, trying to convince as many people as possible to pay for the service of getting a ready-to-run, supported version of the program. I've also been the beneficiary of the ongoing collaboration with Harrison, whose Mixbus program supports, invigorates, improves and contributes to Ardour on a continuing basis.

It has been remarkably successful when viewed through the lens of open source software. We probably generate more actual revenue than almost all but a handful of open source projects. However, when compared with even a small proprietary project, our financial story is lot more modest. Cockos Inc., which makes Reaper and was founded by a multi-millionaire, has in the past had 3 full time employees and typically paid 2-3 contractors at any given time. We are still a long way from even that kind of success.

Subscriptions, Subscriptions and more Subscriptions

When the project first started experimenting with subscriptions, one of our early users suggested starting a campaign called "The 600". The idea was to try to get us to 600 subscribers each at US$10 per month, which would provide US$6000/month of stable income.

The campaign never got launched. Instead, via some sort of incredible magic, we've ended up with more than 3000 subscribers (most at lower monthly amounts) generating around US$8500 per month of stable income. The churn on these subscriptions is high - many start and stop well before a year is over. But the overall level remains about the same (and climbs slowly) because for every person who cancels, someone else starts.

A massive thank you to ALL our subscribers who make my life and work possible, and who make the lives of some of our other developers a bit nicer/easier/more worthwhile. We couldn't do this without you! Thanks for everything!

Numbers

In 2017, Ardour itself generated US$130,565 (this does not include several thousand dollars of PayPal transaction fees). Of that, Paul collected his base salary of US$74,400 plus US$11,165 of the surplus income. Paul paid the operating costs of the Ardour web site (about US$1200 a year) from his income.

The remaining surplus of about US$45,000 was distributed to other active developers, principally Robin Gareus but also including Tim Mayberry, Nick Mainsbridge, Len Ovens and others.

Changes For 2018 and Beyond

The last time I set a salary goal for myself was 2009 (US$6200/month). Simple inflation in the USA since that time would require that to be US$7128 in 2018. In addition, for the 14 years prior to 2015, my wife and I survived without any health insurance; in 2015, following the arrival of the ACA ("Obamacare") in the USA, we started paying for health insurance. In 2018, our monthly premiums for that are US$971 (lest anyone think that this sounds good, that policy comes with a US$7300 deductible per person, meaning that the insurance doesn't really cover anything except terrible accidents and chronic or serious disease). I never factored this in my original salary thoughts.

To reflect these two realities, starting in 2018, I will bump my salary up to US$8100/month. This corresponds to an annual income of US$97200, but without any employer contributions to health insurance or retirement. This is reasonably modest by comparison with median US salaries for a "Senior Software Engineer" or "Lead Software Engineer", which are in the range of US$110,000 to US$130,000 (not counting those employer contributions, which add many $1000's more in value).

Based on recent monthly income levels for the project, this will still leave around US$3000 to be distributed to other active developers. Because of his extraordinary productivity, all-round brilliance and unstoppable energy, a substantial chunk of that is likely to continue to flow toward Robin Gareus for the foreseeable future. Robin also works as a contractor for Harrison Consoles, with his efforts serving as a key bridge between Ardour and Mixbus, ensuring that the two projects remain tightly integrated and both benefitting as much as possible from new ideas and improvements.

Thinking Ahead By Thinking Behind

I mentioned above, I didn't start Ardour with the idea of making money from it. I was a stay-at-home parent at the time, and wasn't giving a lot of thought to my long term future financial situation. 18 years later, my family situation is very different, and I'm notably older myself. I stopped regular paid work about 22 years ago, and as a result haven't been involved in a retirement plan since then. For many years, I wasn't earning any income at all, which meant I also wasn't a participant in Social Security (which provides an extremely minimal retirement income in the USA). Because of all this, and because of Ardour's relative success, I do now need to look at the project as the most likely source of any retirement stability that I may have (retirement is still a decade away for me, if I ever actually retire!).

In thinking about all this, I've come to the following rationalization of how I intend to personally interact with Ardour's finances over the coming years. Back in the early days, I spent about 8 years working on the program without any significant income from it. Taking a rather modest salary figure for that period of US$70,000 per year (again, without any employer contributions to health or retirement), that would total US$560,000 of income. If and when I ever collect that much from the surplus income, I'll stop taking any part of the surplus and will consider the project to truly and fully belong to ... well, I don't know, but not me any more, at least not in the sense I do now. It seems unlikely that this day will ever come, but this rationalization allows me to feel comfortable about my relationship to the project's financial situation.

To the extent that Ardour manages to continue to generate revenue in the future, it will continue to be distributed in accordance with the general principles I've described above.

Bigger and Better?

Ultimately it would be fantastic if the revenue that Ardour generates grows enough to allow us to hire another full-time (or maybe mostly-time) developer. However, there's little interest among the current developers for spending time on "marketing strategies" to try to explicitly work on this goal. We'd rather work on the software itself, and rely for now on the continued organic growth that has bought us this far. Of course, if we hear of any obviously great ideas to get us to this sort of goal, we will consider that.

Posts: 31

Participants: 22

Read full topic


text Almost Ready to Leave Home
Tue, 26 Dec 2017 23:00:14 +0000

@paul wrote:

Ardour began its life 18 years ago, in late December 1999. The story has been told many times in many different places, but the gist of it is that I wanted a program something like ProTools that would run on Linux, and none existed. I decided to write one. I had little idea what would be involved, of course. Which was probably for the best, otherwise I would likely not have started.

Recently, while clearing out old paperwork from my office, I found myself reading some old issues (2001-2003) of the generally excellent magazine, Sound on Sound.They give a pretty good idea of the state of DAW technology at that time as well as other stuff like sampling, sequencing and so forth, which at that time were somewhat separate from the core functionality being offered by DAWs.

It occured to me that Ardour has actually managed to reach the goals I set out back in 2000. It is a capable DAW capable of doing the vast majority of the things people were doing with this kind of program around the start of a new millenium. Not suprisingly, that's still a substantive part of what people are doing now with DAWs in general even at the end of 2017.

There are some things that we were actually doing long before other DAWs. Anywhere-to-anywhere routing is something we more or less pioneered, and has now become common. A truly flexible mixer architecture (whose flexibility is sometimes its downfall). Support for different solo models. Even today press releases for new versions of several proprietary DAWs will regularly mention things that Ardour has done for more than a decade. Oh well - the point is not to gloat over this kind of thing, since there are plenty of things that Ardour doesn't do. The point is to note that the initial goals have largely been satisfied.

In fact, they've been more than satisfied, because Ardour also became a truly multi-platform project (running on Linux, MacOS (nee OS X) and Windows. It also gained some level of support for MIDI workflow, not to mention the video timeline.

Ardour has also served as the basis for two or three "commercial" projects - Harrison Mixbus, Waves Tracks Live (and the likely short-lived Radar Session software). We've somehow developed a way to raise significant (though not substantial) income every month, despite the program remaining under the GPL license. Nobody needs to pay for Ardour, but lots and lots of people choose to do so. These are no small accomplishments.

There were other, somewhat meta-goals too. I wanted Ardour to serve as an example (not a template or a toolbox) for other people to learn how to write a DAW. I doubted that we'd get everything right, but that at least compared to the situation in 1999, when there was no open source DAW suitable for use as a ProTools-like system, Ardour has truly fulfilled this idea. I suspect that Justin Frankel didn't take a lot of inspiration from Ardour's source code when he started writing Reaper, but it was fun having him on our IRC channels for a while as he got started with that project. Ardour has also attracted the involvement of nearly 50 skilled developers over the years, a dozen or so of whom have played major roles in the design and implementation of the program. A couple have even gone on full time paid jobs working on audio technology.

It wouldn't be completely unreasonable, after 18 years of development and having reached the level of features that Ardour now has, to consider it done, at least in some senses. It is true that we have a huge list of 2000+ bugs that remain open in our bug tracker. Our MIDI workflow has lots to complain about, and there are some glaring software design errors that users can see if they insist on trying some not-that-crazy stuff (e.g. working on MIDI versions of Phillip Glass pieces).

Still - people use it. Somebody starts Ardour up somewhere in the world at least every 3 minutes or so. Some of our users rave about in comparison to other DAWs. You can make albums with Ardour. Record live gigs. Basically do all the things I imagined back in December 1999.

But are we done? Absolutely not. In my next post, I'll outline some of the directions that I personally imagine Ardour going in during 2018 and beyond.

Posts: 12

Participants: 11

Read full topic


text What's Going On With Ardour?
Mon, 25 Dec 2017 00:36:14 +0000

@paul wrote:

It’s Christmas 2017, and many people in the Ardour community and beyond may be wondering what is happening with Ardour right now. It’s been several months since our last release, and there’s no word on what is going on.

Between now and the (Gregorian) New Year, I’ll be posting 3 articles about where Ardour has been, where we are heading and the financial aspects of the project.

For now, I will just note that we’re mostly focused on really substantive (wide-ranging, deep and difficult) internal architectural changes that will (over time) make a lot of other stuff possible. There’s absolutely no timeline for the next release at this point, and the work is hard enough that in general we’re trying not to get diverted by bug reports and small feature requests.

Stay tuned for a history and a glimpse of where 2018 might take Ardour …

Posts: 1

Participants: 1

Read full topic


text Ardour 5.12 released
Fri, 15 Sep 2017 22:16:40 +0000

@paul wrote:

  

Ardour 5.12 is now available.

Although when Ardour 5.11 was released, we expected a significant gap until 6.0 will be announced, enough notable features and fixes accumulated that it seemed better for us to push out a 5.12 release before we embark on the major code changes that will mark the real start of the development process for 6.0.

Much of the work in this release was sponsored by Harrison Consoles.

Two of the most notable new features are the improvements in functionality to the new session and new track/bus dialogs, which now offer much easier and more powerful ways to use templates. These include dynamic "track wizard" templates that allow you to interactively setup sessions and/or groups of new track/busses very quickly and very easily. This builds on the new template manager dialog introduced in 5.11, and a new less obvious feature: the ability to create dynamic templates with Lua scripts.

Also notable is the new patch selection dialog for MIDI tracks/instruments, which provides an easy and convenient way to preview patches in software and hardware instruments. Naturally, it integrates fully with Ardour's support for MIDNAM (patch definition files), so you will named programs/patches for both General MIDI synths and those with MIDNAM files.

Download

New Features

  • Improvements to the template manager dialog.
  • Lua templates for tracks and sessions can now be created/scripted.
  • New session dialog functionality improved, with new templates and track wizards.
  • New track dialog functionality improved, with new templates and track wizards.
  • Expose Lua bindings for VCA create/delete/assign/unassign.
  • New patch selector dialog for MIDI tracks. This can be accessed by right clicking in the track header area.

  • Ardour's generic GUI for instrument plugins now includes a keyboard to allow auditioning the plugin settings.

  • Support for a new LV2 extension to notify the host about MIDI bank/program changes (e.g. driven by the plugin's own GUI).
  • Faderport 8: double-click on select button resets gain to 0dB.
  • Display playback-only devices when using JACK.

General Fixes and Improvements

  • Fix MIDI quantization when not using US English.
  • Fix selection of quantization note-end grid size.
  • Catch exceptions thrown from Lua scripts.
  • Fix handling of MIDI channels in the Transform dialog.
  • Improve the heuristic used to display track/bus I/O connections in a compact form, as well a connection menus.
  • Clicks on I/O menus now always connect, rather than toggle connected status.
  • OSC: gracefully handle the user sending the wrong number of parameters.
  • OSC: changing jog mode no longer stops transport unless started by scrub/shuttle.
  • Secondary clock visibility is now a global preference rather than a per-session setting.
  • The editor's summary view is now constrained to the extent of actual regions, rather than the session extent, by default. This can be reset from a right-click on the summary.
  • New configuration setting for playhead auto-scroll speed. If you want to scroll quickly, it is preferred to zoom out first, then scroll.
  • New configuraton setting to define how much zooming will be easily allowed beyond the extents of actual regions in the session.
  • Generic plugin GUI: fix sizing and layout for automation state controls in plugins with many controls.
  • Increase priority of the thread involved in automation recording. This fixes an issue with sparse automation recording when the CPU is busy.
  • Update the included version of NSS (a secure networking library), to provide some features required by some plugins.
  • Fix the way MIDI filenames are "bumped" during snapshots and playlist copying.
  • Fix crash bug in Ableton Push 2 support, introduced in a recent version.
  • Fix various tooltips to avoid problems with special characters in their text.
  • Catch some exceptions during session loading.
  • Relax some restrictions imposed by the Lua sandbox (for scripts).

Contributors

Robin Gareus, Ben Loftis, Johannes Mueller, John Emmas, Len Ovens, Paul Davis, Julien Rivaud, Stefan Müller-Klieser

Posts: 6

Participants: 5

Read full topic


text Ardour 5.11 released
Wed, 16 Aug 2017 18:32:54 +0000

@paul wrote:

  

We are pleased to announce the availability of Ardour 5.11. Like 5.10, this is primarily a bug-fix release, though it also includes VCA automation graphical editing, a new template management dialog and various other useful new features.

Download

New Features

  • VCA automation can now be graphically edited.
  • VCAs can now be selected (e.g. from control surfaces).
  • Allow VCA renaming in the editor window.
  • Bindable buttons for VCA solo and mute.
  • Add select-all-tracks shortcut in the mixer window.
  • Template management dialog (both session and track templates).
  • Allow control surfaces to hide/show plugin GUIs.
  • Realtime export now allows listening to channels being exported.
  • Non-layered MIDI recording now works (MIDI regions will be trimmed at the end of recording to avoid overlaps).
  • Add an LTC generator to the Dummy backend.
  • Update colors for the "Caineville" theme.
  • Expose Off/Play states for MIDI CC "automation".
  • Allow touch automation to be done via Ardour's own knobs (e.g. trim control).

General Fixes and Improvements

  • Fixes for consistent selection and track/bus ordering.
  • Improve display of dB values.
  • Improvements when dragging control points for log-scale or relative parameters.
  • Lookup VST parameter default values once only, at the correct time.
  • Major code cleanup for locale (internationalization) handling.
  • Create a deep-copy of MIDI sources when saving snapshots.
  • Allow saving state even when audio/MIDI engine is not running.
  • Substantial reworking of waveview rendering code.
  • More differentiation of error messages during startup.
  • Fix for a-fluid handling of out-of-memory conditions.
  • Avoid display/use of "mnemonics" in menu items (shortcuts continue to work as usual).
  • Correct an issue when sending from a source with less channels than the destination.
  • Don't invert azimuth & elevation display value for some panning configurations.
  • Fix undo being invoked from a non-GUI thread.
  • Fix crash when rapidly switching snapshots.
  • Show region name correctly in a context menu.
  • Reintroduce a command to toggle editor/mixer windows when they are tabbed.
  • Retain plugins order for copy/cut/paste + Drag-n-Drop.
  • Correctly adjust gain when selection spans multiple track/bus groups.
  • Honor groups when selecting in the mixer.
  • Convert summary display into a horizontal scrollbar (no more y-axis sensitivity for scrolling; now zooms).
  • Fix loading bundle definitions.
  • Changing type of track/bus in the add track/bus dialog no longer resets the name, if edited.
  • Take automation lanes into account when changing "visible track count".
  • Make it impossible to zoom to ridiculously zoomed-out scales.
  • Fix crash when renaming a track to an invalid name.
  • Increase the range of the a-comp stereo release time.
  • Forward-to-grid and Backward-to-grid now snaps even when in magnetic mode.
  • Correct note length setting and display in the note edit dialog.
  • Time info box updates its length display correctly across a tempo change.
  • Indicate region positional lock style with various UTF-8 glyphs (Beamed 1/8th notes => music position lock).
  • Only add a new tempo or meter on a click with the primary modifier pressed (avoid confusion with a tempo-change drag).
  • Disable tempo end drag for meter-locked tempi.
  • Cropping a single region to time selection works for multiple ranges.
  • Setting a tempo to 'Continue' via right click puts it in a permanent state of continuing the previous section's end tempo (basically what 'Lock Continue' should have been). This can be disabled (unlocked) by selecting 'Don't Continue'.
  • Reorganise menu to separate position lock style from more commonly used functions.
  • Main Menu: some re-organization of session- and global-centric windows.
  • Track/Bus mute automation now works as expected.
  • Many improvements to plugin in-line displays.
  • Fix various issues when changing automation state while rolling.
  • Make it possible to select regions at zero when the grid is set to Region Bounds.
  • Fix a bug with LTC chasing when using small buffer sizes and a large initial offset.
  • Ask user about saving when using Save As or Snapshot & Switch.
  • Fix the cursor in some TextEntry popups.
  • Show a-comp's makeup gain and gain reduction in it's inline display.
  • Many crashes at exit or close-session fixed.
  • Prevent duplicate playlist names while renaming.
  • Session > New ... cancel : now retains current session, if any.
  • Use Mach real time priority in process threads.
  • Use real-time safe MIDI buffer allocation for ALSA, CoreAudio and PortAudio (Windows) MIDI backends.
  • Fix for "MIDI Input follows Selection" (breakage introduced during 5.10 development).
  • Improve clock font used on OS X.
  • Fix --samplerate option for ardour-export standalone tool.
  • Add options for bit-depth and BWF format to ardour-export tool.
  • Ensure that broadcast data (BWF) is complaint with EBU specifications.
  • Save sample-rate for sessions created with templates.
  • Fix LV2 preset path on Windows.
  • Do not disable MIDI CC "automation" after clearing all data for a given CC.
  • Only button 1 (typically left) will now add new MIDI CC events on click.

Lua

  • Expose editor vertical zoom.
  • Expose region list.
  • Expose clone/copy regions.
  • Expose systemexec.
  • Improve script sandboxing.
  • Provide access to toggle actions.
  • Expose a new Lua message dialog.
  • Support for template scripts.
  • Support for meta-templates for Session setup.

OSC Support and Control

  • Added /*/db_delta for strip, select, master and monitor.
  • bank_up will now accept -1 for bank down so an encoder can bank.
  • GUI improvements - usability.
  • Allow user selectable group use (/use_group 1 or 0).
  • Prevent crashes or hangs in some cases.
  • Send fewer duplicate messages.

FaderPort 8 Support

  • Use 2 lines for Plugin Parameter Names.
  • Expose Plugin Bypass/Enable per plugin.
  • Shift + Select in Plugin Select mode.
  • Bypass button in Plugin Parameter Edit mode.
  • Don't allow toggling strip bypass/enable.
  • Allow selection of plugin presets.
  • Scribble-strip display preferences.
  • Fixes crash when switching snapshots.
  • Display in mixer order.
  • Add plugin GUI display options.
  • Implement "control link" (control operates on currently focused widget in GUI).
  • Fix shutdown sequence.
  • Indicate implicit solo by blinking.

Translation Updates

  • Czech translation update (Pavel Frich).
  • Japanese translation (Hiroki Inagaki).
  • Swedish translation update (Kristoffer Grundström).
  • Russian translation updates (Petr Semiletov, Alexandre Prokoudine).
  • Chinese translation update (Yq Ysy).
  • French translation correction (Léo Andrès).

Contributors

Ben Loftis, Johannes Mueller, John Emmas, Len Ovens, Nick Mainsbridge, Paul Davis, Robin Gareus, Tim Mayberry, Jelle van der Waa, Julien Rivaud, Thomas Brand, nickolas360, cooltehno

Posts: 1

Participants: 1

Read full topic


text Ardour 5.10 released
Thu, 15 Jun 2017 13:40:15 +0000

@paul wrote:

We are pleased to announce the availability of Ardour 5.10. This is primarily a bug-fix release, with several important fixes for recent selection/cut/copy/paste regressions along with fixes for many long standing issues large and small.

This release also sees the arrival of VCA slave automation, along with improvements in overall VCA master/slave behaviour. There are also significant extensions to Ardour's OSC support.

Download  

General Fixes and Improvements

  • (Time) Range selection and copy/cut/paste now works again.
  • Selection and copy/cut/paste for automation tracks now works again.
  • Extend list of reserved track/port names (including translated versions of "Click").
  • Fix another case where potentially illegal track/port names were not checked correctly.
  • Context click on [Marker] > loop range should set loop range.
  • Tweak/fix splash screen management.
  • Update writable status of a Save-as copy of a Session.
  • Add note name parser to convert to midi note number.
  • VST parameter names can now be up to 128 characters long.
  • Remember the state (shown/hidden, attached/detached) of the Monitor section.
  • Ardour's own custom buttons now correctly reflect the initial state of the action they control.
  • Stop crash after deleting a group.
  • Fix double "Tape" in Record Mode drop down when adding new track.
  • Support note name editing in midi list editor.
  • Fix out-of-bounds waveform image rendering.
  • Set Display Name for OSX/macOS.
  • Fix libhid compile with /recent/ libc (GNU_SOURCE).
  • Fix failure to laod old tempo maps.
  • Use correct variable in BasicUI::jump_by_seconds.
  • Tempo sections with a BBT start XML node are never ramped.
  • Sort tempo map after legacy sections have been assigned a pulse.
  • Include ParameterDescriptor in read-only control output.
  • Implement basic AU parameter-printing.
  • Pretty print control-outputs in generic-UI.
  • Always create a deep copy of MIDI regions when copying playlists.
  • Use correct names when setting MidiTrack properties.
  • Use correct property name in generic MIDI surface.
  • Allow export presets for 176.4KHz.
  • When creating a new session after working on one, the "Cancel" button should be a quit button.
  • Duplicate routes start off unsoloed to avoid issues related to upstream / downstream buses.
  • If actively recording, prevent interaction between mouse and audio clock widget(s).
  • Remove "Close" button from import-dialog (prefer WM close button).
  • Import Dialog now behaves now other dialogs/windows when using Escape.
  • Add route dialog now has "Add" and "Add and Close" buttons. "Add" keeps dialog open so user can add multiple templates.
  • Fix recording-region graphics when using count-in.
  • Fix reversed logic in legacy tempo secton detection.
  • Tempo lines display subdivisions correctly over a tempo change.
  • Fix crash when showing plugin-UI in safe-mode.
  • Fix DSP in a-EQ, when parameters change very slowly.
  • Fix playhead behaviour when synced to JACK tranport.
  • When dragging notes, keep the note length correct even if tempo changes across the drag.
  • a-EQ: Tweak knob layout to be less confusing.
  • Make Import the default action in the Import Dialog.
  • Restore the state of the autoplay button in the import dialog.
  • Consistent "cancel/close" button position on the left.
  

Lua

  • Add a file-chooser LuaDialog Widget.
  • Update LuaDialog example script to include File/Folder selection.
  • Add Lua bindings for VCAs and VCAManager.

VCA & Automation

  • Do not crash when removing a VCA master.
  • Fix relative grouped + VCA slaved gain.
  • Fix Monitor Group override.
  • Allow group gain sharing + VCA again.
  • Remember subgroup-bus.

OSC Support and Control

  • Add Automation control to OSC.
  • Faders can select automation mode.
  • Frame work to add automation for more controls
  • Add Touch message for faders.
  • Add fake timeout based touch.
  • GUI settings take effect on first incoming message.
  • Catch case of surface sending fader move before touch.
  • Add optional paging to sends in select.
  • Add option to send /reply instead of #reply (OSC1.0 compat).
  • Select channel plugin support with paging.
  • Allow set_surface and settings GUI to set send and plugin page sizes.

Control Surfaces

  • Improve all control surfaces' handling of track/bus selection changes.
  • Midi map for Alesis QX25.
  • Update FaderPort8: new possible controllable parameters.
  • Mackie Control: Momentarily light buttons when they are used to trigger a defined action. (This is mainly for F-keys)
  • Mackie Control: If a button is not assigned an action, it will not light, hopefully indicating to the user that it is unmapped).
  • Mackie Control: F-keys are reserved only for user-defined actions; no need for explicit handling.
  • Mackie Control: configuration panel should display the profile name when any button action is changed.
  • Mackie Control: Assign some F-keys for default user profile.
  • Mackie Control map the well-known EQ knobs more explicitly, not heuristically.
  • Mackie Control: Fix issue with strip "select" buttons that stayed stuck on.

Translation Updates

  • German (Edgar Aichinger).
  • Russian (Alexander Prokoudine).

Contributors

Ben Loftis, Damien Zammit, Daniel Sheeler, Johannes Mueller, John Emmas, Len Ovens, Nick Mainsbridge, Nils Geisweiller, Paul Davis, Robin Gareus, Tim Mayberry

Posts: 10

Participants: 6

Read full topic


text Ardour 5.9 released
Mon, 15 May 2017 15:54:14 +0000

@paul wrote:

Ardour 5.9 is now available, representing several months of development that spans some new features and many improvements and fixes.

Among other things, some significant optimizations were made to redraw performance on OS X/macOS that may be apparent if you are using Ardour on that platform. There were further improvements to tempo and MIDI related features and lots of small improvements to state serialization. Support for the Presonus Faderport 8 control surface was added (see the manual for some quite thorough documentation).

As usual, there are also dozens or hundreds of other fixes based on continuing feedback from wonderful Ardour users worldwide.

Download  

General Changes and Improvements

  • Prevent adding Master Bus to a Track/Bus group and make group button insensitive.
  • Re/Add send options in the Processor box context menu and an option to allow feedback loop via Aux sends.
  • Improvements to behaviour of Track/Bus/VCA Color Selection dialog.
  • Consistent Color Selection dialogs with customizable color palette.
  • Update Track/Bus/VCA colors while choosing color in Color Selection dialog.
  • Use Shift key to toggle gain-grouping on a Fader, ctrl to override solo/mute grouping.
  • Update Selection Clock when selected Region properties change.
  • Hide SoundCloud upload in Export Dialog until fixed.
  • Use OpenGL backed rendering/drawing for several Widgets on OS X/macOS including main Track Canvas to improve performance.
  • Add ability to drop Group from VCA via right click on Group tab.
  • Add preference to disable blinking of alert buttons.
  • Various improvements to Audio Setup dialog.
  • Add preference to only enable Click when recording is enabled.
  • Updates to Blueberry Milk colors/theme.
  • Merge most of the string-convert branch (see ardour-dev list for overview).
  • Remove no longer necessary LocaleMode preference.
  • Make -b/--bindings command line option output key bindings to HTML and launch in browser.
  • Add -A/--actions command line option to output actions' names in HTML and open in browser.
  • Deselect WASAPI support by default in Windows installer.
  • Make Track/Bus XML node order in Session file independent of display order [#7327]
  • Add action to select the topmost track and use in Faderport8 surface.
  • Make Group color property accessible to surfaces and scripts.
  • Improve Tap Tempo and allow tapping with keyboard (Space or Enter).
  • Add configurable limit to clock display range.
  • Restore visibility of Monitor Section and whether attached/detached.

Tempo

  • Allow tempo discontinuities at the beginning of ramped tempo section.
  • Changes to Tempo marker operations and modifiers.
  • Add 'Ramp to Next' to Tempo Marker menu, when next tempo is different.
  • Add 'Continue' to Tempo Marker menu to continue end tempo value of previous Tempo Marker.
  • Display red Tempo Mark pointer if tempo jumps more than 1 NTPM.
  • Display note type in marker text if note type is non-quarter.
  • Add entry for end bpm when creating a ramped Tempo in the Tempo Dialog.

MIDI

  • Use a Patch Change dialog to send immediate patch changes via the MIDI Track Controls context/right-click menu.
  • Support note name editing in the MIDI List Editor.

Plugins

  • Add support for VST effSetBypass. [#7266]
  • Cut reverb tail in a-reverb when deactivating plugin.
  • Improve a-delay to follow tempo-ramps and BPM changes.
  • Increase VST scan timeout and set default of Verbose Plugin Scan to false.
  • Changes to plugin categories to improve consistency across plugin API's/standards.

Scripting

  • Add action script to bypass all plugins.
  • Add action script to mute all Tracks.
  • Add script to installers/bundles to save a Session snapshot on export.
  • Add '==' instance equality operator and update scripts to use it.
  • Add bindings for transient analysis and add a script to print transients of selected regions.
  • Add Lua bindings to access MIDI Region note events and example script.
  • Optimize garbage collection (affecting performance of serialization).
  • Improve bindings for RouteGroupList and Plugin classes.
  • Add bindings for FileSource.
  • Add example script to convert MIDI-CC to Plugin Automation.
  • Add LuaDialog and derived Widgets as well as an example script.
  • Add bindings for setting group color.

Control Surfaces

  • Use "Mix" and "Proj" buttons on the Faderport to present the Mixer and Editor rather than a toggle.
  • Various improvements to the OSC surface.
  • Add support for Faderport8 control surface.
  • Update preferences when control surfaces change with session.
  • Retain the state of disabled control surfaces.
  • Add scrub and multi-mode jog commands to OSC surface.
  • Add automation mode feeback to OSC surface.
  • Support gain automation feeback in OSC surface [#7160]
  • Assign some default actions for the function select (F-keys) in the Mackie MCP user profile.
  • Updates to Korg Nano Kontrol2 MIDI map by Philippe Demartin.
  • Add MIDI map for Korg Studio and Arturia KeyLab 49.
  • Add MIDI map for Alesis QX25 from Nathan Stewart [#7345]

Fixes

  • Allow changing track colours with older 4.X Sessions.
  • Fix for touch mute automation.
  • Allow loading of SMF meta data with size greater than 127 bytes.
  • Fix implicit selection when operating Track header control buttons.
  • Fix audition with monitor section.
  • Don't display channel selector for instrument plugins with zero audio outputs.
  • Don't automatically open generic UIs for plugins without controls.
  • Fix crash when adding a plugin immediately after re-order (via script).
  • Fix issue with mouse button event ordering in EngineDialog.
  • Prevent an empty system config and ship the system_config in bundles again.
  • Fix crash when inserting time with split intersected regions.
  • Offset linked regions to compensate for negative start after trim drag [#7105]
  • Restore screen position when undoing creation of a MIDI note.
  • Prevent the General MIDI Control Protocol surface from overriding Session version.
  • Ensure no horizontal movement occurs when dragging regions with the x-constrain modifier enabled [#7260]
  • Fix AFL/PFL from MIDI tracks without audio
  • Work around a crash at exit with some Linux VST UIs.
  • Prevent creation of MIDI regions with length less than a pixel [#7271]
  • Fixes to VST Window re/sizing.
  • Prevent crash when removing time from track with automation. [#7287]
  • Fix issue when undoing of Fade range operation [#7283]
  • Use Tempo Curve color for measure line beats [#4930]
  • Correctly restore clock modes in Location Window and other AudioClocks.
  • Restore Solo/Mute when loading old 4.X Sessions.
  • Avoid possible crash with multi-bus AudioUnit plugins.
  • Prevent issue with automation playback setting Session as modified.
  • Fix issue with Pan stuck at center in OSC surface.
  • Fix toggling Monitor Mute/Dim/Mono actions with OSC.
  • Prevent MIDI tracks from drawing into the Ruler area.
  • Make Peak display in MixerStrip insensitive to mouse clicks/drags.
  • Update Patch Change Naming when plugins change.
  • Fix count-in for non 4/4 time signatures.
  • Hide eye-dropper color picker on OS X/macOS builds due to it not working.
  • Correctly load Track templates with inserts [#5778]
  • Fix crash when dragging playhead or mouse in ruler area [#7304]
  • Fix `set-*-from-edit-range` actions, when accessed from control surfaces
  • Fixes to reset keybindings.
  • Prevent crash during extreme timestretch. [#7305]
  • Fixes for performance issues with region selection. [#7274]
  • Retain order of concurrent MIDI events.
  • Prevent truncation of concurrent events with ALSA raw MIDI buffers.
  • Restore Track/Bus polarity invert state from older Sessions.
  • Use correct action path names in several midi-maps.
  • Prevent crash when loading MIDI port info where ports no longer exist.
  • Fix crash when clicking on the canvas while unloading a Session.
  • Avoid a possible deadlock in the control surface manager.
  • Prevent possible freeze when clicking on canvas without a AudioBackend running.
  • Fixes to performance issues when restoring Region selection state [#7274]
  • Fix nested VCA assigns and mixer-layout.
  • Fixes to copy/paste of MIDI automation from/to Parameter automation.
  • Corrections to latency measurement and Audio Setup dialog behaviour.
  • In smart-mode, don't switch to range-mode after "set range selection" and similar operations. [#7332]
  • Fix vari-speed and non-locked slave modes.
  • Use correct descriptions and typos in --help output.
  • Prevent MIDI learn handling events intended for other operations like temporary un/solo/mute.
  • Make exclusive solo work again via ctrl+alt+click on solo button.
  • Correctly restore track monitoring state from older Sessions. [#7336]
  • Correctly scale ruler for HiDPI. [#7226]
  • Scale text correctly in group tabs for HiDPI. [#7331]
  • Allow Session end marker to move correctly when a Session is created from a template. [#7348]
  • Prevent crash when replacing some LV2 plugins on a MIDI Track. [#7341]
  • Update the profile name in the Mackie control panel to reflect the profile being edited when assigning actions.
  • Make Save As and switch work correctly with a read-only Session. [#7352]
  • Remove duplicate "Tape" menu item in Record Mode drop down in the Add Track/Bus/VCA dialog.
  • Prevent creation of out-of-bounds image sizes during waveform rendering with high samplerates and high zoom levels.

Translation Updates

  • Updated Japanese translation by Hiroki Inagaki.
  • Updated German translation by Edgar Aichinger.

Contributors

André Nusser, Ben Loftis, cooltehno, Edgar Aichinger, Hiroki Inagaki, John Emmas, Len Ovens, licorne-sama, Nathan Stewart, Nick Mainsbridge, Nils Geisweiller, Paul Davis, Robert Schneider, Robin Gareus, Tim Mayberry

Posts: 11

Participants: 8

Read full topic


text Ardour 5.8 released
Tue, 28 Feb 2017 12:33:35 +0000

@paul wrote:

  

Although Ardour 5.6 contained some really great new features and important fixes, it turned out to contain a number of important regressions compared to 5.5. Some were easily noticed and some were more obscure. Nobody is happy when this happens, and we apologize for any frustration or issues that arose from inadequate testing of 5.6.

To address these problems, we are making a quick "hotfix" release of Ardour 5.8, which also brings the usual collection of small features and other bug fixes.

Linux distributions are asked to immediately and promptly replace 5.6 with 5.8 to reduce issues for Ardour users who get the program directly via their software management tools.

Download

General Changes and Improvements

  • Add Record with Count-in functionality accessible via Transport menu.
  • Save and restore Location clock modes in Locations pane in Editor List and Locations Window separately.
  • Improvements to sensitivity of actions in Region context menu. [#7077]
  • Version keyboard shortcut configuration file (.keys).
  • Add support for importing MIDI from Pro Tools Session files.
  • Consistently use the term VCA rather than Control Master.
  • When starting Ardour without any existing configuration files and not copying them from a previous version then still present the Startup/First time dialog.
  • Control (Primary Modifier) and right click on group tab will present Group Edit Window.
  • Shift (Tertiary Modifier) and right click on group tab will remove group.
  • Support for QT5 lv2 UIs in bundles/installers from ardour.org
  • Add support for relocating missing external files in Missing File dialog.
  • Improvements to wording in Preferences and Session Properties.
  • Change master meter type in toolbar via right click.
  • Constrain VCA slave value to prevent overshoot and snap back on release.
  • Use consistent Installer names for all platforms (Name + Version + Arch)

MIDI

  • Separate bank selection into MSB/LSB in Patch Change Dialog.

Plugins

  • Allow rescanning of VST plugins after changing VST path.

Scripting

  • Update bindings and scripts for API changes.
  • Updates to Lua scripting documentation.
  • Add bindings for plugin reordering and add example reverse plugin order script.
  • Add bindings for solo/mute and realtime control changes and update example script.
  • Bind scripts via right click on Lua Action Script Button in Toolbar.
  • Unbind scripts via Shift + right click on Lua Action Script Button in Toolbar.
  • Allow scripts to define a custom icon when bound to a Lua Action Script Button.
  • Include Audio to MIDI script in Bundles/Installers.
  • Add ability to Load/Remove Session scripts in the Script Manager.
  • Edit button in Script Manager now opens Lua Script Window.
  • Add bindings to create Aux sends and add script to send multiple tracks to an Aux bus.
  • Add Action Script Button icons for various scripts.
  • Add example script to show/hide Tracks in the Editor.

Translation Updates

  • Updated Japanese translation by Hiroki Inagaki
  • Updated Czech translation by Pavel Fric

Fixes

  • Use correct position when copying MIDI regions
  • When moving MIDI regions with non-default meter and snap set to Beats, finish in the corect position [#7234]
  • Reset window size when switching between custom and generic plugin UI.
  • Fix timing of regions recorded before the musical origin (bar 1, beat 1)
  • loaded correctly.
  • Vertically constrained Region drag now working again.
  • Properly update main window title when switching Snapshots.
  • Toolbar height no longer changes with varying appearance options.
  • Fix issues with Track and Mixer Strip order.
  • Don't show hidden Mixer Strips when spilling a VCA.
  • Undo/Redo now works for Snap position to grid via Region context menu. [#7246]
  • Ensure toggle Editor & Mixer action always works with a detached Mixer Window.
  • Percussive notes now shown in correct position while dragging during move/copy.

Contributors

Ben Loftis, Damien Zammit, Hiroki Inagaki, John Emmas, Len Ovens, Nick Mainsbridge, Paul Davis, Robin Gareus

Manual

Although the Ardour manual is not part of an Ardour release, manual.ardour.org has seen a lot of activity recently. Thanks go to Ed Ward, Chris Goddard and Shamus Hammons, Len Ovens and others who have been involved in this effort.

Posts: 4

Participants: 4

Read full topic


text Ardour 5.6 released
Sat, 11 Feb 2017 21:40:40 +0000

@paul wrote:

  

Another two months of development has rolled by, involving more than 600 commits by developers, and it's time for us to release Ardour 5.6. Although there are no major new features in this release, there is the usual list of dozens of bug fixes major and minor, plus some workflow and GUI enhancements. There has been a significant rearrangement of the transport bar to try to use space more efficiently and effectively. The new design also permits session navigation while using the Mixer tab, and there are numerous optionally visible elements. Similarly, the Preferences dialog was rearranged to try to make it easier to find and browse the many, many available options. Other interesting new features: session archiving, a new General MIDI default synth for MIDI tracks, and direct and immediate control of routing for heavily multichannel (typically multitimbral) synth plugins.

Download  

  

General Changes and Improvements

  • Speed up unloading large Sessions
  • Speed up recent Session display, with many large Sessions and or snapshots.
  • Transport control area layout changes.
  • Add a mini-timeline to the Toolbar.
  • Follow Edits has been renamed Follow Range and has changed behaviour.
  • Allow customization of Toolbar via Preferences -> Appearance -> Toolbar
  • Add ability to archive Session.
  • Normalize audio when archiving to a fixed point format.
  • Add more precise localization options to Preferences -> General -> Translation.
  • Enable all types of Range locations (loop, start, end) to be glued to BBT.
  • Allow preference for tempo to be expressed in divisions per minute or quarter notes per minute (General -> Tempo).
  • Preference layout, grouping, wording/naming and tooltip changes.
  • Add button to reset keyboard modifiers to recommended defaults in preferences (Editor -> Modifiers).
  • Minor updates to Blueberry Milk, Caineville, Clear Gray and Cubasish Themes.
  • Support added to compile on macOS 10.12 (Sierra).
  • Modify playlist option labels in Duplicate Track/Bus dialog. [#7149]
  • Support import of Tempo maps during MIDI import at selected position.
  • Show context menu on right click on VCA track header.
  • Support all drive letters on windows (with harvid version >= 0.8.2).
  • Rename Bindings Window to Keyboard Shortcuts.
  • Display name of conflicting keyboard shortcut.
  • Allow automation line fill opacity themable.
  • Add global monitoring controls to toolbar, enable visibility via Preferences -> Appearance -> Toolbar.
  • Implement count-in before recording with fixed BPM, enable via Session -> Properties -> Misc.
  • Implement record with pre-roll, accessible via Transport menu.
  • Allow Editor toolbar and background to be themable.
  • Allow changing Metronome level via Mouse Wheel on Metronome button in Toolbar.
  • Display application version Session was last modified/saved with tooltip in recent session list.
  • Scale Gain automation by masters current value if slaved.
  • Add scripts to run Ardour under rr debugging tool.
  • Disable VST scan in safe mode.
  • Mark Session dirty when moving range/tempo markers. [#7217]
  • Add undo/redo for changing marker lock style.
  • Mark Loop button insensitive when no loop range is defined. [#7195]
  • Name VCA's by number and user defined name if set.
  • Add two export format specifications for stems.
  • Include gmsynth.lv2 in application bundles/installers.
  • Add option to use snapshot name instead of Session name when exporting.
  • Save-As now working again as intended (no longer incorrectly asks about saving and does not incorrectly switch to new version unless asked)

Actions/Binding Changes

This release changes the name of several Ardour actions that may be used by OSC & MIDI bindings and by customized key bindings. The affected action names are listed below. The old full action names began with "Editor/" - this has been changed to they all begin with "Common/".

You can ignore this change unless you use OSC, or MIDI binding maps or customized key bindings.

If you do use any of these features, you will need to either/or modify your OSC or MIDI bindings and redefine your key bindings after removing or renaming the customized ones. Failure to do this will mean that existing bindings to these actions will not function as intended.

These changes were made in order to make these actions available from within the Mixer tab, rather than just the Editor.

Affected Actions

  • alternate-jump-forward-to-mark
  • alternate-jump-backward-to-mark
  • set-session-start-from-playhead
  • set-session-end-from-playhead
  • toggle-location-at-playhead
  • add-location-from-playhead
  • alternate-add-location-from-playhead
  • remove-location-from-playhead
  • alternate-remove-location-from-playhead
  • nudge-next-forward
  • nudge-next-backward
  • nudge-playhead-forward
  • nudge-playhead-backward
  • playhead-forward-to-grid
  • playhead-backward-to-grid
  • start-range-from-playhead
  • finish-range-from-playhead
  • start-range
  • finish-range
  • start-punch-range
  • finish-punch-range
  • start-loop-range
  • finish-loop-range
  • alt-start-range
  • alt-finish-range

Editor Improvements

  
  • Duplicate action now works in Range Selection mode.
  • Multi-Duplicate now works for Range Selections.
  • Zoom to selection (z key) now zooms on both axes.
  • Add zoom to selection (horizontal) action.
  • Add preference (editor -> general) to zoom to selection in object mode.
  • Left and right arrow keys move playhead to next/previous grid point instead of region boundary (old behaviour can be accessed with modifiers)
  • Speed up patch change redisplay.
  • Don't locate when clicking on region fade handles in smart mode with follow edits enabled.
  • Add actions to set current meter/tempo.
  • Display boost/cut gain after audio region name.

Mixer Improvements

  • Display vca's at the end of track/bus list.
  • Show isolate solo and lock solo status buttons in master mixer strip but keep de-sensitized to preserve mixer strip layout between track/bus types.
  • Fix update of group color in mixer strip header.
  • Show vca color on number label and top of the mixer strip.
  • Fixes to visual alignment of gui elements in the mixer.
  • Use a popup menu to select meter point instead of cycling through modes.
  • Fix assign record enabled/soloed to control master. [#7204]
  • Assign/unassign selected mixer strips to vca using right click/context menu.

MIDI Improvements

  • Increase midi related test coverage and refactoring.
  • Add midnam support for a-fluid synth.
  • Allow sending immediate patch changes via midi track context menu. [#6830]
  • Speed up midi ghost note redisplay.
  • Save and restore midi automation controls.
  • Add option to use track numbers, track names or instrument names from smf files when importing.
  • Add track and instrument names to smf files.
  • Add option to use tempo map from smf file on import.
  • Access to midi track channel settings now only via context menu.
  • Improved canvas redraw performance with many midi notes.
  • Add the midi channel number to controller names.
  • Implement copy drag for midi notes. [#5570]
  • Prefer general midi synth (gmsynth) as the default instrument.
  • Performance improvements related to display of sysex data.

Plugins Improvements

  • Add support for mac vst hidden/favorites.
  • Show plugin format (lv2/ladspa/vst/etc) in menus to differentiate between the same plugin with several formats installed (e.g au/vst).
  • Allow to directly fan-out when adding multichannel instruments.

Scripting Improvements

  • Add bindings for track/bus groups, miditrack::midicontrol, timecode conversion and audioregion rms/peak.
  • Extend bindings for plugininsert.
  • Add fader to trims script.
  • Add script to add a-high/low pass filter to all tracks.
  • Add create drum tracks script.
  • Add example script to start recording on a midi event.
  • Add script to delete x-run markers.
  • Allow lua bindings up to 10 arguments.
  • Add example script/snippet for importing file/s.
  • Add script to save snapshot after exporting.

Control Surfaces

  • Remove unused feedback option from osc surface controls.
  • Add talent individual monitor controls to osc surface.
  • Make surface numbering the same as port numbering in mackie gui. [#7219]

Fixes

  • Fix update of Track/Bus color in the Summary and Connection Manager.
  • Fix loading of Blueberry Milk and Clear Grey themes. [#7155]
  • Fix issues in Export with trim enabled. [#6412]
  • Fix crash when creating track via region drag when exceeding JACK connection limit. [#6496]
  • Fix crash at stop when recording in non-layered mode.
  • Fix parsing export trim threshold config variable.
  • Fixes for MSVC compiler
  • Fix video-monitor "sync-source" changes
  • Fix a source of hangs when closing Session with ALSA backend.
  • Fix possible crash when naming tracks with reserved I/O names. [#7171]
  • Fix flickering in tempo curve when Markers are reordered.
  • Fixes for sample locked Meter and Tempo sections?
  • Fix crash when dragging sample locked tempo over a music locked Tempo while snapped to grid.
  • Fix potential crash in peak file building.
  • Fix possible crash when removing ports with JACK1.
  • Fix layered record undo to include changes to existing regions.
  • Fixes to ensure Command key generates MOD2 on OS X.
  • Fix region position when dragging multiple regions to respect time base/lock style.
  • Fix thread safety issues with invalidation requests in event loops.
  • Fix inaccessible controls in Pin Connections window. [#7177]
  • Fix crash when resetting with VCA peak-meters.
  • Fix patch changes appearing outside of Region bounds.
  • Fix toggling between Editor and Mixer using Korg nanoKontrol2.
  • Fix Solo button on Faderport.
  • Fix management/ownership of shared playlists. [#7150]
  • Fixes to inactive Tempo sections.
  • Fix possibly incorrect start position of MIDI regions after split.
  • Fix crash when changing Pane widgets. [#7198]
  • Fix MTC slave implicit return on transport stop.
  • Fix some memory leaks in libpbd, libardour and GUI code.
  • Fix undo/redo for Regions -> Edit -> Close Gaps.
  • Fix continuous multi-selection in the Mixer.
  • Fix a-fluidsynth bank select.
  • Fix Generic MIDI controls so changes are propagated to the group (if in one).
  • Fix a number of issues related snap with music locked regions.
  • Fix a few issues with dragging MIDI notes including across tempo changes.
  • Fix state restoration of VCA slaves.
  • Fix saving state of Solo and Mute controls when slaved.
  

updated translations

  • Italian translation. [#7180]
  • German translation by Edgar Aichinger.
  • French translation by Olivier Humbert.
  • Japanese translation by Hiroki Inagaki.
  • Russian translation by Alexandre Prokoudine

Contributors

Ben Loftis, cooltehno, Daniel Sheeler, David Robillard, Dobroslav Slavenskoj, Ed Ward, Hanspeter Portner, John Emmas, Julien Roger, Len Ovens, Nick Mainsbridge, Nil Geisweiller, Paul Davis, Paul Tirk, powerpaul17, Robin Gareus, Tim Mayberry, Tobi Stadelmaier

Posts: 22

Participants: 11

Read full topic


@paul wrote:

Finding a piece of software not to your liking or not capable of what you need is just fine (expected, almost).

And then there’s this sort of thing.

Can you make it user friendly? Fucking ridiculous. I use Sonar,plug in my dongle/breakout box,and it just works. One setting change for in and out for the duo or quad capture. No one in the business has anything good to say about Ardour,if they've even heard of it. I'm not trying to be rode. It's a suggestion. Make it user friendly.

To our friends at Cakewalk: you’re welcome.

Posts: 17

Participants: 15

Read full topic


text Ardour 5.5 released
Thu, 01 Dec 2016 11:43:31 +0000

@paul wrote:

  

Ardour 5.5 is now available, with a variety of new features and many notable and not-so-notable fixes. Among the notable new features are support for VST 2.4 plugins on OS X, the ability to have MIDI input follow MIDI track selection, support for Steinberg CC121, Avid Artist & Artist Mix Control surfaces, "fanning out" of instrument outputs to new tracks/busses and the often requested ability to do horizontal zoom via vertical dragging on the rulers. There are also the usual always-ongoing improvements to scripting and OSC support.

As in the past, some features including OSX VST support, Instrument Fanout, and Avid Artist support were made possible by sponsorship from Harrison Consoles.

Download

Fixes

  • Work around MIDI devices sending invalid timestamps on OSX.
  • Open Sessions with files referenced from removable drives on Windows.
  • Various fixes for NetBSD and FreeBSD.
  • Add MIDI Control Change at correct location when importing.
  • Update Region colors on theme change.
  • Fix/Support note name translations (e.g "Ré ♯").
  • Allow loading sessions with missing external files. [#7067, #7114]
  • Use distinct color identifier for meter clip indicator. [#7010]
  • Prevent panners being reset when switching to Aux sends and back. [#6893]
  • Use correct BBT offset when using Insert Time. [#7072]
  • Fix restoration of key bindings assigned to Windows+key. [#7037]
  • Prevent duplicate moves when selecting regions on shared playlists.
  • Fix crash when instrument instantiation fails on track creation.
  • Prevent infinite loop when calculating tick marks on low zoom levels.
  • Fix LTC-generator 24h wraparound
  • Correctly handle failed activation of Control Surface Modules
  • Fix Master Track moving down one position in Editor after Session reload. [#7080]
  • Mark Session state as changed when tracks are reordered. [#7093]
  • Improved fix for playback of linked MIDI Regions [#6541]
  • Fix to keep Meterbridge Window on top.
  • Fix for non-working buttons in Monitor Section after second Session load [#7098]
  • Fix LV2 state versioning with Session templates.
  • Include Aux Busses in default strip types in OSC Surface [#7090]
  • Fixes to Insert/Remove time dialog [#7072]
  • Fix intermittent hang when stopping PortaudioBackend [#7095]
  • Fix playlist XML nodes changing order on Session save [#7053]
  • Fix crash loading u-he Diva VST plugin on Windows
  • Fix Duplicating Tracks with Sidechains [#7117]
  • Fix incorrect Midi Region length when splitting
  • Fix for widget visibility with detached preferences window [#7002]
  • Fixes when creating MIDI notes in Sustained note mode [#7126]
  • Fixes when creating MIDI notes in Percussive note mode [#7130]
  • Fixes to Cut Mode to make the cut line visible and respect snap modifier
  • Fix inaudible Percussive notes being displayed at the end of the Region
  • Fix crash when editing pitch of notes to outside visible area [#7135]
  • Fix crash when deleting a MIDI Region while mouse over CC event
  • Fix concurrency/locking issue with Event Loop request invalidation [#7049]
  • Fix creation of playlists with duplicate names [#6523, #5681, #6497]
  • Fix output display for non-plugin processors in the Processor Box
  • Fix forwarding of output buffers by using correct channel count
  • Fix loading, recording & saving MIDI with PolyKeyPressure events [#6948]
  • Fixes to Duplicate Track [#7141, #7146]
  • Fixes to OSC Control Surface
  • Fix handling of pitch bend events by a-fluidsynth [#7140]
  • Fix for reading CAF audio files over a certain size

General Improvements

  • Many MIDI and Tempo related refactorings, fixes and improvements to performance, source code documentation and tests. (Thanks Nick)
  • Include Session utilities in the application installers/bundles.
  • Allow feedback loops from internal Sends to enable custom "Echo" chains.
  • Improved performance when reading and writing XML files.
  • Improved performance of Region export.
  • Snap to Track Strip boundaries when scrolling with arrow keys in the Editor.
  • Clicking on a Strip in the Mixer Strip List will move the Strip into view.
  • Snap to Mixer Strip boundaries when scrolling with arrow keys in the Mixer
  • Minor updates to Cubasish Theme.
  • Compensate for latency/correct alignment when exporting the Master Bus.
  • Improve automatic Track naming [#7092]
  • Add option to zoom in the time rulers using button press and dragging vertically. [#6768]
  • Speed up changes to AFL/PFL on large Sessions
  • Large improvements in time to process Solo changes [#7119]
  • Speed up Track/Bus creation time
  • Restrict ALSA input/output device selection to valid combinations
  • Speed up Track deletion when Editor Mixer Strip is visible

MIDI

  • Many minor fixes and improvements
  • Support MIDI input follows Track selection. [#6744]
  • New MIDI -> Ports page in Preferences for managing MIDI port functionality and enabling MIDI input follows Track Selection.
  • Added support for Type 0 MIDI files and add option to split channels into tracks on import.
  • Added MIDI mapping for AKAI Midimix.
  • New MIDI Note selection XML format, existing note selections will be lost.
  • Improved editing in Percussive note mode

Plugins

  • VST 2.4 plugin support on OSX
  • Add functionality to Fan out an Instruments outputs to new Tracks/Busses (video demo explanation at https://vimeo.com/191024580)
  • Allow LV2 plugins to provide Midnam XML.
  • Increase maximum release time in a-comp.
  • Sort Instrument list alphabetically.
  • Updated internal versions of qm-dsp library and qm-vamp plugins.
  • Allow LV2 Plugins to signal state changes and mark Session state as changed.
  • Support LV2 PortGroup extension
  • Add support for output-channel/bus grouping in AU plugins

OS X

  • Mouse drags on plugin GUIs (editors) are now handled correctly when they end outside the window.
  • Video monitor "full screen" mode no long spans all screens

Scripting

  • Added or improved Lua bindings for VAMP plugins, TempoMap, Basic MIDI model editing, Inter-Processor communication, Source, AudioSource, Route, Panner, Instrument
  • Add example script for Audio to Midi Transcription.
  • "Sound Smasher" example script added.
  • Add prototype script for converting polyphonic audio region to a MIDI region.
  • Add example script for instrument fan-out
  • Add example script to modulate parameters globally
  • Add support for calling ARDOUR.DSP Lua functions from UI scripts
  • Add example script to process Regions selected in the Editor
  • Add MIDI LFO example script

Control Surfaces

  • Added Support for Steinbergs CC121 Control Surface
  • Activate/Deactivate plugins via OSC
  • Added configuration files for the Avid Artist Control and Artist Mix Control surfaces.
  • Allow Aux Buses visibility to be controlled separately via OSC
  • Add OSC support to query strips internal sends [#7136]
  • Add OSC support to query plugins and their parameters [#7137]

Translations

  • Updated German translation (Edgar Aichinger)
  • Updated French translation (Olivier Humbert)

Contributors

Ben Loftis, cooltehno, David Robillard, eighthkeepa, John Emmas, Kamil Rytarowski, Len Ovens, Michael Beer, Michiel de Roo, Nathan Stewart, Nick Mainsbridge, Nil Geisweiller, Nils Philippsen, Olivier Humbert, Paul Davis, Robert Scott, Robin Gareus, Tim Mayberry, W.P. van Paassen

Posts: 4

Participants: 4

Read full topic


text Ardour Looks, part 197.2
Wed, 09 Nov 2016 02:14:12 +0000

@paul wrote:

From a discussion on http://cdm.link about FL Studio:

For those who wonder why I tend to ignore/discount "Ardour needs to look better" comments, this is a great introduction :)

Posts: 6

Participants: 6

Read full topic


text Ardour 5.4 released
Sat, 01 Oct 2016 15:25:36 +0000

@paul wrote:

Ardour 5.4 is now available, with important bug fixes for MIDI (including looping), dozens of less significant but still noteworthy fixes and new features, plus the first version of our support for Ableton's Push 2 surface.

2 Major MIDI fixes

  • Looping with MIDI tracks now works correctly. Previous versions of Ardour could be easily provoked into either dropping notes or holding notes if the loop boundaries occured in particular places.
  • If you use a musical meter with a denominator other than 4 (e.g. 5/8, 7/8 or 3/3), versions 5.0 - 5.3 of Ardour incorrectly stored the tempo when writing SMF (.mid) files. The SMF standard requires that tempo is given in terms of pulses per quarter note. Ardour 5.0 - 5.3 incorrectly used pulses per meter denominator (e.g. eighth notes). We have written a utility to correct files written in this way - please let us know if you need to use it. This issue only manifests when using the SMF files with any tool (including Ardour 5.4 or before 5.0) that obeys the SMF standard. We will gladly assist anyone negatively impacted by this error. Just get in touch.

Abelton Push 2 Support

This version of Ardour has the first version of our support for Ableton's Push 2 surface. This is an expensive but beautifully engineered control surface primarily targetting the workflow found in Ableton's Live software and other similar tools such as Bitwig. As of 5.4, Ardour does not offer the same kind of workflow, so we have focused for now on using the Push 2 for mixing and editing and musical performance, without the clip/scene oriented approach in Live. This may change in future versions of Ardour.

Full documentation on Ardour's Push 2 support is available

Fixes

  • Real fix for preferences window/tab (claimed to be fixed in 5.3 but actually not)
  • Update clear-gray theme colors
  • Add track/bus no longer allowed while recording
  • Fix issues with finding files with duplicate names that were imported without copying them to the session
  • Session lock dialog can no longer be closed using the window-manager "X" button
  • Do not run normalize if normalize dialog is closed from the window manager
  • Correctly and fully restore of bindings for mute and solo controls.
  • (Windows only) Creation of Sessions with localized names containing characters that aren't in the system codepage now works. This also fixes the issue where a Session would not open when it was moved into a path with characters that aren't in the system codepage.
  • (Windows only) Cleanup-Unused Sources and Flush Wastebasket now work even when paths contained characters that aren't in the system codepage(most non-ascii characters).
  • Save and Restore analysis and soundcloud checkboxes in the ExportDialog.
  • Do not crash when aborting Region trim using Esc key.
  • Moving Session start/end markers now marks Session as modified.
  • Correct disk usage/space reports on windows.
  • Do not delete selected MIDI Notes while dragging.
  • Remove crash at exit caused by key bindings etc.
  • Remove crash when exiting after using and being disconnected from JACK.
  • MIDI notes now follow changes in meter denominator.
  • Drawing long MIDI notes with the grid/snap enabled no longer snaps them to the wrong position.

Newly Exposed in Lua

  • PeakMeter
  • Record enable/disable
  • Session.request_play_loop() and Session.get_play_loop()
  • Locations.remove()
  • Location.name
  • Plugin controls
  • Glib:build_filename() (for portably constructing paths across platforms)
  • example scripts to prepare a session for recording, and exporting markers as mp4 chapters

Contributors

Robin Gareus, Tim Mayberry, Johannes Mueller, Guido Aulisi, Nathan Stewart, Ross Lagerwall, cooltehno, Thomas Brand, Todd Naugle, Nick Mainsbridge, and Paul Davis.

Posts: 1

Participants: 1

Read full topic


text Ardour Solar Powered Development
Wed, 28 Sep 2016 22:16:06 +0000

@paul wrote:

Some Ardour users and other interested readers may be intrigued to know that almost all of Ardour’s lead developer’s work on the program right now is powered by photovoltaic panels. 540W panel capacity and 510Ah of lead-acid AGM batteries generally provides enough power to keep a 4 core i7-3370US 3.10GHz system running, with occasional use of a Mac Mini. It also runs the fridge, lighting, music and pump systems in the Sprinter van that he and his wife are living in until June 2017. With the exception of the Mac Mini, all other computing equipment is 12V DC native (no power bricks), including the 40W Topping amplifier used to power a pair of Micca monitors.

It is unlikely that the solar power available in the UK during the winter (where the van will be located) will be enough to keep things running, so at some point reverting to a cable and mains power seems likely. But for now, all of Paul’s work is powered by the sun. Welcome to the future!

(ps. as a footnote, the other systems intimately involved in Ardour development, while connected to the grid, are also powered via contracts that guarantee 100% renewable energy sources.)

Posts: 6

Participants: 6

Read full topic


text Ardour web presence: developer wanted
Wed, 14 Sep 2016 01:26:45 +0000

@paul wrote:

Ardour is an open source application for recording, editing and music music & sound for Linux, OS X and Windows. The project started over 16 years ago, and has seen contributions from more than 70 programmers. It recently reached its 5.0 release milestone. It generates sufficient revenue to pay its lead developer a reasonable salary, as well as covering all costs associated with its network presence.

The Ardour project currently needs a small number of small/medium web-related tasks to improve the web experience associated with the application's user community. Although the lead developer also functions as primary web administrator, and has sufficient web development skills to accomplish these tasks, this increasingly seems time inefficient. We have some compensation available for the work (amount(s) to be negotiated).

Ardour currently uses 5 independent web sites:

ardour.org
static site
manual.ardour.org
static site
community.ardour.org
Drupal dynamic site mostly for forums, articles with comment threads, and payment logic/processing.
tracker.ardour.org
Mantis bug tracker
nightly.ardour.org
hand-coded semi-static site

The work to be done mostly concerns community.ardour.org, so the person who undertakes the work should have some reasonable understanding of both PHP and Drupal, even if ultimately other web technologies are chosen.

The specific tasks that need to be done are outlined below. We suspect that it is most likely that someone would tackle one of these tasks at one time (they are mostly, though not entirely independent).

  • Modernize forum (https://github.com/discourse/discourse or similar), keep existing posts and comments (currently drupal)
  • Share user credentials and permissions across all sites: payment, forum, bug-tracker, download, nightly
  • Migrate existing user-database (currently drupal salted md5 hash) to whatever it'll be.
  • Integrate new(er) online payment toolkits into our existing models.
  • (optionally) Update the bug-tracker

If you are interested in tackling one of more of these tasks, please get in touch with paul@linuxaudiosystems.com including an indication of your technical background and estimated compensation level. Ideally we'd like someone who cares about Ardour as much as we do, but fundamentally, the work just needs to get done.

Feel free to post this announcement in any appropriate places.

Posts: 3

Participants: 2

Read full topic


text Ardour 5.3 released
Mon, 29 Aug 2016 01:30:41 +0000

@paul wrote:

Ardour 5.3 is almost entirely a bug fix release that corrects a number of issues noticed and corrected since 5.1.

There was no 5.2 release, due to a mistake during the release process.

If you're looking for information about Ardour 5.0, you'll want to read the release notes.

Download  

Fixes

  • Correct visibility of preferences dialog when the application starts with a detached preferences window.
  • Ensure click free bypass for all a-* plugins.
  • Enable normal operation when using an audio interface on OS X that is split into two "halves" (playback and capture), both with the same name. The Behringer UMC22 is one such device, but there are others already known to use this wierd and poor design. Our assumption is that the device(s) do not use the same sample clock for playback and capture.
  • Improve layout of a-eq GUI.
  • Update CC automation menu on when track selected channels change.
  • Building with support for Windows-VST on Linux now works again.
  • Correct "focus-on-clock" behaviour (bound to keypad divide key by default).

New Stuff

  • Extend lua bindings (processor selection, plugin-info).
  • Single action/button punch in/out feature (available for control surface use or via shortcuts).

Contributors

Robin Gareus, Julien Rivaud, Nathan Stewart and Paul Davis.

Posts: 6

Participants: 4

Read full topic


text Ardour 5.1 released
Thu, 25 Aug 2016 13:08:04 +0000

@paul wrote:

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.

Download  

Fixes

  • 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.

Lua

  • 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.

Contributors

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

Posts: 8

Participants: 4

Read full topic


text Ardour Pong
Sun, 21 Aug 2016 14:28:13 +0000

@paul wrote:

Ardour Pong from Robin Gareus on Vimeo.

A console classic for your console. Sample-accurate automation and all :)

Showcasing Lua scripting facilities/ for the Ardour Digital Audio Workstation. Compact, easy to read code

Posts: 12

Participants: 8

Read full topic


text Ardour 5.0 released
Fri, 12 Aug 2016 10:23:48 +0000

@paul wrote:

Ardour 5.0 is now available for Linux, OS X and Windows. This is a major release focused on substantial changes to the GUI and major new features related to mixing, plugin use, tempo maps, scripting and more. As usual, there are also hundreds of bug fixes. Ardour 5.0 can be parallel-installed with older versions of the program, and does not use the same preference files. It will load sessions from Ardour 2, 3 and 4, though with some potential minor changes.

Windows is now a supported platform

This is the first version of Ardour with official Windows support. Several years of products based on Ardour and our own nightly builds for Windows have made us confident that Ardour runs just as well on Windows as other platforms. We will not be providing support with:

  • installing Ardour on Windows
  • issues with audio hardware
  • system- or user-specific issues
These are out of scope for our developers and user community. However if you have issues actually doing stuff with Ardour, or there are generic problems affecting all Windows users, we will try to provide Windows users with the same kind of assistance that we do on Linux and OS X.

Read more below for the full list of changes ....

Download  

Tabbed User Interface

The editor window, the mixer window and preferences are now available as "tabs" in a single window, with transport controls shared across them all. Working with Ardour on laptops and other small-screen and/or single monitor systems is now much easier. If you use multiple monitors, and/or prefer to have the editor, mixer or preferences in their own windows, you can tear them off and Ardour will remember those settings for the future.

Control Masters (VCAs)

Although track/bus groups have offered a certain kind of grouped-control over gain, solo, mute and more, traditional mixing consoles have long had group master channels ("VCAs") which allow you to combine both a single fader to control the group level while also allowing you to easily adjust the relative levels inside the group. For large projects, this can make mixing much easier to control. After a significant re-engineering effort, Ardour 5.0 has support for control masters. In a nod to our "offer more than 1 way to do things" approach, it will allow you to use either or both of the conventions for combining multiple masters:

  1. Nest VCAs (VCA 2 controls VCA 1 etc.)
  2. Chain VCAs (VCA 1 and VCA2 both control track or bus N)

Tempo Ramps

Although Ardour has some uncommonly flexible options for working with tempo, one thing we've never offered before are "ramps" - continuous smooth changes in tempo, often known as accelerando (tempo gradually speeding up) and ritardando (tempo gradually slowing down). In 5.0, tempo ramping finally comes to Ardour.

In addition, translations between audio sample positions and BBT positions during GUI operations retain the musical position even in the presence of tempo changes.

Lua Scripting

5.0 includes the ability to write scripts in the Lua programming language that have almost complete access to all Ardour internals. You can implement new functionality of many kinds, including writing synths, filters and other signal processing tasks since Lua is realtime safe. This release does not feature as much GUI integration as we would like, but it is still a deep and powerful new feature.

The reference manual contains lots of information about using Lua. You can find dozens of examples in the source code's scripts folder, or browse them on GitHub.

Sidechaining and Pin Connections

Ardour's ability to allow unusual I/O configurations is both a blessing and a curse. On the one hand, it allows users to do creative things that are hard to do in other DAWs. On the other hand, it causes confusion when doing something as simple as adding a compressor plugin with sidechain support. Those 3 inputs? What are they? How should they be wired up?

5.0 sees an amazing new capability to manually control the internal wiring of plugins, if you choose to do so. You can switch the left and right feeds of a normal 2-channel plugin, or the outputs, or bypass inputs or outputs altogether. Adding "odd" plugins (with inputs and outputs) now becomes possible, with you in control of how the extra (or missing) channels are wired up.

There is an excellent video from Harrison Consoles that shows this feature at work in Mixbus. Almost everything in the video is relevant to Ardour.

Plugin Inline Display

In traditional DAWs, including older versions of Ardour, the only way a plugin can draw anything on the screen is by the DAW opening a new window to display the plugin's own editor/GUI.

In Ardour 5.0, plugins can draw displays "inline" in the mixer strips, giving rise to many new possibilities. Note that this feature requires explicit support from the plugin - it does not make it possible to pack normal plugin GUIs into the mixer strip. Also, for the time being, these new graphical displays are for display only - inline controls for all plugin parameters have been available for several releases already.

Built-in Plugins

For a long time, people have asked "what plugins does Ardour come with?" and the answer was "none". Now, Ardour 5.0 comes complete with 5 basic but usable plugins, derived from free and open source code, and curated to ensure that they work well with Ardour and for real world purposes. . In particular, all of them are dezippered for all parameters. None of them have custom GUIs, but are easily and appropriately controllable via the generic Ardour plugin GUI. They are:

a-comp
A side-chain enabled compressor with the usual controls.
a-reverb
A reverb that finds a balance between sounding good, using a lot of CPU and having too many controls.
a-eq
A nice sounding 4-band parametric EQ with shelves
a-delay
A basic single-tap delay line, with tempo sync
a-high/low pass
Independent high and low pass filters with steepness up to 48dB/octave.
a screenshot showing the 5 a-* plugins

These plugins run on all platforms, and should answer your basic needs without having to look for 3rd party solutions until you really need to. Sessions that use only these plugins will be portable to any other instance of Ardour 5.x or later, on any platform. We may add other basic plugins to this set in the future, based on user feedback and requests.

Harrison's high-quality commercial plugins

In addition to the a-* plugins, official Ardour 5.0 bundles (from ardour.org) come with an unlicensed set of Harrison's high-quality commercial plugins for evaluation. The Harrison plugins are fully functional; but their controls will become locked shortly after the plugin's window is opened. Licenses to permanently unlock the controls may be obtained from Harrison's Mixbus Plugin store. The Harrison plugins run on all platforms, ensuring session portability.

a collection of images of Harrison plugins

MIDI Busses

Until 5.0, it was at best convoluted to merge MIDI streams to allow for common processing or routing, for instance to a multi-instrument synthesiser. This release makes busses able to handle equally well audio and MIDI, which enables efficient workflow for virtual drumkits where the arrangement uses different MIDI tracks. Moreover, busses with both Audio and MIDI inputs are well suited for vocoders and similar plugins.

OSC

Ardour's Open Sound Control (OSC) support for 5.0 has been completely overhauled. While limited compatibility with 4.x OSC commands has been retained, the command paths have changed. We have now extended the available commands to make it possible to write a much more fully-featured control surface using OSC. Notably there is significantly more options for feedback to the OSC controller from Ardour itself. 5.0 also features a set of redundant OSC commands that make it easier to use products like Hexler, TouchOSC and Lemur which all have significant limitations in the format of the messages they can send. Specific new features include:

  • Banking has been added so that a surface with limited strips can still access all Ardour's mixer strips.
  • A surface can tell Ardour how many strips to use for banking.
  • A surface can tell Ardour which of two fader maths to use (position or raw dB)
  • A surface can tell Ardour what feedback it would like (buttons only, or controls, or PH position)
  • A surface can tell Ardour what kind of mixer strips it wants to see (audio, midi, buses, etc.)
  • There is a /select strip that always operates on the selected strip (same as the editor mixer strip)
  • More than one surface can be used at a time with independent settings.
  • Those settings are saved with the session.
You'll find full documentation on current OSC support in the manual.

Theming

Ardour 5.0 includes 5 new color themes (all contributed by users), including Caineville (similar to Ableton Live), Unastudia (similar to Presonus Studio One), Cubasish (similar to Cubase), Clear Gray and Blueberry Milk. Note that the theming capabilities of Ardour have not changed since 4.0, but these two users took the time to use the color-choosing possibilities to their fullest. This is done with any need to rebuild Ardour, so anyone who wants to try this can (being aware that it is several hours worth of work to generate a completely new color theme).

Check out all 6 themes in the carousel below, and click on any image for a larger image.

GUI Changes

  • Create new track by dragging an instrument from the favorites sidebar.
  • Allow copying of any processor settings (plugin, fader, meter, etc.) by dragging processor onto another of same type.
  • Redesign keybindings editor to work with tabbed notebook, one tab per set of bindings.
  • Avoid issues with splash screen hiding other windows at startup.
  • Desaturate inactive rec-enabled button, to provide more contrast with active recording state.
  • Consistent Location GUI layout including a "Go To" button.
  • Don't show engine dialog when loading a session..
  • Remove the splash-screen when changing sessions.
  • Re-enable the "Show Tooltip" preference.
  • Rhythm Ferret improved with new modes and options.
  • Removing multiple tracks is now a one confirmation step.
  • Option for stereo-only meters (prevents a multi-output instrument from showing dozens of meters in the track header).
  • Import->Freesound tab is hidden while we update to the new Freesound search protocol.
  • All user interfaces (Editor, Mixer, Control surfaces, etc.) use the same ordering and visibility. .
  • Empty automation: first point creates a value spanning session start/end position.
  • New style for text entryfields, now including a visible cursor.
  • Make BBT ruler visible in default session.
  • Re-layout import dialog (better fit for narrow screens).
  • Do not show inappropriate dialogs at startup, even if they were visible at the last exit from Ardour.
  • Properly sort port-names into normal human-sensible lexicographic order.
  • Make the trim knob on busses show only if there is audio.
  • Add Open Target Folder button to Export Dialog.
  • Consistent track+group show/hide column layout in the Mixer sidebar.
  • Adjusting a region's gain with the Range and Draw tools would sometimes affect the region in the track above. This has been fixed.
  • Overhauled Region/Range spectrum analyzer: axis-labels, 1/octave weighting, log-scale display.
  • Plugin Analysis graphics: show numeric values on mouse over, and offer A/B plot.
  • Improve shuttle control response when grabbed.
  • Make a right click on metronome really show click preferences.
  • Improve placement of Dropdown popups.

Preferences and other Dialogs

  • The Preferences Dialog is now side-tabbed, with all tabs expanded to make clear the full range of possible settings, and the overall height has been reduced. Sync options have been moved into a sub-node of "Transport". The color theme editor has been moved into its own tab.
  • The Group edit dialog is now non-modal, so its appearance doesn't prevent interaction with the rest of the program.
  • The Shuttle controller GUI drawing has been updated and made themeable.

Control Surfaces

  • Added MIDI map for:
    • M-Audio Oxygen 61 v3 (preset 1).
    • M-Audio Oxygen 61.
    • AKAI MPD32.
  • Updated MIDI map for M-Audio Axiom Air 25.
  • Loop toggle and Roll (play) toggle commands now work as they do in the GUI, for all surfaces.

Export

  • Loudness normalization during export according to EBU/ITU standards. This supplements normalization based on peak sample values.
  • Configurable export-silence trim threshold.
  • Add option to auto-save post-export-analysis image.
  • Align stem-export (When exporting raw track outputs with and without processing).
  • Fix stem-export of no-input busses/tracks.
  • Support for timespan realtime export.

There is an excellent video from Harrison Consoles that shows many different aspects of exporting in Mixbus. Almost everything in the video is relevant to Ardour.

Plugins

  • Adding a multi-channel instrument displays a dialog to configure number of outputs.
  • Allow direct instrument replacement on a MIDI track in a single step.
  • There are a number of powerful software synths in the AudioUnit format for OS X which have multiple output busses, mostly to try to provide some guidance to the user about "groups" of outputs. Although we still question the way this design is used by some plugin developers, 5.0 supports them just like all other AU plugins.
  • Fix listing of plugin presets.
  • Fix incorrect design of VST "in-place" processing.
  • Support AU instrument in-place processing.
  • Fix clearing of AudioUnit cache.
  • Major improvements in handling AudioUnit plugin window resizing, whether initiated by the user, or by the plugin.
  • Handle single-bus, non-variable i/o AudioUnit plugins w/multiple configurations.
  • Provide VST and AudioUnit plugins with latency-adjusted BBT (musical time) information.
  • Set latency of sidechain port.
  • Generic GUI redesign - knobs, grid layout etc.
  • Support for LV2 bypass extension.
  • Listen for AudioUnit plugin-driven latency changes.
  • Add initial MIDI sidechain if plugin has one.
  • Support LV2 log trace messages.
  • Support thread-safe LV2 state restoration.

OS X

  • Fix dialog layering on OS X.
  • Work to reduce the impact of slow down errant plugin GUIs for AU. This is a particular problem for users with Retina displays, because of the unfathomably slow code provided by Apple for drawing images.

Miscellaneous Improvements

  • Bus trim control affects sends to the bus as well as regular inputs.
  • Expand options in quantize dialog to include other beat fractions.
  • Reset autoscroll speed to minimum when scrolling stops.
  • Prevent deletion of last port using the Patch bay dialog(s).
  • Add a try-autostart-engine option.
  • Allow duplication of tracks with sends or load templates with sends/inserts.
  • Adding new tracks (or opening a session with tracks) is now faster.
  • Audio/midi files are now imported to "session start" by default (Too many users report they import their first tracks and can't find them).
  • Record Safe: you can now ensure that some tracks are never record-enabled, no matter what grouping or selection status they may have.
  • Primary-Shift click on gain automation button now sets gain automation state to all tracks and busses (may change in the future).
  • Stop-and-forget-capture should not toggle transport state, only stop it.
  • Once the user has explicitly set the session range end, playlist/range changes do not move it.
  • Various transient-detection fixes (Previously, split region at transients followed by, trim+move+undo would not work).
  • Add option to auto-save post-export-analysis image.
  • Added additional metadata placeholders for post-export command.
  • Switching automation-mode to "touch" writes the current value into the automation from session start to session end. This avoids the case where enabling "touch" on an empty automation track could write the wrong value into automation.
  • Improve midnam (patch and parameter names) for Waldorf Blofeld.
  • ALSA: allow environment variable ARDOUR_ALSA_DEVICE to identify a single, arbitrary ALSA PCM name as the only available/allowed device.

Session sample rate changes

  • Never ever change sample-rate saved with the session after creation.
  • Add notification if Engine Rate changes and mismatches session's SR.
  • Update flow when loading a new session with different SR.

Save As/Snapshot improvements

  • Allow snapshots and Save-As even if session is read-only.
  • Change ambiguous "Save as" window title for "Snapshot & Switch".
  • Start save-as in configured session-di.

Bug Fixes

  • Prevent crash if a VST plugin does not implement effEditGetRect.
  • Issues automating control ports on some midi synths.
  • No more livelock caused by infinite/not-a-number control parameters.
  • Force waveform images to be least 1px wide.
  • "Collect Groups" works again.
  • No waveform flickering during recording.
  • Correct region splits when using Strip Silence.
  • Errors when using timestretch tool.
  • EAN (metadata) check digit calculation is now correct.
  • No more lockup/freeze when deleting a region under specific conditions.
  • Upsampling during import of some multi-channel files will no longer crash.
  • MTC alignment now uses latency compensation.
  • Using "Esc" key now works to cancel more stuff.
  • Gain automation copy/paste works correctly.
  • Various fixes for UTF-8 text entered by users or originating from imported audio or MIDI files.
  • CUE/TOC file creation with non ISO-8859-1 chars in source text now works (by substituting underscores).
  • Remove race condition when dropping ports (especially with Jack 2). Ports would remain and could subsequently cause crashes.
  • Changes in logic used by Session > Cleanup to avoid endless recursion in sessions with deeply nested/recursive compound regions.
  • Single click in TimeFX mode brings up region properties editor, as it should.
  • No more crashes when loading a session with non-default clock modes.
  • Remove "clicks" when switching fader and trim automation from "manual" to "play" while transport is rolling.

Translations

Updated translations for Chinese, (Brazilian) Portugese, French, German, Russian, UK English

Translators:

  • Chinese: Yq-Ysy.
  • Brazilian Portugese: Marcelo Teles.
  • French : edwsaintesprit@hotmail.com, Julien Rivaud.
  • German: Edgar Aichinger.
  • Russian: Alexandre Prokoudine.
  • UK English: Colin Fletcher.

Contributors

The largest group of Ardour developers ever helped make 5.0 possible. They are:

Adrian Knoth, Alexandre Prokoudine, André Nusser, Ben Loftis, Colin Fletcher, cooltehno, Damien Zammit, David Robillard, Edgar Aichinger, feandin, Florian Weimer, Guy Sherman, Hanspeter Portner, John Emmas, Julien Rivaud, Len Ovens, Mathias Buhr, Maurizio Berti, Nick Mainsbridge, Nils Philippsen, pablus, Paul Davis, Pavel Potocek, Robin Gareus, Sam Thursfield, Sebastiaan Lokhorst, Sven Gestegård Robertz, Tim Mayberry, yonideshi, Yq-Ysy

Thanks to everyone who helped make this release possible. Robin Gareus in particular (and as usual) performed veritably Atlassian feats of programming, landing many of the major features mentioned above. Nick Mainsbridge wrestled integrals and floating point math to deliver tempo ramps.

Thanks as usual to Harrison Consoles for their sponsorship of several of the major new features in Ardour 5.0, and their continued collaboration.

Posts: 10

Participants: 8

Read full topic


text What's coming in Ardour 5.0
Fri, 01 Jul 2016 11:45:37 +0000

@paul wrote:

It has been longer than usual since the last release of Ardour, and I wanted to give people a sense of the amazing stuff that we’re soon going to be releasing as part of Ardour 5.0. We don’t have a release date yet, but things are rapidly shaping up and we hope to see 5.0 greet the world in the next few weeks.

Major New Features

Tabbed/Single Window Interface

Possibly the biggest change in Ardour since its first release 15 years ago. 5.0 will allow you to (optionally) work in a single window. The editor window, the mixer window and preferences are now available as "tabs" in a single window, with transport controls shared across them all. Working with Ardour on laptops and other small-screen and/or single monitor systems is now much easier.

views of the tabbed interface

If you have multiple monitors or simply prefer to use separate windows, you can tear off the windows you want, and Ardour will remember your choices in the future.

Control Masters

Although track/bus groups have offered a certain kind of grouped-control over gain, solo, mute and more, traditional mixing consoles have long had group master channels which allow you to combine both a single fader to control the group level while also allowing you to easily adjust the relative levels inside the group. For large projects, this can make mixing much easier to control. After a significant re-engineering effort, Ardour 5.0 will have support for this. In a nod to our "offer more than 1 way to do things" approach, will allow you to use either or both of the conventions used on Solid State Logic and Harrison consoles to chain or combine control masters.

Tempo Ramps

Although Ardour has some uncommonly flexible options for working with tempo, one thing we've never offered are "ramps" - continuous smooth changes in tempo, often known as accelerando (tempo gradually speeding up) and ritardando (tempo gradually slowing down. In 5.0, tempo ramping finally comes to Ardour.

tempo and meter bars showing ramps

Lua Scripting

5.0 will include the ability to write scripts in the Lua programming language that have almost complete access to all Ardour internals. You can implement new functionality of many kinds, including even signal processing (Lua is realtime safe). This release will not feature as much GUI integration as we would like, but it is still a deep and powerful new feature.

an example of a Lua script being edited/used

Much more information on Lua scripting can be found in the manual

Plugin Inline Display

In traditional DAWs, including older versions of Ardour, the only way a plugin can draw anything on the screen is by the DAW opening a new window to display the plugin's own editor/GUI.

In Ardour 5.0, plugins can draw displays "inline" in the mixer strips, giving rise to many new possibilities.

mixer showing several inline displays

Sidechaining & Pin Connections

Ardour's willingess to allow unusual I/O configurations is both a blessing and a curse. On the one hand, it allows users to do creative things that are hard in other DAWs. On the other hand, it causes confusion when doing something as simple as adding a compressor plugin with sidechain support. Those 3 inputs? What are they? How should they be wired up?

5.0 sees an amazing new capability to manually control the internal wiring of plugins, if you choose to do so. You can switch the left and right feeds of a normal 2-channel plugin, or the outputs, or bypass inputs or outputs altogether. Adding "odd" plugins (with inputs and outputs) now becomes possible, with you in control of how the extra (or missing) channels are wired up.

an example of plugin pin connection management

As a pleasant side-effect, connecting up sidechain inputs is now a breeze, which will hopefully encourage more people to take advantage of the benefits of this technique.

Less Major New Features

Themes

5.0 will feature at least 5 different themes, with 4 contributions from users, some of which radically alter the overall appearance of Ardour.

several ardour themes

Record Safe
You can now ensure that some tracks are never record-enabled, no matter what grouping or selection status they may have
Replace Instrument
Ever since we introduced MIDI, it has been absurdly hard to change the plugin used as an instrument in a MIDI track. in 5.0, this will be easy.
Configure Multi-Channel Instruments
Plugin instruments that have more than the typical number of outputs have posed notable challenges in Ardour for a long time, because of the program's willingess to handle arbitrary I/O configurations. In 5.0, it will be possible to take control over how many of the outputs you actually use.
Export Loudness Normalization
It is now possible to normalize during export based on loudness rather than peak sample values.
Support For Multi-Bus AudioUnits
There are a number of powerful software synths in the AudioUnit format for OS X which have multiple output busses, mostly to try to provide some guidance to the user about "groups" of outputs. Previous versions of Ardour could not support these plugins. Although we still question the way this design is used by some plugin developers, 5.0 will support them just like all other AU plugins.

Posts: 28

Participants: 16

Read full topic


text Nightly builds are now for TESTING only
Tue, 31 May 2016 20:40:10 +0000

@paul wrote:

The master development branch of Ardour has recently been merged with two major development branches. These bring major new functionality to Ardour (tempo ramps and VCA masters, among other things), but the result is a new version of Ardour. This version is sufficiently different that it could alter/damage your Ardour configuration files and may not correctly work with existing sessions. We have therefore tagged it "5.0-pre0" so that it will create new configuration folders and not interact with your settings and preferences for older versions of Ardour.

For the time being, the nightly builds should be considered for use ONLY on throw-away material, and should NOT be used to work on existing sessions unless they have been backed up and you are interested in helping us debug issues with the new features (which of course is most welcome).

Posts: 20

Participants: 10

Read full topic


text Ardour 4.7 for OS X updated
Sun, 21 Feb 2016 19:31:39 +0000

@paul wrote:

We have released an updated version of Ardour 4.7 for OS X (technically Ardour 4.7.13). The main release included a bug introduced at the last minute that completely broke the operation of all Command- shortcuts. There are no other notable changes at this time. Anyone who downloaded the original 4.7.0 for OS X should get the new one to avoid this issue. Sincere apologies for the lack of full testing of the changes made so close to the release.

Posts: 1

Participants: 1

Read full topic