Unify Manual

Your complete reference to PlugInGuru's creative playground!

User Tools

Site Tools

Trace:
midi-controller-files

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
midi-controller-files [2021/09/11 16:09] – [final sections] shanemidi-controller-files [2023/05/08 18:59] (current) – external edit 127.0.0.1
Line 243: Line 243:
  
 ==== Pads bank A section ==== ==== Pads bank A section ====
-The MPD2018 also supports three banks of MIDI-command assignments for the sixteen physical knobs, yielding a total of 48 logical knobs, but as this is only a partial tutorial example, there are only six "no" lines, all for pad bank A. These are divided into two groups of three lines.+The MPD2018 also supports three banks of MIDI-command assignments for the sixteen physical pads, yielding a total of 48 logical pads, but as this is only a partial tutorial example, there are only six "no" lines, all for pad bank A. These are divided into two groups of three lines.
  
 The first three "no" lines are for the first three pads along the top row of the MPD218 (designated 13, 14, and 15) on the front panel). All three pads are set up to send a specific fractional value (range 0.0 to 1.0) to Unify's Macro8 knob, setting it to a specific position. The first three "no" lines are for the first three pads along the top row of the MPD218 (designated 13, 14, and 15) on the front panel). All three pads are set up to send a specific fractional value (range 0.0 to 1.0) to Unify's Macro8 knob, setting it to a specific position.
Line 280: Line 280:
   - Some devices (the KORG nanoKONTROL2 is a major example) generate MIDI CC messages which are normally reserved for special purposes, e.g. CC#0 (default assignment for the first slider) would normally be interpreted by Unify and most other MIDI instruments as //MIDI Bank Select//. With MIDI controller files, you can effectively intercept such messages, and specify exactly how they are to be interpreted, knowing they will be suppressed at the early stages of Unify's MIDI processing, and won't go on to trigger their more conventional functions.   - Some devices (the KORG nanoKONTROL2 is a major example) generate MIDI CC messages which are normally reserved for special purposes, e.g. CC#0 (default assignment for the first slider) would normally be interpreted by Unify and most other MIDI instruments as //MIDI Bank Select//. With MIDI controller files, you can effectively intercept such messages, and specify exactly how they are to be interpreted, knowing they will be suppressed at the early stages of Unify's MIDI processing, and won't go on to trigger their more conventional functions.
  
 +===== Suppressing specific MIDI messages =====
 +**As of Unify v1.9**, you can put the word //suppress// in place of a normal command-path, to entirely suppress (filter out) a specific CC message.
  
 +This was added in response to feedback from a user who found that a Roland D-50, used as a MIDI controller, sends a MIDI CC#123 (all notes off) message when the last key is released, and this can cause problems with some plug-ins. Adding the line
 +
 +  cc 123 suppress
 +
 +to the active MIDI Controller file will cause this message to be suppressed (filtered out).
  
midi-controller-files.1631376550.txt.gz · Last modified: 2023/05/08 18:59 (external edit)