SGX-Nitro MIDI monitor/message log
Selecting the MIDI monitor tab reveals the MIDI message list. It displays
a summary line for each message received. Any valid MIDI message (not only
sysex, but program and controller changes) is captured and can be examined,
edited, and stored to disk. The log is only populated from MIDI-in messages. You
must select the desired MIDI_In device to receive MIDI
data and of course connect your MIDI device's (such as the SGX-Nitro) MIDI-out to the
selected MIDI-in device on your computer.
Right(or alternate)-clicking on the log will bring up the following context
sensitive operations:
- Delete selection - The highlighted message(s) is/are deleted from the message log.
- Clear input Log - Deletes all messages from the log.
- Copy selected text - Selected text in the monitor window is copied to the clipboard.
- Set double-click action - You can configure the behavior invoked when double-clicking a
line in the log. Note that the following is applicable only to sysex events received
via your MIDI in connection. The log may contain other text-only messages. These have
no data and therefore cannot be loaded into an editor.
- Load msg into buffer - Data for the selected sysex/MIDI event is loaded into
the message buffer (hex editor). From there you can edit it or save it.
- Open in Editor - If the log item is a sysex event containing a valid preset
or MPT, then double-click will bring up the event data in the appropriate editor.
- Send to MIDI Out - Data for the selected sysex/MIDI event is sent to MIDI out.
During the automated backup process (see SGX
Requests) the MIDI monitor log is also used as a message log to display
text regarding the progress of the backup operation. Messages are logged for
each preset as it is received. But during this process, the MIDI data is stored
directly to disk (in the selected folder) instead of being cached in the MIDI
log. While this means that you cannot select presets from the log and load them
into the message buffer, you can open them from the file explorer after the
backup is completed.