Clone this wiki locally
Welcome to the OOM wiki!
This is the new home for OpenOctaveMidi, as part of the OpenOctave Project, a collaboration to build a professional workflow pipeline in Linux, for orchestral and film based projects.
OpenOctaveMidi (OOM) is a linux-based classic midi/audio sequencer with a look and feel users will find in commercial equivalents. The midi tools are powerful, and available in a user friendly format favourable to a fast and efficient workflow. With alsa and jack midi, and JACK and ALSA audio capability, as well as comprehensive instrument sets the user can build templates to his or her specific needs, OOM gets the admin out of the way where possible, leaving the user more time to write music, and bring their creativity to life.
We continue to improve OOM, and are refining the tools further, adding new features on a regular basis as part of our roadmap, so stay tuned!
Become an OOMidi user today, and we hope you enjoy using OOMidi-2011!
*See the FAQ and Troubleshooting pages for some responses to popular questions and challenges.*
**Note to distro packaging specialists**. We've created an announce mailing list for news and developments for OOM, including announcements for tarball releases. You may miss the thrills and overwhelming excitement of our regular mailing lists, but the announce ML will keep you informed, so you can package from the latest builds. We hope you take advantage of this, and keep all of our shared users up to date with the latest features and developments from the OpenOctave team. Thanks!
To subscribe to the announce mailing list, send an email to:
and then send mail to:
We're still building our manual, but we have some quick start pages you can access now. You can get started in OOM, with the wiki page:
Follow us on Twitter! @openoctave
For occasional updates of where we're at, visit our News page. Please note we don't publish weekly.......
OOM uses icons from the SILK icon set developed by Mark James. We duly attribute Mark with credit for these icons which are licensed under the CC attribution license 3.0.
Legal confirmation done, we'd like to thank Mark personally from the OOP team for this amazing set, and the work that has gone into it. Great stuff Mark, and thanks.
We're always keen to promote the importance of LinuxSampler to the OpenOctaveProject pipeline. It's our professional sampler of choice, and is the powerful engine that drives our substantial sample libs effortlessly.
To find out more, go to:
We've also done a quick start guide to creating a Linuxsampler template:
Mailing lists are up and running, and you can subscribe by sending a blank email with the relevent email address as follows:
For posting to these mailing lists, once subscribed, please use:
You can also find us on IRC at #openoctave (freenode)
OOM is built to run on reasonably solid computers, when combined with LinuxSampler, Jack, and a number of other utility apps.
As tested in the OpenOctaveProject basement/dungeon, we recommend the following as a reasonable hardware and software minimum for professional use:
Dual Core AMD64 X2 5600+ 4GB Ram 3 x 7,200 rpm HD 64mb cache, with one for a system Drive, and the other 2 as dedicated Sample Lib drives. A dedicated professional grade soundcard. A solid graphics card, but run as 2D, minimizing the cycles involved to run graphics. We're using an NVIDIA GTX 550 with the NVIDIA binary driver, but as mileage with graphics can vary wildly, it's up to you to determine what constitutes good performance for your particular use case.
Our window manager is Fluxbox, which is more than suitable in terms of efficiency. We run no desktop icons, or any other functions that may reduce cycles we want dedicated to audio performance. Shortcuts are your friends.
Where possible, we run associated apps, outside of OOM, from the terminal, negating the need to use a dedicated GUI. This is not as disconcerting as it sounds for new users, as, for example, you can build configuration files for Linuxsampler from a GUI, then run the config file from the terminal, saving a lot of CPU cycles and RAM in the process.
With a little effort on the part of the user, and a personal reality check on just how many GUI based apps you want open at once, the above system requirements should yield solid performance results.
The above is only a recommendation, and does not constitute a defined minimum requirement to run OOM on your machine, nor does it imply an endorsement of one hardware or software component over another, save those we use on a daily basis, and have good experiences with, providing the stability and efficiency we set as a minimum standard of professional use, at the OpenOctaveProject.
The OpenOctaveProject team is:
Christopher Cherrett (ccherrett)
Andrew Williams (mistik1)
Goran Mekic (meka)
Filipe Coelho (falktx)
with contributions from Vlada, and our team of users testing OOMidi and giving us great feedback.
If you'd like to join the team, as a contributor, be it coding, or additional important contribution (all tasks are treated with equal importance at OOM, however big or small), then please contact us at: