Fast answer

For an intended SysEx receive session, set GLB-15 [SysEX Filter] → Receive to ENABLE and match the Global MIDI Channel. For program or pattern dumps, back up your data first and check GLB-20 Memory Protect.

Do this first

  1. Confirm the sender is connected to the Prophecy's MIDI IN.
  2. Open GLB-15 [SysEX Filter] and set Receive to ENABLE for the transfer.
  3. Check GLB-8 → Global Channel against the editor or librarian. For a program or pattern dump, back up your data and set the relevant GLB-20 Memory Protect switch to OFF before retrying.
  4. After the transfer, return SysEx Receive to DISABLE if you do not need ongoing editor communication.

Diagnose it

Is GLB-15 Receive set to ENABLE?

Yes: Check cable direction, Global Channel, the sender's Prophecy-specific data format and GLB-20 protection for dumps.

No: Enable SysEx receive for this transfer and retry.

Expected result

The Prophecy accepts a supported SysEx transfer; the exact result depends on the message type.

Why this works

Korg documents a SysEx receive filter and distinct data dump message types. This page does not assume that any arbitrary SysEx file is compatible.

Still stuck?

Recheck the physical MIDI direction and the exact source device setting. If this behavior differs on your hardware, keep the model/revision and setup details for a correction report.

All Prophecy fixes
Provenance

Sources & review

Last desk review: . Documentation does not replace a physical hardware test.

Sections reviewed: GLB-8, p. 139; GLB-15, p. 144; GLB-18, pp. 146–148; GLB-20, pp. 148–149; MIDI implementation, pp. 161–170.