User Tools
app_control_via_midi
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| app_control_via_midi [2024/11/20 16:55] – [Direct Control] mware | app_control_via_midi [2024/11/20 16:56] (current) – [Direct Control] mware | ||
|---|---|---|---|
| Line 10: | Line 10: | ||
| * MIDI routing is more intuitive. It's natural to think if you're controlling something with MIDI you'd route the MIDI directly to it. | * MIDI routing is more intuitive. It's natural to think if you're controlling something with MIDI you'd route the MIDI directly to it. | ||
| **Disadvantages** | **Disadvantages** | ||
| - | * CC values are limited to a range of 128 steps. That can result in " | + | * CC values are limited to a range of 128 steps. That can result in " |
| * A few hosts don't handle direct routing of CC's to, for instance, effect plugins. | * A few hosts don't handle direct routing of CC's to, for instance, effect plugins. | ||
| * Each app handles MIDI mapping differently so one has to learn the hard coded CCs or the mapping system for each. | * Each app handles MIDI mapping differently so one has to learn the hard coded CCs or the mapping system for each. | ||
app_control_via_midi.1732150552.txt.gz · Last modified: 2024/11/20 16:55 by mware
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
