MIDI Preferences

MIDI Thru is a multi phase switch. When active, it takes MIDI events at a MIDI IN Port and sends them out one of the MIDI OUT Ports.

Off	No MIDI THRU
On	MIDI THRU to the default MIDI OUT Port (as set in the MIDI tab) using the received MIDI channel
Auto	Map MIDI THRU to the current MIDI component channel and port
MIDI Channel	Map MIDI THRU to the default MIDI channel and MIDI OUT Port
Auto with Smart Port	Map MIDI THRU to the current MIDI component channel and port, ignore MIDI events received from the active instrument's MIDI IN port
Auto from Default MIDI IN Port	Map only MIDI events received from the default MIDI IN port and route to the current MIDI component channel and port With this option set, input CC and patch change events are only processed if they arrive on the default MIDI IN Port

When checked, MIDI Thru will pass real time MIDI events as well as standard MIDI events to the designated MIDI OUT port.

When checked, it indicates that "Local Off" has been assigned for the controller keyboards in the studio. When Local Off is assigned, it is necessary for Midi Quest to echo back MIDI performance events back to the source instruments in order for them to be heard. Under normal circumstances, when Midi Quest receives MIDI performance events from an instrument and it is configured to send to those events back to the same instrument, it does not. The reason is the assumption that the keyboard is already playing the instrument so a second set of events would just steal notes from the synthesizer.

The default settings are the settings that the program uses when the information is not contained within the window itself. The MIDI channel is used when notes are played from a window with no assigned MIDI channel.

MIDI Channel: the MIDI channel used by a window to output notes on when no MIDI channel is assigned to that window

MIDI Port In: the MIDI port used by a window to received MIDI events when no MIDI port is assigned to that window

MIDI Port Out: the MIDI port used when MIDI events are sent from a window with no assigned port

Please note, a MIDI Patch Bay is not a multi-port MIDI interface. A MIDI Patch Bay has only MIDI ports and has no USB connections. Do NOT check this option if you have only multi-port MIDI interfaces.

When checked, this option enables Patch Bay support features in Midi Quest. Patch Bay's were frequently used in the 1980's and 1990's but are rarely used now and have been replaced by multiple multi-port MIDI interfaces and so the capability is rarely required. In addition, enabling these options and then not configuring them properly can cause Midi Quest to operate improperly. If required, please take great care to properly configure Patch Bay support for each MIDI device installed in Midi Quest.

Under normal conditions, it should not be necessary to make use of these parameters. However, if you are using a very fast computer with older instruments, it may be necessary to make adjustments in order to properly transfer SysEx.

Why is this the case? The support files for a particular instrument are normally created and tested around the time of that instrument's release. As computer speeds increase, they are capable of sending individual MIDI bytes closer together. In some cases, current computers are able to pack the SysEx so densely that older instruments are no longer capable of receiving it. These parameters allow Midi Quest to be optimized in a global fashion to deal with these issues.

If is important to remember that a change to any of these three parameters does not take effect until the program is restarted

Delay between SysEx Transmissions: Midi Quest always delays 80 milliseconds between each SysEx transmission and if, during development, we find a longer delay is necessary, we incorporate that delay. In the case where your system is sending the SysEx too quickly for the receiving MIDI devices, an additional delay can be added here. The delay amount is in milliseconds.

Delay SysEx (Windows only): In the case where an instrument can't receive a transmitted SysEx message because the SysEx is too dense, this parameter allows the transmission to be extended by adding additional time between some of the SysEx bytes. The value "n" entered here indicates how frequently the program should insert a 1 millisecond delay. Entering a value of "1" would cause the program to send 1 byte then delay a millisecond, send 1 byte and delay a millisecond and so on. A value of "10" would result in the program sending 10 bytes, delaying a millisecond, 10 byte sent, a millisecond delay and so on until the message is complete. This is the equivalent of the "DM n" macro command. This option is not available for the Macintosh version of Midi Quest as a result of the design of CoreMIDI.

Slow SysEx (Windows only): If it is necessary to have a greater then 1 millisecond delay in the function above, a delay of any number of milliseconds can be selected by this parameter. This option is not available for the Macintosh version of Midi Quest as a result of the design of CoreMIDI.

Midi Quest Pro
Midi Quest
Midi Quest Essentials	(supports a subset of these parameters)
Midi Quest one	(supports a subset of these parameters)