| Can MM4's 'Find' command help me find my car keys?
No. But, it CAN help you to find your missing or misplaced MIDI events.
Will MM4 remember what I last searched for?
Yes. When you click Ok, MM4 saves all of the settings on this page into the preset whose name appears in the "preset" box. To create a new preset without overwriting the previously used preset, enter a new preset name into the preset box before clicking Ok. To save a preset without clicking Ok, click the save icon (a disc). To delete a previously saved preset, click the delete icon (an X).
What do the "set all" and "set none" buttons do?
They represent two ways of approaching a search problem. The "set all" button resets everything on the page to its default setting, insuring that ALL events initially will be found. The "set none" button un-selects everything, insuring that nothing initially will be found. From either of these two staring points, you may then alter the settings to find just what you're looking for.
Ok, I know what "notes" are, but what are RPN and the others?
| Event Type |
Function |
| Controller |
Effect values and other settings. A common is expression (11), a "volume" controller normally used within a track for crescendos and other volume dynamics. Your synthesizer may offer a number of others. |
| Patch change |
Changes the instrument or program on a particular channel. Although discouraged in MIDI Maestro, patch changes may occur mid-track. |
| after-touch |
After-touch events represent pressure changes to keys after they have been pressed, but before they are released. Most keyboards are not sensitive to this. |
| Pressure |
Pressure is similar to after-touch, but is applied to the entire channel rather than on a key-by-key basis. |
| Pitch-wheel |
The pitch-wheel alters the frequency of notes as they are played on a channel. |
| RPN |
RPN stands for Registered Parameter Number. There are only a handful of RPNs, and these control pitch-wheel range as well as keyboard tuning. |
| NRPN |
NRPN stands for Registered Parameter Number. These are not common. They would be definied by a device manufacturer to be specific to a product. |
| Meta |
The Find command may be used to locate Meta events which contain text, such as lyrics. An event will be matched if your text appears anywhere within the lyric text. |
| Chords |
Chords are MIDI Maestro specific events. Enter the text of the chord, such as C#7. |
| SysEx |
These are System Exclusive messages which generally contain bulk programming data for your keyboard(s). |
| Wedges |
These are the "hair pin" dynamic markings showing crescendos and decrescendos in the staff view. |
What are all of these "not" boxes for?
If you've selected notes in the range from C4 (60) to C5 (72), for example, MM4 will find notes with numbers 60, 61, 62, ..., 72. However, if "not" is checked before that range, then MM4 will find 0, 1, 2, ..., 59, and 73, 74, ... 127. That is, all with be found with the exception of the selected range.
Can I limit my search in any way?
Yes. By selecting tracks before opening the Find command, you may choose to search only those selected tracks. Also, you may select a range of time before opening the Find command to search only that specific range of time.
Ok, so now I just click Ok?
When you click Ok, MM4 will search forward from the current song position for the first matching event. If a match is found, the current song position is advanced, and the matching event is selected.
To continue searching for the next event, use the Find Next command (mapped to F3 by default). If multiple tracks contain matches at the same position, events are selected in turn beginning with the first track and proceeding down the track list.
Can I just select all events at once?
Yes. This provides a "filter" functionality. Select the "select all events" option before clicking Ok. You may still use the Find Next command to advance the song position. However, when multiple tracks contain matches at the same position, the Find Next command simply moves to the next song position with matching events instead of forcing you to use the Find Next command once for every matching event.
Are there any caveats I should know about?
Funny you should ask. The Find command currently does not find events that have been adopted by MIDI Maestro as "track properties," such as each track's name, patch, bank, etc. |