Documented and community-documented
Syxloom shows program names for these instruments, but its sources differ, and the app labels them:
- Sequential Prophet '08: from the manufacturer's operation manual (documented).
- Behringer DeepMind 12: from Behringer's user manual (documented).
- Sequential Prophet-6, OB-6, Rev2, Prophet-5 and Take 5: from community documentation, labelled as community-documented in the app. Treat their names as a helpful reading rather than a guarantee.
Requesting a dump
Sequential requests carry no MIDI channel or device ID. The Prophet '08 manual documents two: F0 01 23 06 F7 for the current edit buffer and F0 01 23 05 bb pp F7 for a stored program, where bb is the bank and pp the program (banks 0–1 in manual v1.0; later firmware may differ). Syxloom's Devices tab has presets for both, plus edit-buffer presets for the Prophet-6, OB-6 and Rev2 (community-documented).
There are no request presets for the Prophet-5 and Take 5. Start the dump from the instrument as its manual describes, or paste your own request as hex in the Library; Syxloom recognises the program when it arrives.
The DeepMind 12 request includes a device ID (0–15) set on the synth: F0 00 20 32 20 dd 03 F7 asks for the edit buffer and F0 00 20 32 20 dd 01 bb pp F7 for a stored program, with banks 0–7 (A–H) and programs 0–127. Both are presets in Syxloom, written for device ID 0 and, for the stored program, A1. For another device ID or program, paste the request as hex in the Library.
A backup routine
Keep Syxloom open during capture and sending; switching away stops the current operation.
- Open Monitor and choose the synth's MIDI input. Syxloom uses Apple's CoreMIDI, so a USB connection or a MIDI interface both work.
- Send a request preset from Devices, or start the dump on the synth. Review transfer shows the request before it goes out.
- When the capture is complete, save it. The program name appears in the inspector, with the community-documented label where it applies.
- Tag the entry with the instrument and bank so it is easy to find later.
Why the hex looks scrambled
Both families pack their program data so that every MIDI byte stays below 128: seven bytes of data travel as eight bytes in the message. Syxloom unpacks a copy only to read the name. The bytes it stores and sends are exactly the ones it received.
Sending programs back
Put programs in a send set and open Review transfer, which lists the destination and every message before you confirm. If you load several instruments at once, give each entry its own destination to make a setlist; a routed instrument that is not connected blocks the transfer rather than sending somewhere else. Neither manufacturer documents a gap between these dumps, so 150 ms is Syxloom's conservative suggested default.
An edit-buffer dump replaces the sound you are currently editing. A program dump that carries a bank and program number is meant for a stored slot and can overwrite what is there, so check the manual and capture the instrument's current programs before you send. Syxloom's receipt confirms that your device delivered the bytes; it cannot confirm that the instrument stored them.
Where Syxloom fits
Syxloom is our SysEx librarian for iPhone, iPad and Mac; one purchase covers all three. Its format support is based on published MIDI specifications, and layouts that come from community documentation are labelled in the app. It has been tested on simulators, with a virtual MIDI harness on the Mac and with large generated test libraries, not with physical instruments, and it cannot confirm that an instrument received or stored a patch.
Syxloom is also sold with Midiary, our Standard MIDI File studio for iPhone and iPad, in the MIDI Toolkit bundle on the App Store.
New to SysEx? Start with What is MIDI SysEx, and how do I back up my synth?.
