Introduction
In this companion article, we’ll discuss how to import MIDI data from your notation software to your Digital Audio Workstation in order to create beautiful, broadcast-quality mockups using Spitfire Audio libraries. Many composers prefer to start writing or scoring in a notation program rather than scoring directly in their DAW. The advantage is that when the music is handed to the orchestrator or score producer, there is less meticulous work to be done as scores and parts would not have to be extracted from a mockup. Rather, the notated score informs the composer in their efforts to create realistic mockups that accurately portray their musical ideas.
The Problem with Notation Software
Unfortunately, there are many shortcomings associated with notation software. For example, getting realistic-sounding playback in a notation program is extremely difficult. While sample-based playback engines like NotePerformer by Wallander Instruments are able to provide vastly better playback than general MIDI, they still cannot produce a pristine, authentic-sounding mockup. Most notation programs do not include a way to easily load plugins; thus, Spitfire Audio Products are generally not designed to be compatible with notation software (with the only exception being Dorico by Steinberg). This is why composers prefer to work with sample libraries and virtual instruments when creating a mockup because they can quickly and efficiently achieve a broadcast-quality demo.
There are two methods of creating a mockup in a DAW from a notated score. One method is to manually play each part into your DAW by hand using a MIDI keyboard. This method requires excellent keyboard and sightreading skills. Even then, a composer with advanced musicianship may struggle to get a good recording making this method impractical and inefficient. Another method is to export a MIDI version of your notated score so that it can be imported into your DAW. Then any composer with decent orchestral programming skills can edit the MIDI data in their DAW to create an ultra-realistic demo. It should be noted that these instructions apply to any major notation software or DAW.
Composers who prefer to work with notation software only, and are looking for a free solution should check out MuseScore. MuseScore 4, a free, open-source notation software, has been refreshed with an incredible-sounding playback engine and the ability to load plugins allowing the user to load instances of third-party sample libraries and audio effects plugins. For those who are looking to get into orchestral programming and are looking for free DAW options, please see the list below:
Importing MIDI from Notation to DAW
To import MIDI data from notation software to a DAW, you’ll need to create a “MIDI Friendly” version of your project file. Elements of music notation such as dynamics and expression, slur markings, etc., do not translate well when converted to MIDI. Only time signature, key signature, tempo (including fermatas and similar symbols), pitch, and rhythm information translate correctly to MIDI. Additionally, most notation programs automatically add default panning and leveling information which must be neutralized in order to start programming in your DAW:
- Once you have finished writing in your notation software, duplicate the project file and add “MIDI” to the filename of the duplicated project.
- Open the duplicated “MIDI” project file in your notation software and remove all unnecessary elements of music notation as discussed above.* You should be left with time signature, key signature, tempo markings (including fermatas and all similar symbols that affect tempo), and pitch/rhythm data.
- Open the mixer in your notation software and neutralize all settings: set panning to zero, and set all faders to 0.0 DB.
- Next, export your MIDI-friendly project as a .mid (MIDI) file.
- Open the .mid file in your DAW of choice.
*The reason we remove dynamic markings and hairpins from your notated score is that these markings will appear as volume automation data in your DAW instead of dynamics and expression automation from within a sample library. We need to access the library parameters in order to create a realistic mockup; volume automation is not suitable for adding convincing expression.
By default, most DAWs will load stock plugins and audio effects in each track when you import a MIDI file. You’ll need to remove those stock sounds and replace them with the Spitfire Audio library that applies to the track in question. In the video tutorial, I’ve used Spitfire Appasionata Strings, a dedicated plugin library. It should be noted that you can use our Kontakt-based libraries as well. Once you have loaded the libraries, you are free to start programming your composition. Orchestral Programming can include the following:
- Adding dynamics and expression automation via a MIDI Fader Controller; I prefer to use the Nuance Controller by Pierre.
- Moving MIDI data around on the piano roll for legato patches to properly sync to tempo and trigger portamenti.
- Editing velocity levels of individual MIDI notes.
- Using articulation sets or expression maps to set individual MIDI notes to certain articulations within a sample library. I prefer to use ArtConductor by Babylon Waves.
Please refer to our Academy page which provides excellent resources and education for those wishing to learn advanced orchestral programming and virtual orchestration techniques.
For those interested in using our libraries in notation software, please refer to the following articles:
How do I use Spitfire Audio Libraries with Dorico?
How do I use Spitfire Audio Kontakt Libraries with Sibelius?