2,705
edits
Changes
Jump to navigation
Jump to search
Line 218:
Line 218: − + − This allows you to easily connect any parameter in the Zynthian UI to any CC knob/slider on an external MIDI controller. ''(I intend to extend this feature to other MIDI messages, but currently only CC messages are supported.)'' Anyway, MIDI filter rules can handle any special cases, so it’s not an urgent task.+ − This works with ALL the engines, using the engine’s native MIDI-learning capability when available (and convenient) or the Zynthian’s MIDI-learning mechanism, within the MIDI filter. To be more explicit, native MIDI-learning is used for MOD-UI and ZynAddSubFX OSC parameters. All the other MIDI-mapped parameters are managed by the Zynthian’s MIDI-learning mechanism.+ − + − The MIDI-learning configuration is stored in the snapshot.+ − + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Zynthian UI User Guide (oldstable-2109) (view source)
Revision as of 18:57, 15 January 2019
, 18:57, 15 January 2019→Global MIDI-learning
<br clear=all>
<br clear=all>
=Global MIDI-learning=
=MIDI-learning=
MIDI-learning allows you to easily bind specific MIDI events with Zynthian-UI actions. There are 2 types of MIDI events you can learn:
====MIDI CC====
You get on-screen feedback during the learning process. When you enable MIDI-learning for a parameter, a small green text displaying "??" appears at the bottom of the controller/parameter area in the Zynthian UI. When the parameter is connected to a CC, the number of the assigned CC is shown in the same place.
You can map any parameter in the Zynthian UI to a CC knob/slider on your external MIDI controller. ''(I intend to extend this feature to other MIDI messages, but currently only CC messages are supported. Until then, MIDI-filter rules can be used instead.)''
Learning a MIDI-CC is quite easy:
==How to use MIDI Learning==
1. From the control screen, you click the snapshot button. You will be in CC MIDI-learn screen. It’s identical to the Control screen except that all the controllers have a tiny yellow “???” in the bottom.
2. Move a zynthian controller. Its tiny “???” will change to green while the other 3 will go back to normal state.
3. Finally, move a knob/fader in your MIDI keyboard/controller and the binding is done. The new CC number should appear in the bottom of the learned controller, replacing the tiny "???".
Of course, MIDI-learning configuration, including CC mappings, is stored and restored with snapshots.
'''Technical Note:''' MIDI-CC learning works with all the engines. It uses the engine’s native MIDI-learning capabilities when available. Zynthian’s MIDI-filter mappings are used for the rest. To be more explicit, native MIDI-learning is used for MOD-UI and ZynAddSubFX OSC parameters. All the other parameters are managed by Zynthian’s MIDI-filter mapping.
====MIDI Program Change====obscenely
You can map "SubSnapshots" (ZS3) to MIDI programs. The idea behind this feature is to have a fast preset-change mechanism that can be used on stage. In combination with the “Single Layer” feature, it turns Zynthian in a “Stage-Beast”. You can prepare a snapshot for the full performance, and use ZS3 for fast changing from a song to another, or between parts inside the same song.
Learning a SubSnapShot is obscenely easy:
1. From the control screen, you click the snapshot button '''twice'''. You will see the current list of ZS3s and a message: “Waiting for Program Change…”
2. Simply push a “Program Change” button in your keyboard/controller and the ZS3 will be stored in memory, associated with the Program number you send.
After that, you can recall any stored ZS3 by simply pushing the same PC button again. The memory-stored zs3s will be saved with your snapshot and restored when it’s loaded again.
Every zs3 includes:
Layer ID
Bank
Preset
Controller values
As you can see, it has sense in a SnapShot context, where a set of layers are defined. Zs3 changing is very fast, as no engine must be started.
====MIDI-CC Learning with touch interface====
First, you need a working touch interface in your display. If you don't have a touchscreen, you could use a mouse ...
First, you need a working touch interface in your display. If you don't have a touchscreen, you could use a mouse ...