Ardour 3.0 alpha 1 released

We are happy to announce the first alpha release of Ardour 3.0. This is not the final release of 3.0, and its not even a beta release. Please read more below on what to expect from this alpha version.

What's new in Ardour 3.0?

Ardour 3.0 contains a huge set of changes over Ardour 2.X. The most significant is the addition of MIDI recording, playback and editing support, but you really should take a look at that list to see the full scope of the work that has been done.

It should go without saying that since this is an alpha release we expect there to be quite a few bugs left to fix before we reach a beta or final release. The hope right now is that a month or so of continuous, rolling alpha releases will be followed by a couple of beta releases and then a final release of 3.0 in about 2 months from now. Specifically, Ardour 3.0 itself is not yet feature-frozen, and we anticipate several additions before the beta release.

What do you mean by an alpha release?

This alpha release exists for a few specific reasons:

Session file format now stable

The file format for Ardour 3.0 session files is now stable. This means that we (the developers) promise that work created with this and later versions of Ardour 3 will be usable by all later versions of Ardour 3. It doesn't guarantee that we won't tweak the file format a little bit (though this seems unlikely at present), but it means that if we do change it, we'll ensure that Ardour will continue to load any session files from this release onwards.

We need testers, and complainers and ...

We've had a really great group of people testing Ardour 3 as its been under development, but its time to get more testing, more bug reports, and more comments and ideas. We're not sure that we've done MIDI in the best possible way. We don't know what workflows we handle well at present, and which ones need lots more work. So this release is the first round of asking more people into the "testing pool" to give us feedback and let us know what's broken, what's horribly designed and what works well.

New binary distribution model

On Linux for Intel processors, Ardour 3 (and potentially Ardour 2.8.12) is going be distributed in a distribution neutral format - one package for 32 bit, and one for 64 bit, that will run on any distribution of Linux. We've done some preliminary testing of this to make sure that it basically works, but there's a lot of distributions out there to verify this for.

How do I get this alpha release

Ready to Run binaries

It can be downloaded as two separate binary packages:

After downloading, simply unpack the file wherever you would like this particular version of Ardour 3.0 to live. It can be placed anywhere on your computer's filesystem. Then you can run /wherever/you/put/it/bin/ardour3 (replacing /wherever/you/put/it appropriately). There is no install command, and each package is totally independent, so that if you download a future version of Ardour 3, it will not interfere with this one.

These packages should run on any distribution of Linux with nothing else to install or update. Testing these packages is one of the primary goals of this initial alpha release. BTW, the packages are very large at present because the libraries included have not been stripped, to make debugging easier and more useful.

Source code

There will be no tarball versions of any alpha version. If you want to build Ardour 3 yourself, you should fetch it from svn.

What about OS X

The rather weak development environment for cross-platform applications on OS X has affected our plans on OS X. There will not be any alpha releases available for OS X. The first OS X releases will start with the first beta release - that is, with a version that we think has withstood the first round of widespread testing and is worth using by a larger community.

Distribution Packagers

We would strongly prefer that distributions did not package any alpha release of Ardour 3. We understand that you may have your own reasons for doing so, and that we can't stop you from doing so. However, we will routinely ignore problems bug reports that come from alpha releases not built by us. We intend to release Ardour 3 final this way also, and are sure that there will be some backlash from at at least some parts of the Linux ecosystem over this decision. However, questions about packaging Ardour 3 final are very different for us than the questions about the alpha release stream, and we do ask for your cooperation in reducing our workload in tracking down bugs and problems caused by your own builds of the alphas.

Bug Reporting, Discussions etc.

The first rule of ardour 3 is don't talk about ardour 3 on the forums. There's no code of silence here - its just that web forums are incredibly inefficient ways for the development team to interact with people. So please use these channels to communicate bugs, workflow problems, design ideas and anything else to us:

So exciting!! :smiley:

:slight_smile: Suppppper !

This distribution neutral format for Linux is a godsend. Thanks!
Distributions will keep packaging it and this is great for most people (to ensure stability and updates), but those who want bleeding edge will have a ready and homogenous package to use and test. Just like Firefox :slight_smile: .
(Almost) makes me forget about the bajillion new features in a3. Well, almost.
You rock.

One person likes this.

Cool! I hope to see more, than a segfault. Can’t wait. Thank You!

Great!!!

Congradulations!!!

Are you have any user documentation project for translators? Best idea to have multilanguage wiki here to make easier translation by community.

Great job! going to test it out and report back!

@rusk: we do not use a wiki for documentation, having tried it at least twice and finding that it failed miserably. If you want to contribute to documentation, either directly or via a translation, check the support page for information on the existing tutorial and reference manuals.

@paul

Technically the 2.x reference manual is written in a wiki for the record;) That being said however your point stands of course. I have a different solution I need to chat with you about sometime when I have time to put my thoughts together for 3.x and the manual going forward.

   Seablade

osx-er’s are jiggeling in our pants! linux people work it! we count on you!

Have the binary running on Ubuntu Studio 10.10 right now.

Works nearly the same as well as the yesterday-Build from SVN, only some issues with the GUIs of LV2-Modules.

I will do my best to spread the good news here in Germany :slight_smile:

EDIT:

Runs the same as well on Fedora14/CCRMA. On this it runs with jack2 in a way that could seduce some people to use it for real work.

The progress, Ardour3 made in the last few months is remarkable! Kudos!

Congratulations to all the Ardour team!

@zettberlin I have the same problem, specially with calf-git plugins.

Finally! After years of waiting the alpha is here.

Congratulations on this significant milestone.

Kudos and congrats!

Thanks very much for carrying through on the independent binaries, as you of course know this has been successful already for Mixbus and other commercial applications like Renoise etc. It certainly will very much streamline getting Ardour into users hands and as you alluded to certainly almost eliminate the recurrent bad packaging issues that have nagged some distributions in the past. I’m guessing that the work behind the binary packaging has been as difficult and time consuming as many of the new Audio/MIDI implementations. Anyway a heartfelt thanks for the whole works!!

awesome. congratulations on the alpha. I can’t wait to play with the first Mac beta.

Great news! Keep going!

Freak! I’ve been waiting what seems like an age for this, top work guys.

RESPECT!