Differences

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

--- loopy_pro:midi_troubleshooting [2024/02/09 09:03] – add more suggestions espiegel123
+++ loopy_pro:midi_troubleshooting [2024/04/13 04:31] (current) – espiegel123
@@ Line 1: / Line 1: @@
 ====== Loopy Pro: MIDI Troubleshooting ======
-Loopy Pro's MIDI Learn is generally straightforward and transparent. If you run into problems, the information on this page should help you solve the problem and, if not, it should provide you with the details needed for Loopy Pro support or other users to resolve your problem.
+Loopy Pro's [[loopy_pro:getting_started_with_midi_learn| MIDI Learn]] is generally straightforward and transparent. If you run into problems, the information on this page should help you solve the problem and, if not, it should provide you with the details needed for Loopy Pro support or other users to resolve your problem.
+If you have not yet seen it, you main want to see the page [[loopy_pro:getting_started_with_midi_learn|Loopy Pro: Getting Started with MIDI Learn]].
 Here is a video showing how MIDI Learn should work.
@@ Line 11: / Line 13: @@
 If MIDI Learn is "kind of" working jump down to the MIDI Learn section further down the page.
-The two most common problems people run into are:
+The three most common problems people run into are:
-  * the controller not sending an "on" message on a button/key press and an "off" message on button/key release. This issue can generally be solved by manually setting the trigger to "on". (See the section MIDI Learn below)
+  * **Controller not sending On/Off on press/release**. Loopy Pro expects a controller to send an "on" message on a button/key press and an "off" message on button/key release. If your controller is not set up to do that, Loopy Pro will likely guess wrong about what the intended trigger is. It might choose Hold instead of On. This issue can generally be solved by manually setting the trigger to "On" in the binding or by configuring the MIDI device to send On on press and Off on release.. (See the section MIDI Learn below)
-  * the controller misbehaving when Loopy tries to send messages to the controller. If Loopy or your controller act unpredictably when the controller sends a message try turning off feedback to the device in Loopy Pro's Control Settings panel.
+  * **Controller Feedback**. By default Loopy Pro sends feedback back to a controller so that it can update its LEDs. If Loopy or your controller act unpredictably when the controller sends a message try turning off feedback to the device in Loopy Pro's Control Settings panel.
+  * **On/Hold/Double-Tap mapped to the same event**. Loopy Pro can map different actions to On, Hold and Double-Tap but some care needs to be taken when setting them up. Hold and Double-Tap triggers have a //Defer Other Actions// option in the trigger setup. If this option is not turned on, Loopy Pro will immediately process the On as soon as it comes in. So, on a Hold, for instance, the On is processed and then the Hold is activated. If you turn on Defer Other Actions, Loopy Pro will wait to act until it knows whether the the On is part of a hold or double-tap. This will result in a slight delay but ensures that On is not falsely triggered. In some cases, Loopy Pro can correct for the misfire, but in some cases that is not possible.
@@ Line 23: / Line 26: @@
   * Use a standalone MIDI Monitor to see if your iPad or iPhone is seeing MIDI from the controller.
   * If MIDI is seen, make a note of what messages (and on what channels), your controller is sending
-  * MIDI Learn triggering a clip in Loopy Pro's default document.
+  * MIDI Learn triggering a clip in a new project made from Loopy Pro's default document.
   * If strange things happen when you send a MIDI message you mapped, turn off the **Feedback Enabled** for the controller in Loopy Pro's Control Settings
 ==== Use A MIDI Monitor to See if MIDI Is Received ====
+ of
 Before troubleshooting:
   * Fully shut down your device using "Slide to power off" rather than putting it to sleep at waking it up.
@@ Line 55: / Line 58: @@
   * Launch Loopy Pro
   * Create a new document using Loopy Pro's default document
+  * Choose Clip Settings from the main menu
+  * Scroll to the bottom of the settings panel and choose **Restore Defaults**
+  * In Control Settings, turn off any Global Profiles that are enabled. This step is to ensure there is not some conflict with MIDI bindings that might be interfering.
   * Turn on MIDI Learn mode
   * Tap on the upper-left clip
@@ Line 84: / Line 90: @@
-===== More MIDI Troubleshooting Tips =====
+====== More MIDI Troubleshooting Tips ======
-====== Using a MIDI Monitor to Examine MIDI ======
+===== Changing/Correcting A MIDI Learn=====
+If you MIDI Learn and something isn't quite right, tap on the MIDI Learned message to see options you can change.
+{{:loopy_pro:loopy_pro-midilearnfix-img_5939.jpeg?400|}}
+{{:loopy_pro:loopypro-midilearnfiximg_5940.jpeg?400|}}
+===== Using a MIDI Monitor to Examine MIDI =====
 It is sometimes useful to be able to see the MIDI coming in from controllers or that is being sent from between plugins or widgets. A MIDI Monitoring AUv3 is very handy. Some useful (and free) MIDI Monitor AUv3 are:
@@ Line 112: / Line 127: @@
 {{youtube>cqjowyNR4eM?large}}
+===== Check Your MIDI Bindings =====
+If MIDI events are resulting in unexpected behavior and you have turned off MIDI Feedback, look at all of your MIDI Bindings. MIDI Bindings are the mapping of MIDI events to actions. They are listed and can be edited through the Control Settings panel.
-==== More.... ====
+If a particular MIDI event is causing a problem, make a note of what the event is. If you aren't sure, use a MIDI monitor (as described elsewhere on this page) to see what MIDI message is resulting in the unexpected behavior.
+  * Choose Control Settings to display the panel.
+  * Look inside each listed profile.
+  * The MIDI messages that are bound to action are listed in the profiles.
+  * Find the MIDI message and tap on it to view the details of the actions bound to it.
+  * Look through all the profiles in case the same message is mapped in multiple profiles.
+===== More.... =====
 **What is your pedal sending?** The Loopy Pro's MIDI Learn assumes that a pedal sends a value when pressed and another value when released. If your pedal does not send a CC value of 127 (or note velocity of 127) when pressed and 0 when released, it may throw off what Loopy Pro thinks you are trying to do. Loopy Pro allows you to specify the correct trigger if it makes the wrong guess about what the trigger is. You may want to use a MIDI Monitor to see what your pedal is sending. Using a MIDI Monitor is covered elsewhere on this page.