After more than a year since Ardour 6.9, Ardour 7.0 is now available. This new release features major new features for the software, as well as substantial (even if largely invisible) internal engineering changes. We are happy to bring “clip launching” functionality into Ardour for the first time, along with many other significant improvements, including lots of enhancements for MIDI editing …
This release also sees the addition of official builds for Apple Silicon systems (previously available only via the nightly build site). It is also the end of 32 bit builds for Ardour for all platforms as part of the official download site. Some will remain available on the nightly site for the near-term future.
That’s fantastic news! Thanks to the entire team for the continued hard work on Ardour. @paul I hope you don’t mind that I bring up the following suggestion again now that Ardour 7 is released: On Ardour's home page, add Broadcast and Podcast Producers
This is awesome news!
I got all I need from previous version 6.9, but cant wait too play around with it and find some more tools I can make usable for my workflow!
I use Ardour with JACK all day every day, so “doesn’t work at all on JACK” is not accurate, nor useful. If you’d like us to investigate, please read https://ardour.org/debugging_ardour.html
I did check MIDI clock slaving several months ago, but it has been a while since then. I can check it again, but it will take me a while to get setup - very few of my MIDI devices generate MIDI clock.
As I chose to switch from the subscription model, to a one-time $45 payment, I no longer have access to debuggable versions of Ardour, and are not able contribute bug reports on the latest build. I I’m still in possession of Ardour-7.0.pre0.2610, and can contribute bug reports based off this build.
The linux x86_64 build will likely be back tomorrow. The disk on the build system filled up last night (thanks, PulseAudio log messages … 190GB thereof!)
I note that the implementation of the Cue functionality is different from Mixbus 32C in some ways: there’s 16 rows instead of 8, and it’s a separate window.
I’m also intrigued by “I/O Plugins”. I don’t see anywhere on the GUI for these, but I’m assuming this is academic at this point anyway. Would these be to support what I would call “embedded hardware plugins” like the ones built into devices like the UAD Apollo audio interfaces?
Obviously, such a thing would require software/driver support.
The only difference with the Mixbus 8 cue functionality is the number of slots.
I/O plugins really have nothing to do with embedded hardware plugins. They are normal plugins like the ones you would place in/on a track or bus, but they run outside of the context of tracks and busses. This gives them certain possibilities that are not possible with plugins running in a track or a bus.
That’s very odd. I’ve just launched another old project and found the Cue is inline, as I was expecting. But I have a project where it always opens a new window.
The main motivation is to provide additional I/O. Notably network streams via NDI. Since the feature was made for an Ardour derivative: Mixbus VBM - Harrison Audio Consoles I would no call it academic. However integration in Ardour is not yet completely fleshed out, but some of work has already been done for 7.1.
I/O Plugins can serve as alternative to external applications that one would otherwise be connected as JACK application. Another application would be to use them as input pre-processor.
