Dorico Tutorials

Exporting General MIDI from Dorico

Dorico doesn’t include a built-in “General MIDI” export mode, but you can export General MIDI from Dorico with a few manual steps.
By disabling Expression Maps, you remove all keyswitches and custom controller data, leaving a straightforward MIDI file that will import cleanly into Logic, Cubase, or any other DAW.
For recurring projects, you can even build a reusable “maps-off” Playback Template that you can apply whenever you need a General MIDI export.
If you’d like: consult the Dorico manual on this topic

Before You Export…

Think of this step as a boolean filter — a quick yes/no decision that determines whether you even need to export General MIDI from Dorico in the first place.

In earlier workflows, notation users were taught to export raw GM-style MIDI and rebuild the production in a DAW. That made sense back when MIDI was the common denominator and notation software couldn’t host serious instruments.

Today, that’s changed. With VST (or AU) libraries available in both Dorico and most DAWs, you can often use the same sampled instruments—Kontakt, HALion, ARIA, or other full-featured libraries—in both environments.

• ✅ If you plan to work with the same libraries in your DAW, leave your Expression Maps ON. You’ll keep articulations, dynamics, and performance data intact and save time later.
• ⚠️ If the collaborator or destination system expects a General MIDI file, or isn’t equipped to interpret keyswitches and CC data, then it’s best to disable Expression Maps before you export General MIDI from Dorico.

In short: same library = leave maps on; unfamiliar or GM-only setup = turn them off.

One-off General MIDI Export from Dorico (fastest method)

1. Disable Expression Maps on every track
   • Go to Play → Track Inspector.
   • In the Ex. Map dropdown, choose the top item: -- (None).
   • Repeat for every track in your score.
2. Export the MIDI
   • Use File → Export → MIDI…
   • The resulting file will contain plain note and velocity data with minimal controller clutter.
   • The file will include track names – but not necessarily GM Patch #’s.
   • Some DAWs will recognize the instrument names and interpret them as Patch #s.

💡 Tip: This is ideal for one-time exports where you don’t need to recall the setup later.

Reusable “Maps-Off” Playback Template

If you plan to do this repeatedly for the same instrumentation, save your map-free configuration as a reusable Playback Template. The next steps assume you’ve turned off your Expression Maps.

1. Open the Endpoint Editor
   Click the ⚙️ gear icon on the top track to open Endpoint Setup.
2. Observe the included instruments
   The dialog shows all instruments assigned to that VST instance. Take note of where the list ends.
3. Create a new Endpoint from your new configuration with the Expression Maps turned off.
   Click Save Endpoint Configuration and give it a clear name, such as
   HALion Sonic No Maps 1.
4. Repeat for each VST
   Move to the next VST instance (the first track beyond the last one in step 2), open its gear, and save again.
   Do this for every separate VST (HALion, ARIA, Kontakt, Opus, etc.).
5. Create a Playback Template
   • Top menu: Play → Playback Templates…
   • Click the + (Add Playback Template) button (lower left).
6. Add your new Endpoints
   • Choose Add Manual…
   • Select the map-free Endpoints you just saved.
7. Name your template
   Example: Orchestral – GM Export (No Maps)
8. Use it next time
   • Apply this template whenever you need a GM export for the same instrumentation.
   • If your orchestration changes, repeat this process for the new configuration.

Why It Works

Expression Maps tell Dorico how to trigger articulations and dynamic controls for virtual instruments.
Turning them off disables that layer, producing a clean, notation-driven MIDI output.
The receiving DAW or GM player then interprets the tracks using its own patch logic—often correctly, since track names are preserved.

Quick Reference

Limitations and Behavior Notes

Dorico’s MIDI export isn’t designed to produce a fully compliant General MIDI file.
It prioritizes notation accuracy over playback standardization.

• Track names are preserved.
  Dorico embeds every instrument name as a Track Name meta-event. Most DAWs import these automatically.
• Dorico doesn’t export GM patch information, but does include instrument names, which some DAWs are able to interpret, and may be visible in the DAW’s track list.
• Some patch info may appear.
  Using Dorico’s HALion Sonic Selection template can embed GM-compatible Program Change messages.
  With Iconica, HSO, ARIA, or NotePerformer, you’ll often see default program 0 (Acoustic Grand Piano).
• No Bank Select messages.
  Dorico omits CC 0/32 (Bank Select MSB/LSB), so GM players only see basic patch numbers.
• DAW mapping varies.
  Logic and other DAWs may infer instruments from track names. (Strings are often correct, winds and brass may be guessed.
• Expression Maps off = clean MIDI.
  Disabling maps removes keyswitches, articulation, and modulation CCs, yielding a straightforward, readable file.

Need a True GM File?

If you require strict GM compliance—with every instrument carrying a correct Program Change and Bank Select—Dorico isn’t built for that.
Instead:

1. Export MusicXML from Dorico.
2. Open it in Finale or some other notation software that has true GM support.
3. In Finale: MIDI/Audio → Play Finale Through MIDI → General MIDI.
4. Finale assigns authentic GM patches automatically.
5. Export MIDI from Finale for a standards-compliant GM file.