site documents a petition put forward by doug wyatt creator of oms
after the buyout by gibson.. it was a petition to gibson for them to release oms ownership
to be opensource
notice the first question : is oms compatible with mac os 9!!!
this is because opcode was closed down before mac os 9.0 was ever released...
so it was never officially updated for use with mac os 9
Q: Is OMS compatible with Mac OS 9.x?
A: Yes, to the best of our knowledge, and contrary to some persistent rumor-mongering. All of the significant problems we're aware of have been due to bugs in other developers' OMS drivers.
Q: Is OMS compatible with Mac OS X?
A: Some parts of it appear to run in the Classic environment, but in general, the Classic environment is not well-suited for MIDI; not all hardware is accessible from it. OMS is not accessible from native OS X applications.
Q: Has Gibson shown any signs of being interested in finding new caretakers for OMS, Vision and Opcode's other intellectual property?
A: To our knowledge, no.
Q: What's Apple doing for MIDI on Mac OS X?
A: Apple is providing a new MIDI Services API, unrelated to OMS and QuickTime. It has a new MIDI driver plugin model and new OMS-like programming interfaces (API's) for applications to talk to MIDI hardware. There aren't any user-visible MIDI features; Apple just provides system support for hardware makers to write drivers and applications to access them.
Programmers who have used OMS before find that the new system shares some of OMS's concepts, many of which were in turn based on Apple's old MIDI Manager. MIDI Services supports efficient MIDI I/O with precise timestamping and scheduling, but it does not have some of OMS's higher-level functionality such as studio and patch name management, and musical timing services.
Q: Are MIDI Services part of Carbon? Are they accessible from Classic?
Q: So what should developers who wish to support both Mac OS 9 and Mac OS X do?
A: Use OMS on 9, and MIDI Services on X. Many developers are already familiar with the issues involved in writing code to run on multiple platforms and should be able to create abstractions to facilitate portability.
Q: How can developers learn more about Apple's MIDI Services?
A: The application interfaces are in the CoreMIDI framework (docs in MIDIServices.h) and the driver plugin interface is in the CoreMIDIServer framework (docs in MIDIDriver.h). Sample code and a bit of additional documentation is in /Developer/Examples/CoreAudio/MIDI.