Remote (Utilities Menu)
Remote provides a remote control interface for Midi Quest Pro so that Midi Quest files can be loaded and transmitted under the control of any hardware or software that can generate MIDI events.
If you are using a sequencer which doesn't offer any of the plug-in hosts currently supported by Midi Quest, you can still have the sequencer remotely load and send Midi Quest SysEx files using this window. In addition, you could use a remove keyboard or controller hardware to do the same.
The interface for Remote is simple, you create a list of files that you want to be able to send; assign a comment or reminder as to what the file is for; determine the trigger event and specify a MIDI port or use the one stored in the SysEx file.
You can have as many Remote windows open as you wish. Each Remote window can have as many triggers as you wish. This allows you to download setup as many different downloads as you wish with you or a sequencer deciding when the SysEx should be sent.
Creating a New Remote Window
Choose Utilities/Remote from the menus.
Opening a Remote File List from Disk
To open a previously saved Remote file by choosing File/Open and selecting the file to load.
Editing a Remote File List
All editing of Remote File Lists is through the context menu. Right click in the window to display the popup context menu. You can cut, copy, paste, clear, add or modify entries.
The Remote Setup Dialog
The Remote Setup dialog allows you to create or edit an entry for the Remote File List. There are four components to this dialog: the file to load and send, a descriptive comment, a MIDI port (options), and a trigger event.
The file is the Midi Quest File you want to send when the trigger condition specified below is met. It might be a single patch, a bank, a Collection or a Set. You can use the Browse button to display a File Selector dialog to select the file you wish to load and send.
The Comment is provided simply so you can have a reminder as to what this is used for
Port is the MIDI port to send the SysEx to. Normally, you will probably want to send the SysEx to the MIDI port selection that is stored in the file itself. However, you can choose to over-ride this and send the SysEx to a specific MIDI port selected here.
The trigger is the MIDI event that causes Midi Quest to load and send the file. The trigger can be either a standard MIDI event such as a note on, note off, or controller event. Alternately, output can be triggered by the reception of a SysEx event. If you want a MIDI event to trigger output then click on the "MIDI" button. Alternately, click on the "SysEx" button to enter a SysEx message.
If you choose MIDI as the trigger style, use the four parameters to select the type of MIDI event that will trigger output. You can select from any of the standard MIDI event types: note on, note off, poly key pressure, controller value, patch change, channel pressure and pitch wheel.
In each case, the trigger can be on any MIDI channel or limited to the specific MIDI channel you select.
The final two parameters are configured based on the selected Event type. Select the settings to create the desired trigger.
If you select SysEx as the trigger then all of the MIDI settings are disabled and a text entry area is displayed. Here you should enter the SysEx message that you want Midi Quest to search for in order to generate output. Your SysEx message should start with an "F0" and should end with "F7". Between these two you can enter as many values as needed to create the SysEx message that will act as the trigger. All values are entered as HEX and with the exception of the values F0, F7, and FF, the values should be in the range 00 to 7F (0 to 127).
"FF" is a special case value. It will match to any value and allows matching to channelized SysEx messages where the channel is ignored.