MIDI Configuration on Mac OS 9 for Sequencing

During the Mac OS 9 era, configuring MIDI for music sequencing required dedicated third-party system extensions, as the operating system lacked a modern, built-in framework like Core MIDI. Musicians relied primarily on Opcode’s Open Music System (OMS) or Mark of the Unicorn’s FreeMIDI to bridge the gap between their hardware instruments, physical interfaces, and sequencing software. This article explores how external hardware was connected, how these MIDI management systems were configured, and how sequencing programs communicated with studio gear.

Hardware Interfaces and Physical Connections

Before modern plug-and-play USB interfaces became standard, Mac OS 9 systems utilized high-speed serial ports—specifically the RS-422 "Modem" and "Printer" ports found on legacy Macs. Musicians connected multi-port MIDI interfaces, such as the MOTU MIDI Timepiece or Opcode Studio 64X, directly to these serial ports.

Later G3 and G4 models phased out serial ports in favor of USB, requiring either native USB MIDI interfaces or third-party serial-to-USB adapters. Because the Mac operating system did not automatically detect external MIDI hardware, a critical first step was disabling AppleTalk in the Chooser control panel to free up the printer port for dedicated MIDI data transmission.

The Role of OMS and FreeMIDI

Because Mac OS 9 had no centralized, native MIDI engine after Apple discontinued its early MIDI Manager, software developers filled the void. Two competing protocols became the backbone of music production:

  • Open Music System (OMS): Developed by Opcode Systems and later acquired by Gibson, OMS became the industry-standard graphic MIDI environment. It was required by applications such as Digidesign Pro Tools, Emagic Logic Audio, and Steinberg Cubase.
  • FreeMIDI: Developed by MOTU (Mark of the Unicorn), FreeMIDI served a similar purpose and was the native system for Digital Performer, though it offered an OMS-compatibility mode to work across other applications.

These applications operated at the system level via OS 9 extensions, allowing sequencing software to share access to MIDI ports simultaneously without causing hardware access conflicts.

Defining the Studio Setup

Musicians configured their setup by launching a standalone application—most commonly OMS Setup. Within this software, users built a graphical representation of their entire physical studio.

  1. Detecting Interfaces: The user ran a scan to let the software discover connected serial or USB interfaces.
  2. Adding Devices: Users created virtual representations of each hardware synthesizer, drum machine, sampler, or effect unit.
  3. Defining Parameters: For each connected device, the user specified the manufacturer, model, physical input and output ports, MIDI channel availability (1–16), and whether the unit sent or received MIDI Clock, Time Code, or System Exclusive (SysEx) data.

Once configured, the user saved a "Studio Setup" file. This file was stored in the System Folder and loaded automatically whenever the computer booted.

Integration with Sequencing Software

Once the studio layout was defined in OMS or FreeMIDI, sequencing applications integrated with it seamlessly. Instead of manually mapping raw port addresses and channel numbers within the sequencer, programs like Pro Tools, Cubase, or Logic simply read the saved Studio Setup.

Inside the sequencer's track inspector, available MIDI destinations were displayed by their actual device names (e.g., "Korg Triton - Ch. 1" or "Roland JV-1080 - Ch. 10") rather than generic port names like "Modem Port B". If an instrument was reassigned to a different physical port on the interface, the musician only needed to update the central setup utility once, and all sequencer sessions would automatically adopt the new routing.