This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revisionBoth sides next revision |
| loopy_pro:midi_troubleshooting [2024/03/17 04:08] – link to new midi learn page espiegel123 | loopy_pro:midi_troubleshooting [2024/03/29 04:23] – add more information for On/Hold... espiegel123 |
|---|
| |
| The three 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. |
| * having more than one binding to the same midi event. While it is possible to use On, Double Tap and Hold for the same MIDI event, some care needs to be taken when setting these up -- and can result in added latency when processing a simple on. | * **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. |
| |
| |
espiegel123