Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1]   Go Down

Author Topic: Macintosh Serial MIDI: Hardware, Cables, Clocking, Protocols and Drivers  (Read 3 times)

smilesdavis

  • Moderator
  • 1024 MB
  • ******
  • Posts: 1276
  • ...

Macintosh Serial MIDI: Hardware, Cables, Clocking, Protocols and Drivers
Mac hardware → connector → cable topology → clock source/rate → serial data rate/framing → virtual-port framing → driver/API

1984–1990 — Macintosh serial hardware

  • Macintosh 128K / 512K / 512Ke: Zilog Z8530 SCC; separate modem/printer channels; DE-9 Macintosh differential serial; fewer handshake/clock connections than later Mini-DIN-8.
  • Macintosh Plus (1986): Mini-DIN-8 serial; Tx± / Rx± / HSKi / HSKo; HSKi = handshake input or external SCC clock; GPi pin 7 not connected.
  • SE / Macintosh II generation (1987–): Mini-DIN-8 becomes standard; two SCC channels = modem + printer. SE/SE30/II-family/Portable modem-port GPi provides additional SCC clock routing; LC, like Plus, has GPi pin 7 unconnected.
  • Apple System Peripheral-8 Cable M0197 (1987): straight Macintosh Mini-DIN-8 peripheral cable later specified by Yamaha TG100 and Opcode Studio 5.
  • Mac serial hardware supports asynchronous, synchronous and externally-clocked operation where the required SCC clock paths are exposed.

1991


1992


1993


1994

  • Power Macintosh 6100 / 7100 / 8100: Macintosh serial survives the 68K → PowerPC transition; modem/printer serial remains available to existing MIDI hardware.
  • PowerBook 500 series: one external Macintosh serial port rather than separate printer + modem connectors.

1995


1996


1997


1998


1999


Protocol evolution / observations

  • Yamaha: TG100 = external-clock transport / MTP OFF → MU50 = F5 cable/port layer → MU100 = two F5 ports / 32 parts + MTP configuration.
  • F5: Yamaha, Korg and MTP-compatible implementations use an F5 host-control/cable layer; shared F5 usage ≠ proven protocol identity or interoperability.
  • Opcode: Studio 5 offers MTP emulation; Studio 4 interoperates with MTP while using its own more efficient host protocol.
  • Emagic: Unitor8 offers MTP emulation while retaining FAST / AMT operation.
  • Protocol identity ≠ compatibility mode: Opcode and Emagic can present an MTP-compatible personality without their native protocol being MTP.

Bottom line:

same Mini-DIN-8 connector ≠ same cable
same cable ≠ same host protocol
1 MHz clock ≠ serial data rate or MTP
GeoPort hardware ≠ GeoPort protocol
F5 xx = virtual-port / line-control framing, not proof of protocol identity
MTP compatibility may be emulation rather than native protocol identity
USB serial ≠ Macintosh SCC
replacement-port compatibility = electrical/clock support + port emulation + driver/API

❓ Remaining byte-level questions:

F5 mapping/interoperability: Yamaha/Korg ↔ MOTU MTP
MOTU FAST + network framing
Opcode native host protocol
Midiman serial host protocol
Logged
new in September: iSight (box), System 7 (box)
Pages: [1]   Go Up

Recent Topics