Differences
This shows you the differences between two versions of the page.
Next revisionBoth sides next revision | |||
loopy_pro:getting_started_with_midi_learn [2024/03/17 03:33] – created espiegel123 | loopy_pro:getting_started_with_midi_learn [2024/03/17 04:01] – espiegel123 | ||
---|---|---|---|
Line 8: | Line 8: | ||
The MIDI Learn system is a quick way to map a MIDI message from a controller to an on-screen layout element: clip, button, slider, etc. | The MIDI Learn system is a quick way to map a MIDI message from a controller to an on-screen layout element: clip, button, slider, etc. | ||
+ | |||
+ | NOTE: As of Loopy Pro 1.1.16, you can use typing keyboards for MIDI Learn in addition to MIDI controllers. | ||
To MIDI Learn a user interface element: | To MIDI Learn a user interface element: | ||
* Connect the MIDI device that you want to use to trigger things in Loopy Pro. If it is a Bluetooth MIDI device, choose Bluetooth Devices from the main menu to make sure that your device is connected. | * Connect the MIDI device that you want to use to trigger things in Loopy Pro. If it is a Bluetooth MIDI device, choose Bluetooth Devices from the main menu to make sure that your device is connected. | ||
* Choose MIDI Learn from the main menu | * Choose MIDI Learn from the main menu | ||
+ | * OPTIONAL: Choose a profile to learn into. | ||
* Tap on a user interface element that you want to trigger or control with MIDI | * Tap on a user interface element that you want to trigger or control with MIDI | ||
* Touch the control on your MIDI device that you want to control/ | * Touch the control on your MIDI device that you want to control/ | ||
Line 22: | Line 25: | ||
===== MIDI Bindings ===== | ===== MIDI Bindings ===== | ||
+ | MIDI Bindings are mappings of MIDI messages (or keypresses on a typing keyboard) to Loopy Pro actions. A binding can trigger a single action or a series of actions. When you MIDI Learn, Loopy Pro creates a binding that is stored in a //profile// that you can access via the [[https:// | ||
+ | |||
+ | **More about actions and action sequences**: | ||
+ | |||
+ | ==== Control Profiles ==== | ||
+ | MIDI Bindings are are stored in control profiles (or just profiles). Project profiles are local to the project. You should generally create bindings here for elements particular to the layout -- especially any widgets (sliders, buttons, etc). Global Profiles are bindings available to all projects. These generally should not be bindings to widgets and other local elements. | ||
+ | |||
+ | Profiles can be activated and deactivated in the Control Settings panel using the check " | ||
+ | |||
+ | Loopy Pro has actions to activate, deactivate, and switch control profiles. | ||
+ | |||
+ | ===== MIDI Controllers ===== | ||
+ | |||
+ | Any MIDI source visible to Loopy Pro, including AUv3 that send MIDI can trigger MIDI bindings. | ||
+ | |||
+ | ==== Footswitch Note ==== | ||
+ | Pretty much any footswitch can be used with Loopy Pro. For the best MIDI Learn experience, a footswitch should be set up to send an ON message (cc value 127 or note velocity 127) when pressed and an OFF message (CC value 0 or note velocity 0) when released. Other setups can work but may need manual editing of the learned event. For instance, if a footswitch only sends an ON message, Loopy Pro will interpret that as a HOLD. You can manually reassign that to ON. See [[loopy_pro: | ||
+ | |||
+ | |||
+ | |||
+ | {{tag> |