Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
loopy_pro:midi_troubleshooting [2024/02/06 15:02] – 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: 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' |
+ | |||
+ | If you have not yet seen it, you main want to see the page [[loopy_pro: | ||
Here is a video showing how MIDI Learn should work. | 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. | 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 | + | * **Controller |
- | * 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 |
+ | * **On/ | ||
===== Basic Troubleshooting Procedure ===== | ===== Basic Troubleshooting Procedure ===== | ||
Line 19: | Line 23: | ||
If you aren't sure where to start, start with this procedure. The outline is | If you aren't sure where to start, start with this procedure. The outline is | ||
+ | * Reboot your device. | ||
* Use a standalone MIDI Monitor to see if your iPad or iPhone is seeing MIDI from the controller. | * 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 | * If MIDI is seen, make a note of what messages (and on what channels), your controller is sending | ||
Line 72: | Line 77: | ||
If that does not solve your problem, you may want to see if your pedal has a setting to ignore incoming MIDI in case something else is sending MIDI back to your device. | If that does not solve your problem, you may want to see if your pedal has a setting to ignore incoming MIDI in case something else is sending MIDI back to your device. | ||
+ | ==== Other Causes of Common Problems ==== | ||
+ | If the troubleshooting procedure didn't identify the problem, perhaps you are encountering one of these common issues: | ||
- | ===== More MIDI Troubleshooting Tips ===== | + | * **Insufficient power supplied to the device**. Some MIDI devices require more power than the iPad or iPhone can supply. Some require more than the Apple USB charger supplies. This can be an issue when using Apple' |
+ | * **Bad cables or bad connection**. If your iPhone/iPad doesn' | ||
+ | * **Poor quality MIDI adapter**. Some cheap 5-pin MIDI to USB connectors don't work well. | ||
+ | * **Network MIDI**. For reasons that remain mysterious, there are some external MIDI devices that do not work well when Network MIDI is active. By default, Loopy Pro leaves Network MIDI off. Check the setting in Loopy Pro's System Settings to make sure that Network MIDI is off. | ||
- | ====== Using a MIDI Monitor to Examine MIDI ====== | + | |
+ | ====== More MIDI Troubleshooting Tips ====== | ||
+ | |||
+ | ===== Changing/ | ||
+ | |||
+ | If you MIDI Learn and something isn't quite right, tap on the MIDI Learned message to see options you can change. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | ===== 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: | 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 102: | Line 124: | ||
{{youtube> | {{youtube> | ||
+ | ===== Check Your MIDI Bindings ===== | ||
- | ==== More.... ==== | + | 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.... ===== | ||
**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. | **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. | ||
Line 120: | Line 151: | ||
If you have an AUv3 such as a sampler that responds to MIDI and which is not responding, you may need to turn off idling for that effect. Normally, Loopy puts effects that aren't receiving any audio input to sleep in order to free up CPU. This is called idling. To turn off idling, open the AUv3 window. Long-press on the label that says On, Off, or Idle and turn off //Enable Idle Mode// in the panel that pops up. | If you have an AUv3 such as a sampler that responds to MIDI and which is not responding, you may need to turn off idling for that effect. Normally, Loopy puts effects that aren't receiving any audio input to sleep in order to free up CPU. This is called idling. To turn off idling, open the AUv3 window. Long-press on the label that says On, Off, or Idle and turn off //Enable Idle Mode// in the panel that pops up. | ||
+ | |||
+ | {{tag> | ||