Ardour (software)

Recording Ardour's recording abilities are limited by only the hardware it is run on; there are no built-in limits on the number of tracks the user can record to. When recording on top of existing media, it can perform latency compensation, positioning recorded material where it was intended to be when recording it. Monitoring options include self-monitoring, external hardware support (dependent on sound card support), and specialized hardware support (e.g. JACK Audio Connection Kit). Self-monitoring makes it possible to apply plug-in effects while recording. Using the JACK audio, Ardour can record concurrently from both the audio card and compatible software. Mixing Ardour supports an arbitrary number of tracks and buses through an "anything to anywhere" routing system. All gain, panning and plug-in parameters can be automated. All sample data is mixed and maintained internally in 32-bit floating point format. Editing Ardour supports dragging, trimming, splitting and time-stretching recorded regions with sample-level resolution, and supports layer regions. It includes a crossfade editor and beat detection, unlimited undo/redo, and a "snapshot" feature for saving the current state of a session to a file. Mastering Ardour can be used as an audio mastering environment. Its integration with the JACK Audio Connection Kit makes it possible to use mastering tools such as JAMin. Its mixer's output can be sent to third-party audio processing software for processing and/or recording. It can also export TOC and CUE files for creating audio CDs. == Compatibility ==

Ardour attempts to adhere to industry standards, such as SMPTE/MTC, Broadcast Wave Format, MIDI Machine Control and XML. It has been tested on Linux, x86-64, x86, PowerPC and ARM (for at least version 3) architectures; Solaris, macOS on Intel and PowerPC, Windows on Intel architectures and FreeBSD. It takes advantage of all of these systems' multiprocessor, multicore SMP and real-time features. Pre-built binaries of Ardour are available for purchase for Linux, macOS and Windows. It is also possible to build Ardour for free from the freely available source code. Plug-ins Ardour relies on plug-ins for many features, from audio effects processing to dynamic control. It supports the following plugin format and platform combinations: LV2 on Linux, FreeBSD, macOS and Windows; Audio Units on macOS; Steinberg's VST2 on Linux, macOS and Windows; LADSPA on Linux, FreeBSD, macOS and Windows. It is theoretically possible to use plugins created for Windows in the VST2 format on Linux with the help of Wine, but the project team does not recommend it. Since version 6.5, it also supports VST3 plugins on all supported platforms. Unlike most modern 64-bit DAW's, Ardour does not run 32bit VST's natively. Import and export Ardour can import audio clips into sessions from many common audio file formats, including WAV, FLAC, Vorbis, AIFF, CAF, W64, BWF and MP3; SMF files are supported for MIDI import. Ardour can export whole sessions or parts of sessions, and import audio clips into sessions, using its built-in audio file database manager, or directly from an ordinary file browser. == Supporting companies and future ==

The SAE Institute provided corporate support for Ardour until February 2009, an initiative for providing a more integrated experience on Mac OS X and the development of a simpler version for students and others new to audio processing. Solid State Logic employed Paul Davis to work full-time on Ardour during the development of version 2, until the end of 2006. Harrison Audio has supported the Ardour project since early 2005. Harrison's Mixbus DAW, LiveTrax front-of-house multi-track recorder, and their destructive film dubber, the Xdubber, are based on Ardour. Mixbus extends Ardour to add Harrison's own proprietary DSP and a more console-like workflow. The Xdubber was a customizable platform for enterprise-class digital audio workstation (DAW) users. Waves Audio privately supported Ardour development in 2009. It also developed the Waves Tracks Live software in collaboration with Ardour developers, with most of the source code changes becoming part of Ardour's codebase. == See also ==