7 Creative Techniques with Bome’s SendSX in Live Performance

Bome’s SendSX: A Complete Beginner’s Guide

What SendSX is

Bome’s SendSX is a lightweight utility for sending and formatting MIDI System Exclusive (SysEx) messages and other MIDI data from text input. It lets you create, edit, and transmit exact MIDI bytes without needing a full MIDI sequencer, making it useful for device configuration, firmware updates, patch management, and testing MIDI hardware or software.

Why use SendSX

• Precision: Enter exact hexadecimal SysEx strings to control device parameters or initiate device-specific commands.
• Simplicity: Minimal UI focused solely on sending SysEx and raw MIDI messages—good for quick tasks.
• Portability: Small footprint and fast startup compared with larger DAW-based workflows.
• Debugging: SendSX is handy for diagnosing MIDI communication problems or confirming device responses.

Installing and launching

1. Download SendSX from Bome’s website (choose the version for your OS).
2. Unzip or run the installer, then launch the application.
3. On first run, allow access to your system’s MIDI devices if prompted.

Interface overview

• Input field: Where you type hexadecimal bytes or textual MIDI messages.
• Send button: Transmits the content over the selected MIDI output.
• Output selector: Choose which MIDI port or virtual driver to use.
• Logging/Response area: Displays sent bytes and any received data (if supported by your device/driver).

Writing and sending messages

• SysEx format: Start with 0xF0 and end with 0xF7. Example for a generic SysEx message:

  Code
  Copy CodeCopied
  F0 7D 10 01 00 F7 

  • F0 = SysEx start
  • 7D = Manufacturer ID (7D is non-commercial / educational)
  • … = payload bytes
  • F7 = SysEx end
• MIDI bytes can be typed with or without spaces; SendSX will parse them.
• After entering your message, select the correct MIDI output and click Send.

Common use cases

• Patch or preset upload: Send bulk SysEx dumps to update patch banks on hardware synths.
• Device configuration: Toggle device settings or request device info if the device accepts SysEx commands.
• Firmware or bootloader commands: Some devices require precise SysEx sequences to initiate updates—SendSX provides that precision.
• Testing and development: Validate MIDI message handling for new hardware or software.

Tips for safe and effective use

• Verify device docs: Always check the manufacturer’s SysEx implementation chart before sending commands. Incorrect SysEx can change settings or brick devices.
• Backup current settings: When possible, request and save a device’s current SysEx dump before sending changes.
• Use the correct MIDI port: Ensure the selected output targets the intended device or virtual loopback.
• Keep messages short for testing: Send small, non-destructive queries first (e.g., device identity request) before bulk writes.
• Use a non-commercial ID for tests: Manufacturer ID 7D is reserved for non-commercial testing and will generally be ignored by production gear.

Troubleshooting

• No response: Check MIDI cable/USB connections, correct port selection, and that the device is powered and set to receive SysEx.
• Garbled data: Ensure the device expects 7-bit data payloads; some devices use encoding schemes for bulk dumps.
• Permissions errors (macOS): Grant MIDI access in System Settings and allow the app to use the selected MIDI drivers.

Example workflows

1. Request device identity: “` F0 7E 7F 06 01 F7