Unify Manual

Your complete reference to PlugInGuru's creative playground!

User Tools

Site Tools


midi-monitor

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
midi-monitor [2020/07/24 14:53] – created shanemidi-monitor [2023/05/08 18:59] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== MIDI Monitor ====== ====== MIDI Monitor ======
 Unify's built-in **MIDI Monitor** plug-in is a simple utility that helps troubleshoot MIDI issues by displaying MIDI activity. It's easiest to use in an Instrument slot, but can be used anywhere in Unify, as it passes MIDI messages through unchanged. Unify's built-in **MIDI Monitor** plug-in is a simple utility that helps troubleshoot MIDI issues by displaying MIDI activity. It's easiest to use in an Instrument slot, but can be used anywhere in Unify, as it passes MIDI messages through unchanged.
- 
-To understand MIDI data flow in Unify, see [[midi-details|How Unify processes MIDI data]]. 
  
 {{::midi-monitor.png|}} {{::midi-monitor.png|}}
 +
 +To understand MIDI data flow in Unify, see [[midi-details|How Unify processes MIDI data]].
  
 ===== Instantiating MIDI Monitor in Unify ===== ===== Instantiating MIDI Monitor in Unify =====
Line 33: Line 33:
   * Text description (see below)   * Text description (see below)
  
-The **Clear** button at the top right clears the display area, and also resets the time relative to which MIDI event-times are displayed.+The **Clear** button at the top right clears the display area, and also (starting in Unify v1.3.x) resets the time relative to which MIDI event-times are displayed.
  
-The four check-boxes in the //Filtering// area allow you to specify whether or not certain types of MIDI events will appear in the display: +The **MIDI Ch** pop-up menu lets you select whether MIDI Monitor shows incoming messages on all MIDI channels, or only one selected channel. 
-  * **System-Common and Real-Time** (NOT shown by default)+ 
 +The five check-boxes in the //Filtering// area allow you to specify whether or not certain types of MIDI events will appear in the display: 
 +  * **System-Common and Real-Time**
     * Certain MIDI controllers (especially older Yamaha keyboards) produce a continuous stream of MIDI control and timing messages, which were used for synchronization with older MIDI sequencing hardware. It is useful to suppress display of these messages, in order to monitor e.g. note/CC data.     * Certain MIDI controllers (especially older Yamaha keyboards) produce a continuous stream of MIDI control and timing messages, which were used for synchronization with older MIDI sequencing hardware. It is useful to suppress display of these messages, in order to monitor e.g. note/CC data.
     * Note the MIDI //System-Common// message category also includes //System Exclusive// messages, which are typically very large, and used for device-specific functions.     * Note the MIDI //System-Common// message category also includes //System Exclusive// messages, which are typically very large, and used for device-specific functions.
-  * **Note on/off** events correspond to MIDI keys going down and up.+  * **Note on/off** events correspond to MIDI keys going down and up
     * Every note-on has a //note number// (nn) in the range 0-127 (middle C = 60)     * Every note-on has a //note number// (nn) in the range 0-127 (middle C = 60)
     * Every note-on also has a //velocity//, also in the range 0-127, where 1 is very soft and 127 is very loud. Velocity value 0 is a special case, and is used by some MIDI controllers instead of a note-off event.     * Every note-on also has a //velocity//, also in the range 0-127, where 1 is very soft and 127 is very loud. Velocity value 0 is a special case, and is used by some MIDI controllers instead of a note-off event.
Line 46: Line 48:
     * Many CC numbers have associated "standard interpretation"; this is indicated where applicable     * Many CC numbers have associated "standard interpretation"; this is indicated where applicable
     * Some CC numbers are traditionally used for special functions, rather than indicating actual //continuous controller// activity. For example, CC#0 is used for //bank select//, and CC#32 may also be used to extend the bank selection to a 14-bit value (aka "sub bank"). Unify is quite capable of interpreting even these "non-CC" messages to e.g. control Macro knobs, and furthermore, several commercial MIDI controllers (notably the KORG nanoKontrol) use such "non-CC" messages in this way.     * Some CC numbers are traditionally used for special functions, rather than indicating actual //continuous controller// activity. For example, CC#0 is used for //bank select//, and CC#32 may also be used to extend the bank selection to a 14-bit value (aka "sub bank"). Unify is quite capable of interpreting even these "non-CC" messages to e.g. control Macro knobs, and furthermore, several commercial MIDI controllers (notably the KORG nanoKontrol) use such "non-CC" messages in this way.
 +  * **Pitch Bend**
 +    * Check to display MIDI pitch-bend (pitch wheel) messages.
 +  * **Aftertouch**
 +    * Check to display both Channel Pressure (mono aftertouch) and Polyphonic Aftertouch messages.
 +
 +===== Caveat =====
 +We recommend that you do not leave //MIDI Monitor// in a patch indefinitely, because the amount of text will build up over time, consuming extra memory and possibly bogging down your CPU.
  
 ===== Further reading ===== ===== Further reading =====
midi-monitor.1595602401.txt.gz · Last modified: 2023/05/08 18:59 (external edit)