home *** CD-ROM | disk | FTP | other *** search
-
- ** MidiLab/2 Installation and Notes **
-
- MidiLab/2 should be installed within an OS/2 2.0 environment, in its own
- directory. Install as follows:
-
- 1. Create a directory for MidiLab/2 on a drive of your choice. The following
- examples and instructions assume the directory is named MLABPM.
-
- 2. Copy MLABPM.ZIP (or MLABPM.RAM) into the MLABPM directory. Use PKUNZIP
- (or LOADRAM2) to break it apart. (you've already done this or you
- wouldn't be reading this file)
-
- 3. Set up a program template in an existing folder or on the desktop
- specifying the following parameters:
-
- - Path and file name: [d:]\MLABPM\MLABPM.EXE
- - Parameters: 30 20 20 20 15 15 15 15 /P=[d:]\songlib
- - Working directory: [d:]\MLABPM
-
- The eight numeric parameters specify the track data sizes in kbytes.
- The /P parameter is used to specify a default directory for loading and
- saving MIDI data files. Extensions of .MID (standard MIDI format 1) and
- .ML (MidiLab/2 native format) are supported. A sample songfile
- (FULL5TH.ML) is included, to be placed in a directory of your choice.
-
- 4. Add a DEVICE statement to CONFIG.SYS for the MidiLab/2 MPU device driver:
- DEVICE=[d:]\MLABPM\MPU401DD.SYS I=nn
- where:
- nn is the interrupt for which the MPU hardware is wired. (usually 2 or 5)
-
- 5. After re-booting your system, MidiLab/2 will be ready to run by mousing
- the MidiLab/2 icon created in step 3.
-
- ------------------------------------------------------------------------------
- The online HELP contains the documentation and description of the product,
- as well as an introductory MIDI tutorial. Everything (I hope) you need to know
- is contained in the help support. Most, if not all, dialogs and pull-downs
- have at least some basic verbage on their functions.
-
- MidiLab/2 will run in a 'demo' mode if you don't have the MPU-401 hardware.
- The play and record functions will be disabled, but the file manager,
- editor, and most of the dialog boxes and windows will be available.
-
- MidiLab/2 has evolved over a seven year period, starting out as a DOS program,
- then OS/2 1.3 non-PM, and finally on to 2.0 32 bit. Your comments and
- suggestions are welcome, either on MIDILAB FORUM (VM), PC-TIE, or Compuserve.
-
- ------------------------------------------------------------------------------
- Release 1.10 notes: April 1993
-
- - Added improvements to Editor, including ability to easily mark large blocks.
- - Added MLABPM.INI; initialization file.
- - Added Remote Control facility, enabling MidiLab/2 to be controlled from a
- MIDI device.
- - Track capacity extended to 65K
- - Miscellaneous bug and performance fixes.
-
- IMPORTANT: MidiLab/2 is designed for a high-resolution display (1024 X 768).
- Until I get font selection support in, you may have a problem with
- some of the dialog box text being truncated.
-
- Usage notes:
-
- - If performance problems occur, turn off the index display from the
- 'Utilities' pull-down.
-
- - Time bases greater than 192 PPQ (pulses per quarter note) are not
- supported. If you have an existing MIDI song file with > 192, playback
- quality may be compromised.
-
- - MidiLab/2 supports a maximum of eight virtual tracks, and will load only
- the first nine tracks of an existing file containing more than this.
- In creating files with MidiLab/2, several tracks may be merged into one,
- so that the effective number of tracks is virtually unlimited.
-
- - In Edit, the event list box is limited to approx. 2000 events. This is
- due to an OS/2 limitation of 65K for list box contents. This
- limitation is expected to be lifted in a future release of OS/2.
-
- ------------------------------------------------------------------------------
-
- James L. Bell
- Far Pavilion Studio
- VM: NR0004 @ BLDVMA
- Compuserve: 71034,3001
- Tel: (408) 378-9649