Differences

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

--- loopy_pro:midi_troubleshooting [2024/02/11 11:29] – espiegel123
+++ loopy_pro:midi_troubleshooting [2024/04/01 14:18] – add section about looking through bindings 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 121: / Line 124: @@
 {{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.
+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.... =====