OpenOctaveMidi - Le Bottin des Jeux Linux



Title: OpenOctaveMidi Type: Tool
Genre: Development Status:
Category: Development ➤ Musical composition ➤ Sequencer ➤ DAW Commercial:
Tags: Development; Musical Composition; DAW Demo:
Released: Latest : 2012 / Dev : B42cc8c985 Package Name:
Date: 2012-04-04 Extern Repo:
License: GPL v2 Repo:
Perspective: Third person Package: ✓
Visual: 2D Binary: ✓
Pacing: Real Time Source: ✓
Played: Single PDA:
Quality (record): 5 stars Quality (game):
Contrib.: Goupil & Louis ID: 14339
Created: 2014-06-19 Updated: 2020-02-09


[fr]: Un séquenceur Audio/MIDI classique basé sur linux avec un ressenti utilisateur équivalents à des produits commerciaux [en]: A linux-based classic midi/audio sequencer with a look and feel users will find in commercial equivalents


Trailer / Gameplay [en] / [en] / [fr] :


Website & videos
[Homepage] [Dev site 1 2] [Features/About] [Screenshots] [Videos t t t t t t t t t t g g g] [WIKI] [FAQ] [RSS] [Changelog 1 2]

Commercial : [Support their work (Donate)]

• (empty)
Technical informations
[Open Hub] [OpenOctaveMidi (The Composer's Toolbox)]

Devs (Open Octave Project [fr] [en]) : [Site 1 2] [twitter] [YouTube] [Interview 1 2]
Game : [Blog] [Forums] [twitter] [YouTube]

On other sites


News / Source of this Entry (SotE) / News (SotN)

Description [fr]

Un séquenceur Audio/MIDI classique basé sur Linux avec un ressenti utilisateur équivalents à des produits commerciaux, par l'Open Octave Project.

OpenOctaveMidi (MOO) est une Digital Audio Workstation (DAW, aka station de travail audio) basée sur Linux (et cherche à être multi-plateforme) conçue pour donner aux musiciens les outils nécessaires pour composer sur un ordinateur, et même être amusante !

OpenOctaveMidi est un séquenceur Audio/MIDI classique basé sur linux avec un ressenti utilisateur équivalents à des produits commerciaux.
Les outils MIDI sont puissants, et disponibles dans un format convivial favorable à un flux de travail rapide et efficace.
Avec ALSA et jack midi, et des capacités audio JACK et ALSA, ainsi qu'un panel complet d'instruments l'utilisateur est à même de mettre au point des modèles pour ses besoins spécifiques, OOM prend en charge la partie administration lorsque c'est possible, laissant à l'utilisateur davantage de temps pour écrire de la musique et donner vie à sa créativité.

Nous sommes un projet open source (licence GPL v2), OpenOctaveMidi est donc libre. 

Description [en]

Open Octave Midi is a Linux based (looking to be crossplatform) Digital Audio Workstation (DAW) designed to give musicians the tools needed to make composing on a computer possible, and even fun!

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!
We are an open sourced project (GPL v2 License), so using Open Octave Midi is free.

What does the Open Octave Project do for me?

We're bringing together a collection of applications, and developing our own, to provide a professional working environment that does the following:

• Enables users to work within a dedicated audio/midi projectbase, primarily for orchestral and film score use.
• Monitors closely developments within our applications of choice, and provide feedback to proactive developers, in a positive and constructive manner.
• Develop further, or build from scratch, applications with added or modified tools, with the intent of creating a continuous, efficient, and powerful workflow, from "A to B", removing as many obstacles or workarounds as possible.

We are focused on orchestral and film writing and recording, as a daily professional working environment, and are examining in fine detail the process of inputting, editing, and recording, to give a user the best possible opportunity for a smooth, unhindered, and efficient experience, maximising their productive time, and minimising where possible any non productive time, in a real use case scenario. We don't like workarounds anymore than anyone else, so we're keen to avoid or remove them, where we can.


☑ The Conductor

A comprehensive engine to make multiple bank and patch insertion into the timeline a great experience. Make chains of patches, and quickly and efficiently add the patches in the ruler. Click another patch, add it manually, then start the sequencer again.

User created Round Robin sequences are more than possible, and bring a change from Sample Lib created Round Robin files that play the same way every time.

The Conductor was designed and built by the OpenOctave team. It performs a very important function as part of the overall workflow, and that is the management and automation of bank and program changes. For experienced Midi writers and users, the handling of extremely large and complex sample libraries is always an important consideration in workflow. For an orchestral writer, who might insert several hundred, or thousands, of program changes in a project, often with repetitive sequences, i.e. Up and Down bows for strings, the workflow process is often extremely time consuming. The Conductor is built to take as much of the "donkey work" out of program change data input as possible.

☑ The OpenOctave Orchestral Template

Out of the box orchestral scoring is now a reality with the oomidi-template. Powered by the Sonatina Symphony Orchestra, the oomidi-template opens a new world for users, whether it's scoring for YouTube, your first indie projects, or full feature film.

☑ OpenOctave Studio

The Open Octave Studio becomes the heart of your audio setup. This innovative new session manager truly is a breath of fresh air! In one word... Easy!

OOStudio is our in-house OOM session manager, and has been built to reduce the administration of starting an OOM project session which incorporates multiple applications.
OOStudio is a one action session manager, that automatically starts applications in a specified order, bringing up an entire OOM project session. From initializing Jackd to starting OOM with a designated project, OOStudio goes through your session profile step by step. Once up and running, OOStudio sits in your toolbar as a tray icon, and you can access it at any time to check the status of your session. As well as the OpenOctave Project core applications we use, you can also add, in the custom commands section, other external apps that you wish to run in the session.

In addition to the above, users can switch sessions whenever they wish by bringing up the OOStudio GUI from the icon in the dock, selecting a new session, and opening it. The previous sessions will be closed, and the new one will commence. Right click the icon and select Restore. If you're opening a new session while the previous one is still running, and you haven't saved, you'll get a prompt asking you to either save or not.

When a new session is created, and run, OOM opens with a project of the same name. Each session is saved as a folder, and all the files associated with that project are stored in the same folder, so an OOStudio session is completely independent of other sessions.

OOStudio also has an import a session or template feature that gives you the real security of back-up sessions. When you've created a session that you wish to backup, select it in the create new tab from the Template drop down menu, which will create a copy of the Template or Session, as you will see in the Name field, rename it with something like "My Masterpiece-backup-10-2011", then specify your backup location. Easy.

If all goes wrong in your system for some reason, you can import the backups directly into the session directory in the Open tab, and you're off and running again.

☑ Our new Midi Assign engine

A truly generic surface engine in which users can build specific CC assignments for control surfaces, can release the true value of using a specialised control surface, complete with feedback support, and a unique and intuitive learning method to give you complete flexibility.

The midi assign feature in OOM is unique, in that it is truly generic. Users can build midi assign presets for any control surface, and project templates. As well as midi learn applied to any midi control type, including Record, Mute, and Solo toggle functions, users can transmit data sets from their control surface to OOM via the nrpn checkbox in each control strip, and Midi Assign will also accept sysex data transmitted from their control surface. (We've tested this with a couple of different midi keyboards with multiple knobs and buttons, as well as the popular Behringer BCF2000 control surface.)

☑ New Epic Keyswitch Engine
For allocating patches to keyswitches. You can now bring your favourite patches together in one efficient workflow, and by harnessing the power of single touch keyswitching, you can effectively use your keyboard controller to switch between articulations with one hand, while inputting your Epic score with the other.

The Performer

If the Arranger Window is the panoramic view of your project, then the Performer is the workshop. It's in this pianoroll style canvas where dedicated midi users do much of their work, shaping and molding a midi performance with the primary tool of their trade.

The Performer is, using the same analogy, a complete toolset. Any midi data can be inputted, edited, or removed. The Performer can display several parts at a time, doing away with the need for multiple part windows.

Where possible in this page, we've tried to keep images a natural size, within the limitations of the wiki page dimensions.

This page describes static functions, toolsets, and functions in the Performer.

☑ A completely new colour scheme

For easy track and part recognition. Choose from over 100 professionally designed colour matches that provide unique visual cues throughout the entire project, no matter how busy your masterpiece may be.

We've given each colour a unique name, making them easy and fun to identify, and remember.

The Composer
The Composer is the user's overall picture of his project. Here, he can set global project settings, record music, data, automation, in a canvas that contains all the tracks he has in his project. The Composer is linear, and tracks are read and played from left to right. OOM differs a little from other sequencers, with the resource centre on the left, which is tabbed, and contains all information about a specified track, our unique designed and built OOM Patch Sequencer, with which the user can automate much of the work involved in handling large sample library banks and patches, and the global feature TrackViews, which has also been designed and built by our own team at the OpenOctaveProject.

☑ The Orchestra Pit

Consolidates all of your most important functions and configurations into one easy to use and easy to navigate environment, featuring Epic views, single track mixer, the Conductor, Comments, and routes.

The Performer Orchestra Pit features the Conductor, Tracklist, and Note info, ensuring you're in touch with all your essential project requirements.

The Orchestra Pit is the docked panel on the left of the Composer window. There are multiple tabs, each one for a different function, set of functions, or OOM feature.

Note. If you close the Orchestra Pit, you can open it again by rightclicking on a blank area on OOM, and selecting Orchestra Pit.

☑ Track headers have been redesigned with you in mind!

Complete control of gain, pan, automation, record, mute, solo, as well as three user defined project management buttons from one small and compact interface, that adjusts it's controls with the height of the track. Monitor midi input and vu levels as well as quickly identifying full header length tracknames at a glance.

The OOM design structure is by track type. In addition to this, track types can be viewed as mixer strips, not only in the Mixer and MixerDock, but in the Orchestra Pit as well, by clicking on the Mixer tab..

Tracks are colour coded for easy identification, so the user will quickly identify what type of track they're looking at. The Track header colour matches the track's associated mixer strip, so retaining a continuity of visual recognition.

In addition the above, Midi and Audio track parts can be organised visually using OOM colour scheme by setting the default part colour in the track header rightclick menu. Part colours can be changed at anytime, and you can have more than one part colour in the same track.

See the section at the bottom of this page for the OOM track and part colour scheme selections.

☑ Cool new Fade In / Out and Auto Crossfade design

With sample accurate transitions you can quickly see how much fade is applied.

☑ The Tracklist

Puts the professional Midi Composer in one window, from project creation to finish. Edit in the Performer with multiple part input, edit and remove, create and delete parts, Epic recording, and much more.

The TrackList is a powerful part management system unique to OOM, and integral to great workflow in the Performer.

We've compressed and reduced the window size of these images to fit in the wiki, as we're presenting function. If you have a widescreen monitor, for example, you'll have plenty of canvas to work in, and as the saying goes, it's a joy to behold.....

The Tracklist is one of the most powerful features in OOM, and was specifically created to present and display not only currently loaded parts in your project, but all tracks, even if no parts are present in those tracks.

With the Tracklist feature it's entirely feasible to add a single part to a single track in the Composer, then do the rest of your midi work in the Performer window, including creating new parts for tracks on the fly. Tracklist makes that possible. Those experienced in working with MIDI will know that midi/audio applications tend towards a generic workflow approach to all components of working in DAWs towards the Main window, rather than specialize in project and part management workflow for all components, especially those as important as Midi Editing windows.

Tracklist removes that limitation.

Here at the OpenOctaveProject, we usually have the Composer open in one workspace, and the Performer open in another, all fullscreen. From experience, more time is spent in the Performer, and if, like a couple of us at least, you can read MIDI pianoroll style canvas as easily as reading notation, then it's a natural thing to do, and great workflow, in our humble opinions.

Multiple parts can be viewed in the Performer by clicking on the multipart icon in the Epic Toolbar. This action is global for the Performer, so it regulates the display of a part or multiple parts selected from the Tracklist.

☑ Epic Views

Our brand new feature that makes multiple track transposed recording in one pass a reality, with Epic strings, Epic brass, and Epic choirs as examples of the power of using Epic views, and brings massive time saving workflow to you.

No more recording the same line in several tracks one at a time.

Create an Epic view, hit Record, and play. Easy.

Epic Views are a powerful engine in the OOM feature set, and form a significant component in OOM's excellent workflow.

Epic Views is an OOM custom designed and built feature engine with one task, which is putting the user in complete control of his project.

With Epic Custom Views, the user can put Tympani next to Contrabasses, Oboes next to Choirs, and, well, the choices are unlimited. It's up to you. Custom views can be created or removed at will, and any type of track can be added to any custom view. The user might want to keep all his 1stviolin midi tracks with the 1stviolin wave tracks, and busses, and auxes, and, well, any combination.

Epic Views are simple and easy to use, requiring only a click to turn them on and off, and will mix and match to the user's requirements, with multiple custom views checked.

Epic Views live in the Orchestra Pit on the left of the window, and the tab is marked Epic Views. Simply click on the tab to open the Epic Views window.

☑ New Main Mixer

With multiple row selection, mixer strip expand and contract, either individually, or globally, 1024 plugin slots, and more, gives you a truly customised overview of your entire project, harnessing the true power of Epic Views.

The mixer is a detailed view of all the tracks and buss tracks in your project. The mixer can be more clearly defined by the user to show what he or she wishes, with an View menu in which the user can check on or off by track/buss type.

As well as Views, our Mixer can show your Custom Views as well, and you can use the Mixer OrchestraPit dock on the left to select which view, or combination of views, you'd like to see visible.

A special thanks to Grigor Iliev from Linuxsampler. His rack design in Fantasia was the inspiration for the OOMidi Mixer and MixerDock racks.

☑ Extensively redesigned Automation

Features, including easy to grab nodes, instant node creation and removal, and Copy/Paste Automation sections to another part or section of another track.


Automation has had varying degrees of success in many apps, more often than not, in the way it's presented to the user. Some apps will use bezier curves to present automation data and a means of edit to the user, while others will use straight lines between "nodes", and the user can add as many as they want to create nice curves, or silence noise, and other artifacts in a recorded wave. Automation is, in more than one case, poorly presented, with tiny nodes making it hard to locate and select with a mouse, cramped automation tracks or lanes, and often badly functional management of multiple lanes in a single track.
We've opted for a simple approach in OOM that's clear and easy to use, and decided the user should have the choice where and how they want to manipulate automation data, without the often remarked comments about bezier curves, in that they can distort the data either side of the edited node. Either way suits some users and not others, and both are valid for particular use cases, but for editing artifacts out of waves, a set of straight lines is a definitive function, and so, in OOM, that's what we considered important enough when building the automation. At some stage in the future, we'd like to have both formats in OOM, so all users have a choice, but this won't make it into the next release of OOM.

☑ New Mixerdock

Seemlessly works together with EPIC Views to instantly provide a mixer strip view of your tracks in the Composer, and makes checking levels a workflow delight.

Why have one mixer when you can have two?

OOM, in addition to the main mixer has a unique docked view in the Composer, called the MixerDock. It opens at the bottom of your screen, and can be detached should you wish to put it somewhere else, common with generic dock behaviour.

☑ LV2, Ladspa, and DSSI effect plugin support

And a completely new plugin manager with intelligent filtered search functions.

OOM supports LV2 (effects), and Ladspa effect plugins.

Note: The LV2 plugin format is going forward at a rapid pace. SLV2 has been replaced with Lilv. We run OOM with SLV2 NOT installed, and use the new Lilv lib instead with success. If you have SLV2 installed, OOM will use it, but your mileage may vary, and as SLV2 will no longer be developed, we won't support any SLV2 oddities that may occur.

Please Note. The CALF plugin team have been providing Linux users with excellent LV2 plugins. We've had a report that a couple of the older versions are a little problematic at the moment. The latest git builds are being used at OpenOctave, and they work fine. You can find the git repository at: git clone

☑ Import midimaps directly from Linuxsampler

With our unique Import Instrument feature.
No more building your large sample library banks and patches twice.
Do it once in Linuxsampler, and Import Instruments creates a matching Instrument Set.
A massive time saver!

OOM has a powerful feature called instruments sets. This is a complete file you save for each instrument you choose to build.

By default, OOM has 3 .idfs in the instruments directory. These are GM, GS, and XG.

This wiki page describes the function of the instrument set, and how to create your own. Our working environments here at the OpenOctaveProject involve almost exclusive use of LinuxSampler, with large sample libraries, so we've added a section, detailing the use of our LS automated Import Engine.

Instrument Set Manager

OOM has an fundamental midi structure that relies on a instrument set.

There are default instrument sets in OOM, but the Instrument Sets Manager enables the user to build their own instruments sets, according to requirements. This window is a list of current instrument sets built by the user.

In the picture below, as an example, and as well as the default sets, there are 3 complete orchestral groups of instrument sets, 28, 40, and 128, so the number of sets you can create is, well, unlimited.

OOM uses the *.idf format for instrument sets, and you can set the default directory to store your sets in the Global Settings menu.

Installation [fr]

Un dépôt UBUNTU est disponible sur le site Launchpad (lien "Dev site 2" ci-dessus).

Test [fr]

Commentaire généraux :
Note de l'auteur du Bottin : OpenOctaveMidi semble être un formidable projet, néanmoins - de mon point de vue, il manque un accès aisé à son installation via dépôt Debian (les dépôts UBUNTU posent parfois des soucis de compatibilité avec d'autres distributions telles que Debian du fait de dépendances non disponibles).
Si vous avez les compétences nécessaires, n'hésitez pas à créer/proposer des dépôts/paquets pour les autres distributions.
Un tel outil - aussi soigné, ne peut se contenter de proposer des souces (souvent difficiles à compiler/installer du fait de nombreuses dépendances qui nécessitent des compétences qui ne sont pas à la portée des musiciens) ou de dépôts UBUNTU, il mériterait largement son entrée dans la distribution Debian.
Il serait vraiment dommage de laisser mourir un tel projet.