Differences

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

--- midi-monitor [2021/09/03 01:23] – shane
+++ midi-monitor [2022/02/04 15:10] – external edit 127.0.0.1
@@ Line 6: / Line 6: @@
 To understand MIDI data flow in Unify, see [[midi-details|How Unify processes MIDI data]].
-===== 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.
 ===== Instantiating MIDI Monitor in Unify =====
 //MIDI Monitor// can be inserted or swapped into //any// plug-in slot in Unify.
@@ Line 50: / Line 48: @@
     * 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.
+===== 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 =====