Skip to content

Installing OOM

Jump to bottom
alekz49 edited this page Oct 10, 2011 · 167 revisions


This quickstart manual is defined as ongoing, and as a result, we offer no responsibility for errors or omissions, as we build it.

Once you've successfully installed OOM, and you wish to start your OOM journey, go to the Getting Started wiki page here:

Getting Started

Please Note. Remove ALL older oomidi files, including old config files, before installing OOMidi-2011. We've made some structural changes that are NOT compatible with older versions. Thanks.

If you've previously installed OOM in /usr/local, then files will be found in:

  • /usr/local/bin/*
  • /usr/local/share/*
  • /usr/local/lib/* (If a 64bit install, /usr/local/lib64/*)
  • ~/.config/OOMidi (Remove or move the OOMidi folder)
  • ~/.oom

Download the OpenOctaveMidi-2011 source code from here:

OpenOctaveMidi-2011



OpenOctaveMidi is an opensource project, licensed as GPL v2.

See below for confirmation that distro specific OOMidi-2011 packages have been built by distro packaging specialists. We supply the source code tarball, and they do the rest. Note that in accordance with trademark or licencing policy for the use of TM or other licensed logos on our wiki, we confirm we have no direct affiliation with the logo rightsholders of a formal nature, but an informal one in the spirit of working together as part of the greater Linux community.

The following Linux Distributions have pre-packaged binaries of OOMidi-2011.

KXStudio
Arch-AUR


Packagers Latest tarball is OOMidi-2011.3.1 (7th October 2011)

We also have a twitter feed to notify everyone about upcoming releases and developments @openoctave


*This page contains the following sections:*
  • OpenOctave Midi and Audio Sequencer
  • Installation
  • Requirements
  • Template Set
  • Install Sonatina
  • Compiling from Source
  • Starting OOM from OOStudio
  • Starting OOM

OpenOctave Midi and Audio Sequencer (OOM)

OOM is a linear midi and audio sequencer for Linux operating systems, both 32 and 64bit, licensed under the GPL-V2. Although some comparison could be made with commercial applications, like Cubase and Logic (Not to be construed as an endorsement of these applications), OOM was, and continues to be, built as a tool of use for composing, writing and recording midi and audio, and this defines it's role most clearly.

The Quick-Start manual is intended as a guide for users to get them started and running using OOM.

Introduction

Using a DAW, like OOM, to record and compose music isn't a new idea. Since computers first used a monitor, the concept of producing music of some sort or other has had a prominent place in the exploration of possibilities using a computer to perform tasks. And in this context, and that of a DAW, the computer continues that role, as a tool of use. The same was true of the software, with a significant evolution of music based applications from DOS, and command line applications, to the complex graphically based interfaces we've come to assume is normal today. As hardware gets faster and more powerful, so software is written to exploit these attributes, and hardware and software regularly swap places in the priority with hardware more powerful, then software attempting to exceed hardware capability.

In the OOM build philosophy lies a common truth. The user experience is paramount. OOM may not be replete with iridescent, heavily saturated colors, or buttons that sing and dance when you press them with the mouse. That's not our goal, nor will it be in the future. OOM is 2D, functional, and the user workflow is powerful and user configurable. We seek to put the tools in the user's hands in the most efficient manner possible, and as we use OOM on a daily basis at the OpenOctaveProject, we're just as enthusiastic to reduce the number of unnecessary actions the user needs to use to perform a function, navigate, and perform the 3 essentials of DAW use, Input, Edit, Remove.

So you won't find endless menus, sub-menus, sub-sub-menus in OOM, or a small army of popup windows to deal with. OOM does what it says on the tin.

In that spirit, let's continue.....

Installation

Our preferred Linux distro type is Gentoo. Using a Gentoo ebuild is simple, and source based. The OOM ebuild will pull in the required dependencies to build OOM. We have our own overlay, which Gentoo users can install as root with the command:

layman -a oomidi

For those who want to build from source, ensure you have the following installed.

Please note. If some distros provide specifically built packages for OOM, those distros may split required libs and packages into something like “foo”, and “foo-dev”, so you may need to search for development packages if this is the case. We do not support or answer queries for distro specific problems or challenges. Please communicate with your distro packaging specialists.

OOMidi is distributed under the GNU General Public License (GPL).

Requirements

Note. LV2 has changed its libs fairly recently, and we've built the host structure for LV2 in OOM based on LILV and its associates. The older SLV2 lib, if installed, will take precedence as a legacy fallback, however we're not supporting SLV2 going forward, and will continue to finetune LV2 effects support in OOM based on the LILV libs. If you wish to take advantage of the stable and more modern LILV libs for LV2, then turn off SLV2 in the cmake file, or uninstall SLV2, and install LILV instead, as a more general update for LV2 across your system.

Gentoo users will find ebuilds for the LV2 libs in our oomidi overlay. Other distros may, or may not, have the latest builds. If in doubt, install from source by downloading the 4 libs from www.drobilla.net.

Template Set

The oomidi-templates are installed globally when OOM is installed, and will appear as a default template in OOStudio.

To function properly, the oomidi-template requires a correct installation of Linuxsampler with the SFZ engine compiled in the app.

Ensure that you download and install the latest version of Liblscp, which can be downloaded with:

svn co https://svn.linuxsampler.org/svn/liblscp/trunk liblscp

Ensure that you download and install the latest version of Libgig, which can be downloaded with:

svn co https://svn.linuxsampler.org/svn/libgig/trunk libgig

Note that libgig must be installed before linuxsampler.

The latest build of Linuxsampler can be found in their Subversion repository, and can be downloaded with:

svn co https://svn.linuxsampler.org/svn/linuxsampler/trunk linuxsampler

cd to each directory in turn, and build the apps from there.

Follow the instructions in the included INSTALL files for each download. Note that the following command will need to be issued first, in each case, in order to create configuration files from svn downloads:

make -f Makefile.cvs

Once you've built Linuxsampler and the libs, and got everything correctly up and running with GIG and SFZ support, then you're ready for the next part of the process.

Note that if you install the 3 Linuxsampler builds from a repo, the builds MUST be the latest svn builds. In Gentoo, we can do this with the "9999" ebuild. If your distro based versions are too old, then you'll need to build from svn, as described above.

Install Sonatina

We're still trying to find a more permanent home for the SSO, but for the time being, you can download it from:

[ Sonatina-Linux ](http://www.zshare.net/download/928804050b47c140/ :target="_blank" )

(Right-click this link and select open link in new tab, to open as a new tab in your browser)

Sonatina (SSO) is a CC licensed Sample library of fairly modest size (just over 450MB) built as an Orchestral set, in SFZ format.

The sequence to install Sonatina in the correct directory is as follows, and we assume you've downloaded the archive to a folder called Downloads in your home directory:

1 Open a terminal, and type:

 cd ~/Downloads

2 Install the SSO with the following command:

 sudo tar xjf sonatina1.tar.bz2 -C /usr/share/sounds/

3 You should now have the Sonatina library installed on your system, in /usr/share/sounds, and you can check this with the command:

 ls -lah /usr/share/sounds/

Compiling OOMidi-2011 from source

or just use a graphical de-compressor to unpack it somewhere.

To compile OOMidi, run the following command from the top level directory where the source code was unpacked (the directory where the README file is):

    ./compile_oom.sh

OOM is installed by default into /usr/local.

Then cd into the build directory with:

     cd build

Compile OOM with the following command:

  sudo make install

Starting OOM from OOStudio

The instructions described here, for using the default OOMidi-templates, rely on a correct installation of Sonatina SFZ sample lib, and the latest builds from svn of the Linuxsampler libs, details for which are further up this page.

To start the default oomidi-template session, type:

    oostudio

Select OOMidi_Orchestral_Template from the dropdown Template menu, then name the session, and give it a location.

Press the create new button at the bottom of the window, and a dialog will open asking you if you want to run the session now. Press OK.

OOM will open after Jack and Linuxsampler, and you'll see OOM open with the name of the project session you just created.

There are three more steps to take before you get sound, and they are:

  • Connect your midi keyboard into OOM
  • Connect your Audio Outputs from OOM
  • Define your midi input for midi tracks

Open the Connections Manager from the Settings menu, or by using the shortcut F2

Select the Midi Ports Tab. You'll see existing midi output ports to Linuxsampler, and you'll need to create a new port for your midi input.

Go to the first undefined midi port in the list.

In the column D-name, press the little arrow, and a list will come up of your ALSA input devices, and any JACK midi devices if you're running -Xraw in Jack. Select the entry that is your midi keyboard, or midi input device. Go to the row of buttons on the left, and press the button in the column I (This denotes input) Make sure the O button is not green, but dark. (off)

Select the Audio Connections tab, and in the middle panel at the top, select Master. There will be 2 entries as our MASTER output is stereo. In the right hand panel you'll see a list of jack ports you can connect to. Select 1, and press connect. Choose the other Master entry in the middle panel, go to the right panel, and choose another jack port, then press connect. In the bottom panel you should have 2 new entries showing Master connected out to your system playback ports, quite possibly system:playback_1, and system:playback_2.

Final step.

Select a midi track, and press the Conductor tab in the Orchestra Pit on the left. At the bottom is a ports section, with a dropdown menu for assigning the output port to a track, a midi channel selector that you set to the channel you are sending midi data out from, and a midi input icon.

Press it, and a list of ports will come up in a menu. Choose the Midi Input port you just created, and follow into the sub-menu. You'll see a list of midi channels, and an entry near the bottom called Set Global Channel 1 Select this entry.

Global channel 1 sets the midi input channel 1 to all ports at once, or as the name implies, globally. We put this in so you only have to select the input once, instead of doing it for each and every track, manually.

Remember:

OOM tracks will only accept input if the track is Record Armed.

Go to the track header you selected and press the Record button. It will show red.

Play your keyboard, and you should have sound.

If there's a problem then go through the steps again, and make sure you built your midi input port, and connected the audio output ports, correctly.

The team and fellow users can be found on IRC, at #openoctave (freenode)

Starting OOM

OOM can be started by typing:

        oomidi

You can also start OOM with options and an existing project file, or midi file. Example:

   oomidi ~/audio-projects/myfile.oom

The following is a list of options OOM will take:

-a start in midi-only mode

-d debug mode: no threads

-D debug mode: enable some debug messages

-m debug mode: trace midi Input

-M debug mode: trace midi Output

-s debug mode: trace sync

-P set real time priority to n (default: 50)

-p don't load LADSPA plugins

-v print version

For most users, the majority of these options will be unnecessary, but may prove useful to experienced linux users with some debugging skills who have encountered a local problem.

  • OOM Configuration File /home/user/.config/OOMidi/OOMidi.cfg
  • Hidden Project File; stores list of last projects /home/user/.config/OOMidi/projects
  • Instrument folder of instrument sets /home/user/.config/OOMidi/Instruments/

OOM recognizes the following file types:

Default OOM format

.oom

midi file; can be imported and exported

.mid

karaoke: midi file with additional information; some types can be imported

.kar

Stored midi parts, these are an alternative way of storing structures in OOM.

.mpt

Stored plugin presets

.pre

known bugs = quite a few!

Let us know whether OOMidi works for you !!!

Have a look at the webpage http://www.openoctave.org for details.

Work in progress.....

Quick Start Manual Index

News

Home

FAQ

Troubleshooting

Installing OOM

Getting started

Creating a project

The Composer

The Performer

Working with Midi

Working-with-Audio

Mixer

Shortcuts

Creating MIDI Maps

Linuxsampler

Participate

Links

www.openoctave.org

www.linuxsampler.org

Clone this wiki locally