Troubleshooting MIDI - Revision history

Edwards: /* Basic Troubleshooting Procedure */

2025-11-14T01:25:00Z

Basic Troubleshooting Procedure

← Older revision		Revision as of 11:25, 14 November 2025
Line 54:		Line 54:
	Use a standalone MIDI Monitor such as ShowMIDI (which can also be loaded as an AUv3), MIDI Wrench, MIDI Scope, or any of the other MIDI Monitors that can run standalone. ShowMIDI is convenient because it runs as both and AU and a standalone app and it gives you a picture the recent activity (as opposed to the long type monitors that can sometimes show an overwhelming amount of data).		Use a standalone MIDI Monitor such as ShowMIDI (which can also be loaded as an AUv3), MIDI Wrench, MIDI Scope, or any of the other MIDI Monitors that can run standalone. ShowMIDI is convenient because it runs as both and AU and a standalone app and it gives you a picture the recent activity (as opposed to the long type monitors that can sometimes show an overwhelming amount of data).

	When you launch the monitor, ~~'''~~check to make sure that your MIDI Device is listed~~'''~~. If your controller is connected to an audio/MIDI or MIDI interface with a standard MIDI cable, the MIDI will come from the MIDI port of the interface.		'''Make sure your controller is seen'''. When you launch the monitor, check to make sure that your MIDI Device is listed. If your controller is connected to an audio/MIDI or MIDI interface with a standard MIDI cable, the MIDI will come from the MIDI port of the interface.

	If your device is not listed, the OS does not see it. Loopy Pro will see any device seen by the OS. If the device isn't seen, you should check your connections and make sure that it is receiving enough power. You may want to contact the MIDI/audio interface manufacturer to ensure that it is compatible with iOS. Check to see if there is a firmware update for the interface.		'''If your device is not listed''', the OS does not see it. Loopy Pro will see any device seen by the OS.

	If the interface is ~~listed, press~~ a ~~button on your controller and make note of what is being sent~~. If ~~no message~~ is ~~received~~, ~~check your cables and confirm~~ that the ~~interface~~ or ~~controller is compatible with iOS~~.		* Check your connections. Bad cables or mis-behaving hubs are common problems.
			* You may want to contact the MIDI/audio interface manufacturer to ensure that it is compatible with iOS. Check to see if there is a firmware update for the interface.
			* If the controller is connected via USB, make sure that you have supplied enough power to the hub or USB dongle. Some controllers require more power than the iPad or iPhone supply. Some require more power than the Apple Camera Adapter plus Apple USB charger supplies.

	If the controller is ~~connected via USB~~, ~~make sure~~ that ~~you have supplied enough power. Some controllers require more power than~~ the ~~iPad~~ or ~~iPhone supply~~. ~~Some require more power than the Apple Camera Adapter plus Apple USB charger supplies~~.		'''If the interface is listed''', press a button on your controller and make note of what is being sent. If no message is received, check your cables and confirm that the interface or controller is compatible with iOS.

			'''If MIDI Messages are being received''', check to see what messages are being sent. We recommend [[Footswitches#Testing Your Controller\|this procedure]].

	See [[MIDI Monitor Usage]] for more information about using a MIDI Monitor in Loopy Pro.		See [[MIDI Monitor Usage]] for more information about using a MIDI Monitor in Loopy Pro.

Edwards: various tweaks

2025-11-14T00:23:11Z

various tweaks

Edwards: /* MIDI Feedback */

2025-05-01T04:18:50Z

MIDI Feedback

← Older revision		Revision as of 14:18, 1 May 2025
Line 92:		Line 92:

	By default, Loopy Pro sends feedback to a controller when Loopy received MIDI that you have mapped to something. For many controllers, this allows them to update their display to reflect Loopy's state. For example, if a pad is mapped to play a clip, the pad will light up with the clip is playing.		By default, Loopy Pro sends feedback to a controller when Loopy received MIDI that you have mapped to something. For many controllers, this allows them to update their display to reflect Loopy's state. For example, if a pad is mapped to play a clip, the pad will light up with the clip is playing.

			See the [https://loopypro.com/manual/#midi-state-feedback manual] for more about MIDI state feedback to controllers.

	=== Feedback Loops ===		=== Feedback Loops ===

Edwards: add information about testing state feedback

2025-05-01T04:15:23Z

add information about testing state feedback

← Older revision		Revision as of 14:15, 1 May 2025
Line 88:		Line 88:
	'''HOLD''' rather than '''ON''' learned. Some controllers only send an ON message and no release/off message. If this is the case, Loopy Pro will see that as a HOLD message. You can tell Loopy Pro to use ON instead of hold. Hold messages will result in delayed response. To change HOLD to ON, tap on the part of the MIDI Learn panel that displays the learned message. You will see options for the triggering event, choose ON. If your controller is configurable, set it to send an ON when pressed and OFF when released.		'''HOLD''' rather than '''ON''' learned. Some controllers only send an ON message and no release/off message. If this is the case, Loopy Pro will see that as a HOLD message. You can tell Loopy Pro to use ON instead of hold. Hold messages will result in delayed response. To change HOLD to ON, tap on the part of the MIDI Learn panel that displays the learned message. You will see options for the triggering event, choose ON. If your controller is configurable, set it to send an ON when pressed and OFF when released.

	= MIDI Feedback =		== MIDI Feedback ==
	If you get surprising response when controlling Loopy via MIDI, the problem may be an inadvertent feedback loop, or the controller may not respond well to the feedback that Loopy Pro sends.		If you get surprising response when controlling Loopy via MIDI, the problem may be an inadvertent feedback loop, or the controller may not respond well to the feedback that Loopy Pro sends.

	By default, Loopy Pro sends feedback to a controller when Loopy received MIDI that you have mapped to something. For many controllers, this allows them to update their display to reflect Loopy's state. For example, if a pad is mapped to play a clip, the pad will light up with the clip is playing. Some controllers, however, misinterpret the feedback and may send it back to Loopy (creating a feedback loop) OR it might interpret as some sort of button press or bank change.		By default, Loopy Pro sends feedback to a controller when Loopy received MIDI that you have mapped to something. For many controllers, this allows them to update their display to reflect Loopy's state. For example, if a pad is mapped to play a clip, the pad will light up with the clip is playing.

			=== Feedback Loops ===
			Some controllers, however, misinterpret the feedback and may send it back to Loopy (creating a feedback loop) OR it might interpret as some sort of button press or bank change.

	To see if feedback is the issue, open Loopy's Control Settings panel. Find your MIDI controller in the list of MIDI sources at the top of the panel. Turn off the setting labeled '''Feedback Enabled''' and see if that solves things.		To see if feedback is the issue, open Loopy's Control Settings panel. Find your MIDI controller in the list of MIDI sources at the top of the panel. Turn off the setting labeled '''Feedback Enabled''' and see if that solves things.
Line 97:		Line 100:
	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.

	= Control Profile Issues =		=== Testing State Feedback ===
			If Feedback is enabled for your controller but is not being being updated when value or control is changed in Loopy Pro, you may want to check to see if your controller responds to the type of MIDI Feedback that Loopy Pro provides. To test if the controller responds to state feedback, do the following:

			* Use a MIDI monitor to determine the message sent by a control on your controller that you want to test.
			* Create a new Loopy Pro project from Loopy Pro's default project.
			* Choose Control Settings from the main menu.
			* Make sure that feedback is enabled for your controller.
			* Turn off all global profiles.
			* Add the controller to Loopy Pro's mixer by tapping the + and choosing Add MIDI.
			* Add a button widget to the canvas.
			* Tap on the button widget to open its editor
			* In the Press/Release section, add a Send MIDI Message action. Set it to the message you want to test.
			* Press and hold the button. The LED should light up on your controller or go to its maximum.
			* Release the button. The LED should turn off or the display switch to its minimum.

			== Control Profile Issues ==

	== Check Your MIDI Bindings ==		=== Check Your MIDI Bindings ===
	If MIDI events are resulting in unexpected behavior and you have turned off MIDI Feedback, look at all of your [https://loopypro.com/manual/#adding-bindings-manually MIDI Bindings]. Bindings can be view in the Control Settings panel.		If MIDI events are resulting in unexpected behavior and you have turned off MIDI Feedback, look at all of your [https://loopypro.com/manual/#adding-bindings-manually MIDI Bindings]. Bindings can be view in the Control Settings panel.

Line 110:		Line 128:
	* Look through all the profiles in case the same message is mapped in multiple profiles.		* Look through all the profiles in case the same message is mapped in multiple profiles.

	== Global Profile Issues ==		=== Global Profile Issues ===
	MIDI bindings learned to or created in a global profile can behave unexpectedly if the target is a clip or widget. Global profiles are best used for actions that don't reference specific items on the page.		MIDI bindings learned to or created in a global profile can behave unexpectedly if the target is a clip or widget. Global profiles are best used for actions that don't reference specific items on the page.

Line 120:		Line 138:


	= Changing/Correcting A MIDI Learn =
			== Changing/Correcting A MIDI Learn ==
	If you MIDI Learn and something isn't quite right, you can edit the trigger and other options. For example, if Loopy Pro chose HOLD as the trigger rather than ON, you can fix that. Tap on the MIDI Learned message to see options you can change.		If you MIDI Learn and something isn't quite right, you can edit the trigger and other options. For example, if Loopy Pro chose HOLD as the trigger rather than ON, you can fix that. Tap on the MIDI Learned message to see options you can change.

Line 127:		Line 146:
	[[File:loopypro-midilearnfiximg_5940.jpeg\|400px]]		[[File:loopypro-midilearnfiximg_5940.jpeg\|400px]]

	= Other Causes of Common Problems =		== Other Causes of Common Problems ==
	If the troubleshooting procedure didn't identify the problem, perhaps you are encountering one of these common issues:		If the troubleshooting procedure didn't identify the problem, perhaps you are encountering one of these common issues:

Line 135:		Line 154:
	* '''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.		* '''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.

	= More... =		== More... ==

	== MIDI-Controlled Effects Not Responding ==		=== MIDI-Controlled Effects Not Responding ===
	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.

	== Find out what your pedal is sending ==		=== Find out what your pedal is 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 Usage\|MIDI Monitor]] to see what your pedal is sending. Using a MIDI Monitor is covered elsewhere on this page.		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 Usage\|MIDI Monitor]] to see what your pedal is sending. Using a MIDI Monitor is covered elsewhere on this page.

	== ~~Make~~ Turn Off Feedback in Your Controller ~~- Morningstar Pedals~~ ==		=== Morningstar Pedals - Turn Off Feedback in Your Controller ===
	'''For the Morningstar pedals''', use the pedal's global configuration menu to turn ''Cross MIDI Thru'' '''Off''' and ''Ignore MIDI Clock'' '''On'''.		'''For the Morningstar pedals''', use the pedal's global configuration menu to turn ''Cross MIDI Thru'' '''Off''' and ''Ignore MIDI Clock'' '''On'''.

Michael at 01:57, 20 June 2024

2024-06-20T01:57:40Z

Edwards: re-organize and improve

2024-06-19T19:56:17Z

re-organize and improve

Show changes

Michael at 06:29, 13 June 2024

2024-06-13T06:29:20Z

← Older revision		Revision as of 16:29, 13 June 2024
Line 1:		Line 1:
	[[Category:Common Issues and Troubleshooting]]		[[Category:Common Issues and Troubleshooting\|3]]

	Loopy Pro's [[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.		Loopy Pro's [[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.

Michael: Michael moved page MIDI Troubleshooting to Troubleshooting MIDI

2024-06-13T06:10:54Z

Michael moved page MIDI Troubleshooting to Troubleshooting MIDI

← Older revision		Revision as of 16:10, 13 June 2024
(No difference)

Michael at 06:00, 13 June 2024

2024-06-13T06:00:47Z

← Older revision		Revision as of 16:00, 13 June 2024
Line 1:		Line 1:
	[[Category:Common Issues and Troubleshooting]]		[[Category:Common Issues and Troubleshooting]]
	~~= MIDI Troubleshooting =~~

	Loopy Pro's [[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.		Loopy Pro's [[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.

Michael: Michael moved page Midi Troubleshooting to MIDI Troubleshooting without leaving a redirect

2024-06-13T04:24:09Z

Michael moved page Midi Troubleshooting to MIDI Troubleshooting without leaving a redirect

← Older revision		Revision as of 14:24, 13 June 2024
(No difference)

← Older revision		Revision as of 10:23, 14 November 2025
Line 20:		Line 20:
	Loopy Pro's [[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.		Loopy Pro's [[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 [[Getting Started With MIDI Learn]].		See the page [[Getting Started With MIDI Learn]] if you have not already visited it.

	Here is a video showing how MIDI Learn should work.		Here is a video showing how MIDI Learn should work.
Line 27:		Line 27:

	The most common problems people run into related to MIDI Learn are:		The most common problems people run into related to MIDI Learn are:
	* '''The controller not being seeing at all'''. The Basic Troubleshooting Procedure will help you identify if your iPad or iPhone is seeing the controller at all.		* '''The controller not being seeing at all'''. The Basic Troubleshooting Procedure found on this page will help you identify if your iPad or iPhone is seeing the controller at all.
	* '''Controller not sending an "on" message on press and an "off" message on release'''. Loopy Pro's MIDI Learn 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).		* '''Controller not sending an "on" message on press and an "off" message on release'''. If your controller sends MIDI CCs or MIDI notes, Loopy Pro's MIDI Learn expects the controller to send an ''on'' message on press and an ''off'' message on release. ''On'' messages are a note velocity or CC value greater than 0; ''off'' messages are note velocity 0 or CC value 0. Typically, a note velocity/CC value of 127 is preferred. 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 when learning from the controller. This issue can generally be solved by manually setting the trigger to "On" in the MIDI binding or by configuring the MIDI device to send On on press and Off on release. (See the section MIDI Learn below). Note that a controller must send notes or CCs to be able to use hold and double tap triggers.
	* '''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.		* '''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.		* '''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. For more information see this [[Tech Note:MIDI Bindings\|tech note]].
	If MIDI Learn is ~~nog~~ working at all, start with the ''Basic Troubleshooting Procedure'' below.		If MIDI Learn is not working at all, start with the ''Basic Troubleshooting Procedure'' below.

	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.

	== Basic Troubleshooting Procedure ==		== Basic Troubleshooting Procedure ==
	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.		* 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 (such as the free ShowMIDI app/plugin) 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
	* MIDI Learn triggering a clip in a new project made from Loopy Pro's default document.		* MIDI Learn triggering a clip in a new project made from Loopy Pro's default document.
