|
|
|
|
|
|
Q:
Automation, MIDI Cannot pass automation between Windows Sequencer and Session 8 (IBM), even though sequencer will sync to S8.
A:
1) Session 8 MIDI window not configured correctly (Automation Receive Internal enabled, Channel = sequencer track channel).
2) Select another MIDI port for automation and timecode then re-select the Session 8 port. 3) Corrupted Session 8 application (reinstall S8). 4) MIDI Map in Session8.ini missing, or contains incorrect values (all zero). Throw away MIDIPRTR.DLL, SCSI_DSP.DLL and SESSION8.INI, then reinstall S8. 5)Check C:\Windows\System.INI file. Make sure Midi1=Digimidi.drv. If there is a "Midi=" then change that to another number (eg. Midi2=...) just so long as Digimidi=Midi1. When the software loads it looks for these Midi #'s and renumbers them so Digimidi can be #1 but it cannot see a plain ole "Midi=" therefore it can't renumber it and will conflict. 6)If it doesn't work and everything is setup correctly then there may be a problem with Windows Midi Mapper. You will have to use a recovery disk or Windows disks to reload Windows. Midi Mapper may show up and may appear to be functional but reloading seems to be the only viable option.
Other Popular Articles:
Audio CDs produce a repetitive clicking in the audio after labeling them with a pen. Connector, Problems Output Connectors are a problem- PA1000, PA1800 hard drives, Storage, Hard Drive Compatibility K2000, K2500 List Current 6/21/95 Calvin or Janis, Revision Calvin or Janis K2000/K2000R Disk, Hard Drive, Storage, Backup, Problem Backup problems with K2000 Hard Drive |