Creating a project
*Please note, this page is constantly updated, so information and pictures will change regularly, as we fix bugs, enhance existing features, and build new ones, that will enhance the getting started process.....*
We hope you've had a bit of a browse through our quick start pages, and familiarized yourself with at least some of the components in OOM. Creating a project in OOM is fairly simple, and hopefully this guide will help foster a rewarding OOM user experience.
This page contains the following sections:
- Midi
- Creating Midi Ports
- Setting up Audio
- Create a Midi Track
- Create an Audio Track
- Recording Midi
- Recording Audio
- Global Settings
When you first open a new project, the Metronome window will appear by default, in which you can set the type (Audio or Midi), and volume of the sound you want to hear. For a more detailed explanation of the Metronome, and its functions, go to the wiki page:
Midi in OOM is, like any track based component, comprised of inputs and outputs. In a midi track, the input is usually provided by a hardware device, like a midi keyboard, or controller surface of some kind. The output from a midi track goes to any software or hardware device that is capable of receiving midi data, like a software or hardware sampler. In the examples to follow, our midi input device is a midi keyboard, and the output is the excellent OpenSource sampler, LinuxSampler
An OOM midi track needs the following additional component, which is a midi instrument set (.idf). By default, a midi track in OOM opens with a default GM bank and patch instrument set. Those familiar with the GM standard will quickly recognize the patches.
There is a separate section on creating a midi instrument set, and we recommend you read that first, then come back here.
If you're happy with the default GM instrument set for now in your enthusiasm to get OOM open, then move on to the next section.
Note. We've created default files for working with the CC licensed Sonatina Symphony Orchestra (SSO), called oomidi-templates. If you want a fast and easy setup to see and hear how OOM works, then see the Installing OOM page for instructions on how to install the SSO, and starting OOM from OOStudio, our in-house built Session Manager, and pre-built Sonatina Instrument Sets, and an .lscp file to run in Linuxsampler. Please ensure, if you choose this path, to that you follow the instructions for installing the latest version of Linuxsampler, and associated libs on the same page.
When you've created one or more instrument sets of your choice, if you don't wish to use the standard GM set, go to the menu Global Settings, and select the option Connections Manager. Shortcut is F2
This will open a dialog, and you'll see a tabbed selection of options, being Audio Routing Manager, Midi Port Manager, Midi Sync/Presets, and Midi Assign.
Select the tab, Midi Port Manager
Starting from the top left of the **Midi connections** window, the functions are:
Port This is the number of the port you've created.
GUI For those instruments like softsynths, which have a user interface.
I and O These columns show an icon which represents the capability of the instrument or instrument set to display Ins and/or Outs. Some instruments will only show 1 icon here, and some 2.
Instrument This is the column for your instrument set, and you'll see in empty ports the default instrument is GM. By clicking on the down arrow, a list appears of the instrument sets you have on your system, including the default sets within the app, and those you created yourself.
Device name In this column is the device you create for the port. You can either create a new jack device, or choose from the Alsa devices on your system. OOM is capable of managing both.
In routes Out routes These columns are the external in and out lists for the port device you're creating. If you have created a jack device as an input port, then you can set aliases for example in the Ins port. If you've created a jack device as an output port, then press the outs arrow for the port and a list of currently running jack clients capable of receiving jackmidi will appear, and you choose which one you want to associate with that port.
IMPORTANT: We highlight currently running deliberately. If you use external samples, instruments, input devices, etc, they MUST be active and running before you start OOM.
in ch, out ch partially out of view When these are set to none, the port/device will transmit on all channels for the device. You can change this to the channel of your choice by double clicking on "none", and entering the value for the channel you want.
State out of view This describes the state of the port. when you've done it right, it will say OK!
At the bottom of the Window are 2 buttons, Reset, and Close. Reset will return all the ports to a default state. Close will close the window.
User Tip. It's a good idea to sort out all your midi porting first, as these port/devices will appear in a list to select from when creating midi tracks. Whatever you initially set in the track for the port, and channel number, these can be changed at anytime in the advanced section of the Patch Sequencer tab.
Close that window.
Now the midi is set, we'll need to connect Linuxsampler's audio outputs into OOM, so you can hear what you're playing.
As previously explained we use OOM for orchestral and fim scoring. Like most Daws, OOM can be used for many type of recording and creating, and in OOM, the audio structure is linear, from input busses, to the Master output, as it is for Midi, from input port to output port.
The first step is creating input buss/tracks to accept audio into OOM.
The Input buss accepts JACK or ALSA audio ports, and can be routed inside of OOM to Audio Tracks, Audio Busses, or Output Busses.
To create an Input buss, you have the following options:
- Go to the Edit Menu, and select Add Track, which will open a sub-menu listing OOM's track types. Choose Input. Note that when you add an Input to OOM, the View will change to the Input View.
- Hover your mouse in the track header column, and right click. This will bring up a list of OOM track types, and you select Input.
- Add an Input buss to the track list using the shortcut SHIFT + I
Add as many Inputs as you want, and ensure that no two inputs have the same name. You'll be prompted if you try to do this, and OOM will refuse to accept Inputs of the same name.
Once you've created your Inputs, save the project, then open the Connections Manager again (F2), and click on the Audio Connections tab.
Your inputs will be listed in the centre panel. Any audio output channels from currently running external apps, like LinuxSampler, will appear in the left hand panel as potential inputs into OOM. Select your Input Buss in the middle panel, then select the port you wish to capture coming into OOM, in the left hand panel. If the connection is valid, then you'll see the button marked connect, highlight Green. Click on it, and a new port connection will appear in the bottom panel, showing you have made a successful connection. (The ESC key closes the connections manager). If you've built Mono Input Busses, then only one entry will appear for the Input Buss. If you've built your Input Busses as Stereo, which is the default, then you'll see two entries for the Input Buss.
An input connection into OOM is now created, and can be routed to Audio Tracks, Audio Busses, the MASTER track or any other Output Buss type, or a combination of these.
For the purpose of example at this point, we assume that Input Busses will be routed to Audio Busses, then to the MASTER output buss, to monitor audio generated from midi data being sent.
To create an Audio Buss, you have the following options:
- Go to the Edit Menu, and select Add Track, which will open a sub-menu listing OOM's track types. Choose Audio Buss. Note that when you add a Audio Buss to OOM, the View will change to the Buss View.
- Hover your mouse in the track header column, and right click. This will bring up a list of OOM track types, and you select Audio Buss.
- Add an Audio buss to the track list using the shortcut SHIFT + G
Open the Connections Manager again ( F2 ). In the audio connections tab, a new entry has appeared in the middle panel which is your newly created Audio Buss. Highlight it, and then look in the left hand panel for your Input Buss. Select that, and press the Green connect button. You'll see a new connection appear in the bottom panel.
While you have the Audio Buss selected in the middle panel, go to the panel on the right, and select MASTER. Press connect to connect your Audio Buss output, to the MASTER Input. Again, you'll see a new connection appear in the bottom panel, which shows your Audio Buss routed out to the MASTER.
Select MASTER in the middle panel, and a list of possible playback ports, or audio inputs for external apps, will appear in the right hand panel. The MASTER output is stereo by default, so ensure you make both connections to your external audio input ports. For the purpose of example, route your MASTER outputs to JACK playback ports, usually called something like system playback 1, system playback 2, and so on.
You now have an audio signal chain going from Linuxsampler to the Input Buss, the Audio buss, the MASTER Output Buss, and then out to your jack playback ports.
Once you've created your ports, it's time to create a midi track, and set the in and out ports for it. To create a midi track, you have more than one option.
- Go to the Edit menu, and select the entry Add Track, which will open a sub-menu listing the track types available in OOM. Select Midi.
- You can also hover your mouse in the track header column, and right click. This will bring up a list of track types, and you select Midi.
- Finally, you can simply add a Midi track to the project by using the shortcut Shift + M.
A brief explanation of the functions in a midi track header:
At the top of the header is the name of the track. Hover the mouse over the header and rightclick. Select the menu item Rename Track, to assign a name of your choice.
The knob on the left of the track is the Pan knob.
In the middle of the track is a bar. The three dots on the left of the bar are, from left to right:
The Blue, Pink, and Purple lights are toggle on/off. They don't perform a code base function, but are added as project indicators, that users decide the role for. An example is Blue=Recorded, Pink=Recorded, and partially edited, and Purple=Recorded and edited. We call these Project Indicators, and they provide, for the example given, a quick overview of the state of a track. They are particularly useful in large complex projects.
Between the 2 sets of 3 dots in the Bar is a blank space. This changes to a cream coloured light when midi activity is detected. The dots on the right of the bar, from left to right, are:
Record, which shows Red when selected, and means the track is is a record armed state. Mute, which shows Yellow when selected, and means the track is in a muted state. Solo, which shows Green when selected, which means the track is soloed.
Under that bar is the Gain slider for the track, and under that at the bottom of the header, is the VU meter, giving the user a track based view of levels.
Highlight the midi track so it changes to a darker colour, and then go to the The Conductor tab in the Orchestra Pit.
Setting the midi input port for the track is as follows:
At the bottom of the Conductor tab is a set of controls, where the user sets midi ports for the track.
The dropdown menu is a list of all ports you created in the midi ports manager. Select the port you want as output from the track, and next to that menu, set the Midi channel number, To the right if that is the Input Port icon, and when this pressed, it brings up a list of ports you can use for input into your track.
This picture has been condensed from a large menu for an orchestral template. But it shows the input port as an ALSA usb midi keyboard "MK-249 USB keyboard MIDI 1", and to the right of that the channel selected as input to the track in OOM, as channel 1.
Note: OOM is a generic DAW with the capability of using both jack and alsa ports, in and out, and mixed in a project if desired.
Note that in the right hand list, there an entry called " Set Global Channel 1". This entry is based on the assumption that the user will more than likely input to OOM for all tracks from a single keyboard, on channel 1, so when this entry is checked, it will set the midi keyboard to input for all midi tracks in the project, as input Midi Channel 1.
In the event that users have 2 midi keyboards, for example, 1 for inputting notes and recording midi, and the other to control CC parameters, or keyswitches to select patches, and the user wants the second control input device to input to all midi tracks, then each input device should be set to Global channel 1. The same is true for any combination or number of midi hardware or software devices that the user wants to use for input. Set each device in turn to input, and use the Global Channel 1 entry to have them transmit into OOM, all on channel 1.
Midi Track names in OOM cannot be the same for tracks or busses (OOM will not accept any attempt to do so), so ensure the track name for any track is unique.
Remember:
For any midi or audio track to accept input in OOM, it must be record-armed.
User Tip: At OpenOctave we use OOM to write music with, not just code the app, and we saved time by adding all the midi tracks first, naming them, then opening the advanced tab and, highlighting each track in turn, set the output port for each track. When we'd done that, we went back into one track, and using the Global channel 1 entry, added the input device to all tracks at once. We're using large orchestral templates setup in a "master" template, so there's lots of tracks to add and configure. It may not come as a surprise to fellow users that we decided to add a global input feature for all those tracks at once, instead of tediously doing it one track at a time....
Creating an Audio Track is a similar process to creating a midi track. Once the track is created we route input and outputs. An audio track input comes from Input Busses, and can be routed out to Audio Busses, and the MASTER Output Buss. By default, when an Audio Track is created, it's already routed to MASTER.
To create an Audio Track, you have the following options:
- Go to the Edit menu, and select the entry Add Track, which will open a sub-menu listing the track types available in OOM. Select Audio.
- You can also hover your mouse in the track header column, and right click. This will bring up a list of track types, and you select Audio.
- Finally, you can simply add an Audio track to the project by using the shortcut Shift + W.
At the top of the header is the name of the track. Hover the mouse over the header and rightclick. Select the menu item Rename Track, to assign a name of your choice.
The knob on the left of the track is the Pan knob.
In the middle of the track is a bar. The three dots on the left of the bar are, from left to right:
The Blue, Pink, and Purple lights are toggle on/off. They don't perform a code base function, but are added as project indicators, that users decide the role for. An example is Blue=Recorded, Pink=Recorded and partially edited, and Purple=Recorded and edited. We call these Project Indicators, and they provide, for the example given, a quick overview of the state of a track. They are particularly useful in large complex projects.
Between the 2 sets of 3 dots in the middle of the bar is the letter A. When clicked, this opens a menu with possible Automation lanes for the track. Defaults are Volume and Pan.
The dots on the right of the bar, from left to right, are:
Record, which shows Red when selected, and means the track is is a record armed state.
Mute, which shows Yellow when selected, and means the track is in a muted state.
Solo, which shows Green when selected, which means the track is soloed.
Under that bar is the Gain slider for the track, and under that at the bottom of the header, is the VU meter, giving the user a track based view of levels.
When you've added an Audio Track, open the Connections Manager (F2 ), and select your track in the middle panel. On the left you'll see a list of Input Busses you've already created, so select one, and connect it. While you have the audio track selected, go to the panel on the right, and select which Audio or Output Buss you want to connect your Audio Track outputs to. The MASTER will already be connected by default, so if you want to route the Audio Track to an Audio Buss instead, select the connection to MASTER in the bottom panel, and remove it.
Audio Track names in OOM cannot be the same for tracks or busses (OOM will not accept any attempt to do so), so ensure the track name for any track is unique.
Remember:
For any midi or audio track to accept input in OOM, it must be record-armed.
Recording Midi in OOM can be carried out in both the Composer and Performer. In the Composer, a midi track is record armed, Global record arm is enabled in the Transport bar, or the transport toolbar (shortcut is R ), and recording begins when playback is commenced, either by pressing the play icon the Transport Toolbar, or by pressing SPACE. When SPACE is pressed again, playback is halted, and recording stops, with Global record automatically dis-armed, with a new part appearing in the track.
We've also developed a special engine for recording OOM Midi (and Audio) Called Epic Recording. This enables multiple track recording from one input record, with additional settings for designated program changes, and transpose for specified tracks. To find out more about Epic Recording, go to the wiki page:
For Recording in the Performer, please see the wiki page:
Audio Track
Recording in an Audio Track is the same as recording in Midi. The Audio track is record armed, then Global record armed is enabled. Playback is commenced by pressing SPACE, and recording begins. Pressing SPACE again stops playback, and recording stops, with Global record arm automatically dis-armed. When recording is stopped, a new part will be displayed in the track.
In the Settings Menu there is an entry called Global Settings. you can set overall parameters for running OOM in these pages, and they apply universally, outside of Project specific settings.
*Work in progress.....*