Chasing

Chasing
Chasing is a form of event tracking. When you enable Chasing, Metro scans through the Section before playback begins and accesses the most recent event in order to incorporate it in playback. For example, say you placed a Program Change event at Bar 6 but you want playback to begin at Bar 10; with Chasing enabled, Metro can scan to that event and play the correct sound (the sound of the Program event placed at Bar 6) when you play from Bar 10. Without Chasing enabled, the correct sound might not play because the Program Change event from Bar 6 is not contained within the playback range.

Chasing is almost always desirable; however, a minor drawback is that it can cause slight delays before playback or recording begins.

You can choose the type of MIDI data you want chased by checking the corresponding data types in the MIDI Data Chasing dialog box.

Use the Delay 'N' /60ths of a second after sending sysex to instruct Metro to wait 'N'/60ths of a second in between sending SysEx packets. The default setting is suitable for most MIDI devices, but you may opt for a longer delay time if you experience problems sending System Exclusive data to a particular device.

Send all instances of controllers between 'X' and 'Y' when chasing sysex should be utilized when controllers are used to alter the timbre of a sound - especially if the timbre of that sound is incrementally varied throughout a given track. This will allow Metro to track controller values and accurately play the modified sound. All instances of controller numbers falling within the user-specified range will be chased upon playback.

Choose the Send all instances of program changes checkbox in order to successively send all Program Changes from the beginning of the piece to the current insertion point before playback occurs. Chasing all instances of Program Changes is particularly useful when working with Bank Select messages (Bank Select messages sometimes consist of two Program Changes).