Whats the point of creating a “MIDI 2” object on the desktop if it always works the same as the “MIDI” object?
This problem is logged as APAR JR10933. It really has nothing to do with the Crystal Semiconductor drivers, but it affects Crystal Semiconductor’s OS/2 customers because the IBM-supplied MIDI drivers (OPL3.SYS and MPU401.SYS) are used for MIDI support, so it’s very easy to install two MIDI drivers. Since it’s a WPS/MPPM bug, you can use any non-WPS or non-MPPM.EXE method to play MIDI files, and they will all work. The “MIDI” object is a pointer to the “Sequencer01” device, and the “MIDI 2” object is (or, supposed to be) a pointer to the “Sequencer02” device. So you can, for instance, use the REXX interface to play on Sequencer02: C:\MMOS2\SOUNDS> play file=bach.mid dev=sequencer02 Q11: What is the difference between FM Synthesis (OPL-3) and WaveTable Synthesis (MPU-401)? A: Both of these technologies refer to how the songs in your MIDI files are played on your hardware. When a song is stored in MIDI format, the actual sounds of the music are not stored. Instead, MIDI only contains info