Line 67:		Line 67:
	If you have confirmed that your device is receiving MIDI, the next step is to see what happens when you MIDI Learn from the device.		If you have confirmed that your device is receiving MIDI, the next step is to see what happens when you MIDI Learn from the device.

	Here is a video showing how MIDI Learn should work. If something different happens, make note of what happens differently as that will point the direction to how to solve the problem.		Here is a video showing how MIDI Learn should work. If something different happens, make note of what happens differently as that will point the direction to how to solve the problem.<youtube>HYdBRZSWaQA</youtube>


	<youtube>HYdBRZSWaQA</youtube>

	To troubleshoot after confirming that MIDI is being received from your controller:		To troubleshoot after confirming that MIDI is being received from your controller:

← Older revision		Revision as of 11:57, 20 June 2024
Line 1:		Line 1:
	[[Category:Common Issues and Troubleshooting\|3]]		[[Category:Common Issues and Troubleshooting\|3]]

	~~= Troubleshooting MIDI =~~
	This page is intended to help you solve MIDI related problems. Common issues are:		This page is intended to help you solve MIDI related problems. Common issues are:

Line 18:		Line 17:
	If MIDI bindings start triggering the wrong widget or clip, the problem may be related to the profile being used. See [[Troubleshooting MIDI#Control Profile Issues\|Control Profile Issues]] below.		If MIDI bindings start triggering the wrong widget or clip, the problem may be related to the profile being used. See [[Troubleshooting MIDI#Control Profile Issues\|Control Profile Issues]] below.

	== MIDI Learn and Connection Troubleshooting ==		= MIDI Learn and Connection Troubleshooting =
	Loopy Pro's [[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.		Loopy Pro's [[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.

Line 36:		Line 35:
	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.

	=== Basic Troubleshooting Procedure ===		== Basic Troubleshooting Procedure ==
	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

Line 45:		Line 44:
	* 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		* 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 ===		== Use A MIDI Monitor to See if MIDI Is Received ==
	Before troubleshooting:		Before troubleshooting:
	* Fully shut down your device using "Slide to power off" rather than putting it to sleep at waking it up.		* Fully shut down your device using "Slide to power off" rather than putting it to sleep at waking it up.
Line 65:		Line 64:
	See [[MIDI Monitor Usage]] for more information about using a MIDI Monitor in Loopy Pro.		See [[MIDI Monitor Usage]] for more information about using a MIDI Monitor in Loopy Pro.

	=== Perform MIDI Learn ===		== Perform MIDI Learn ==
	If you have confirmed that your device is receiving MIDI, the next step is to see what happens when you MIDI Learn from the device.		If you have confirmed that your device is receiving MIDI, the next step is to see what happens when you MIDI Learn from the device.

Line 89:		Line 88:
	'''HOLD''' rather than '''ON''' learned. Some controllers only send an ON message and no release/off message. If this is the case, Loopy Pro will see that as a HOLD message. You can tell Loopy Pro to use ON instead of hold. Hold messages will result in delayed response. To change HOLD to ON, tap on the part of the MIDI Learn panel that displays the learned message. You will see options for the triggering event, choose ON. If your controller is configurable, set it to send an ON when pressed and OFF when released.		'''HOLD''' rather than '''ON''' learned. Some controllers only send an ON message and no release/off message. If this is the case, Loopy Pro will see that as a HOLD message. You can tell Loopy Pro to use ON instead of hold. Hold messages will result in delayed response. To change HOLD to ON, tap on the part of the MIDI Learn panel that displays the learned message. You will see options for the triggering event, choose ON. If your controller is configurable, set it to send an ON when pressed and OFF when released.

	== MIDI Feedback ==		= MIDI Feedback =
	If you get surprising response when controlling Loopy via MIDI, the problem may be an inadvertent feedback loop, or the controller may not respond well to the feedback that Loopy Pro sends.		If you get surprising response when controlling Loopy via MIDI, the problem may be an inadvertent feedback loop, or the controller may not respond well to the feedback that Loopy Pro sends.

Line 98:		Line 97:
	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.

	== Control Profile Issues ==		= Control Profile Issues =

	=== Check Your MIDI Bindings ===		== Check Your MIDI Bindings ==
	If MIDI events are resulting in unexpected behavior and you have turned off MIDI Feedback, look at all of your [https://loopypro.com/manual/#adding-bindings-manually MIDI Bindings]. Bindings can be view in the Control Settings panel.		If MIDI events are resulting in unexpected behavior and you have turned off MIDI Feedback, look at all of your [https://loopypro.com/manual/#adding-bindings-manually MIDI Bindings]. Bindings can be view in the Control Settings panel.

Line 111:		Line 110:
	* Look through all the profiles in case the same message is mapped in multiple profiles.		* Look through all the profiles in case the same message is mapped in multiple profiles.

	=== Global Profile Issues ===		== Global Profile Issues ==
	MIDI bindings learned to or created in a global profile can behave unexpectedly if the target is a clip or widget. Global profiles are best used for actions that don't reference specific items on the page.		MIDI bindings learned to or created in a global profile can behave unexpectedly if the target is a clip or widget. Global profiles are best used for actions that don't reference specific items on the page.

Line 121:		Line 120:


	== Changing/Correcting A MIDI Learn ==		= Changing/Correcting A MIDI Learn =
	If you MIDI Learn and something isn't quite right, you can edit the trigger and other options. For example, if Loopy Pro chose HOLD as the trigger rather than ON, you can fix that. Tap on the MIDI Learned message to see options you can change.		If you MIDI Learn and something isn't quite right, you can edit the trigger and other options. For example, if Loopy Pro chose HOLD as the trigger rather than ON, you can fix that. Tap on the MIDI Learned message to see options you can change.

Line 128:		Line 127:
	[[File:loopypro-midilearnfiximg_5940.jpeg\|400px]]		[[File:loopypro-midilearnfiximg_5940.jpeg\|400px]]

	== Other Causes of Common Problems ==		= Other Causes of Common Problems =
	If the troubleshooting procedure didn't identify the problem, perhaps you are encountering one of these common issues:		If the troubleshooting procedure didn't identify the problem, perhaps you are encountering one of these common issues:

Line 136:		Line 135:
	* '''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.		* '''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.

	== More... ==		= More... =

	=== MIDI-Controlled Effects Not Responding ===		== MIDI-Controlled Effects Not Responding ==
	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.

	=== Find out what your pedal is sending ===		== Find out what your pedal is 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 Usage\|MIDI Monitor]] to see what your pedal is sending. Using a MIDI Monitor is covered elsewhere on this page.		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 Usage\|MIDI Monitor]] to see what your pedal is sending. Using a MIDI Monitor is covered elsewhere on this page.

	=== Make Turn Off Feedback in Your Controller - Morningstar Pedals ===		== Make Turn Off Feedback in Your Controller - Morningstar Pedals ==
	'''For the Morningstar pedals''', use the pedal's global configuration menu to turn ''Cross MIDI Thru'' '''Off''' and ''Ignore MIDI Clock'' '''On'''.		'''For the Morningstar pedals''', use the pedal's global configuration menu to turn ''Cross MIDI Thru'' '''Off''' and ''Ignore MIDI Clock'' '''On'''.