Differences

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

--- loopy_pro_troubleshooting [2024/02/04 05:09] – [MIDI LEARN - How It Should Work] tweak wording espiegel123
+++ loopy_pro_troubleshooting [2024/04/03 06:22] (current) – espiegel123
@@ Line 3: / Line 3: @@
 This page covers tips for troubleshooting Loopy Pro. If you have not checked Loopy Pro's manual, you may want to start by taking a look at the [[https://loopypro.com/manual/|Loopy Pro Manual]] a link to it is found in Loopy Pro's Help menu.
+Related Troubleshooting articles:
+  * [[loopy_pro:troubleshooting_audio_problems|Troubleshooting Audio Problems]]
+  * [[loopy_pro:troubleshooting_first_loop|Loopy Pro: Troubleshooting Your First Loop]]
+  * [[loopy_pro:midi_troubleshooting|Loopy Pro: MIDI Troubleshooting]]
+  * [[loopy_pro:troubleshooting_transients|Loopy Pro: Troubleshooting Transients]]
+===== No Audio Input or Output =====
+See [[loopy_pro:troubleshooting_audio_problems|Loopy Pro: Troubleshooting  Audio Connections]]
 ===== Audio Levels Of Recorded Tracks Seems Too Loud =====
@@ Line 10: / Line 18: @@
 To turn off Echo Cancellation, tap on the mic icon in the mixer to see the input options and turn off Echo Cancellation. If you don't plan on using the mic, you might even want to delete that channel from the mixer.
-===== Using a MIDI Monitor to Examine MIDI =====
+===== MIDI Pedal/Learn/Controller Troubleshooting =====
-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:
+see: [[loopy_pro:midi_troubleshooting|Loopy Pro: MIDI Troubleshooting]]
-  * [[https://apps.apple.com/us/app/showmidi/id6472608850|Show MIDI]] - ShowMIDI is a non-logging style MIDI monitor that shows current activity. Because it doesn't log data, it let's you focus on what is happening know without having to wade through a large list of messages. You may also want a logging style MIDI monitor (all the others below are logging style) plug-in.
-  * [[https://apps.apple.com/us/app/streambyter/id1398712641|Streambyter]] - Streambyter is a free iOS MIDI-processing plugin that also has a MIDI monitor built-in. As a MIDI processor Streambyter might be intimidating, but the MIDI Monitor works well and can be used without knowing about StreamByter.
-  * [[https://apps.apple.com/us/app/mfxmonitor/id1451193551|mfxMonitor]] is a free MIDI monitor from Streambyter's developer
-  * [[https://apps.apple.com/us/app/midi-tools/id1446209019|MIDI Tools]] includes a MIDI Monitor
-To use the MIDI Monitor:
+===== MIDI Controlled Effects Not Responding =====
-  * Display Loopy Pro's Mixer in extended view
-  * Tap the + sign to add a mixer channel
-  * Choose Add MIDI
-  * Choose the MIDI Monitor
-  * Choose Add MIDI to add your source device or Virtual MIDI (to spy on the traffic coming into Loopy Pro's virtual MIDI port)
-  * Tap on the + sign in the Destination cell for the device you want to monitor and choose the MIDI Monitor you used earlier.
-Open the MIDI Monitor's window and you can watch the MIDI traffic.
+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.
-**Streambyter Note**. If you are new to Streambyter, tap on the button with the magnifying glass icon to see its MIDI monitor.
+===== Loop Beginning Truncated or "Muted" or "Blurred" =====
-{{:lp-streambyter.png?400|}}
+Loopy Pro's default settings generally result in click-free loops. If your recordings have sharp transients at the very beginning of the loop, this can result in the transient being blurred. There are a few settings to look at. These can be changed at the global, color, or individual loop level.
-Quick tutorial showing StreamByter as a MIDI Monitor in Loopy:
+   * **Loop Boundary Crossfade** - crossfades the loop beginning and end to eliminate clicks. The default setting is 50 ms. The minimum setting is 0.
-{{youtube>cqjowyNR4eM?large}}
+   * **Fade In / Fade Out** - the default setting is Microfade. The minimum setting is Hard Zero.
+Set all three of these settings (Loop Boundary Crossfade, Fade In, and Fade Out) to 0 and Hard Zero. If the loop beginning is correct, use these settings.
+**Check to see if an action is causing a fade in**. If after setting those to 0, the beginning is truncated make sure that there are no actions involved in the recording process that might cause a slight fade. The unmute action has a very short fade in to reduce clicks. (NOTE: almost all digital mixers have very short-scale fade in otherwise muting and unmuting would be very prone to clicks).
-===== MIDI Pedal/Controller Troubleshooting =====
+**Sync issues**. If you are recording something that is MIDI-synced, there may be a slight offset. In the synchronization settings for Loopy Pro, select your device and see if changing the offset solves the problem. Try both negative and positive offsets.
-==== MIDI LEARN - How It Should Work ====
-Generally, MIDI Learn is straightforward. Here is a video showing how it 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}}
-Loopy Pro's MIDI Learn assumes that the MIDI controller sends an ON message (MIDI note on or a MIDI CC with a value of 127) when a controller pedal or key is pressed and an OFF message when the pad or key is released.
-Some controllers only send and on message and not release 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.
-The two most common problems 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".
-  * the controller misbehaving when Loopy tries to send messages to the controller (which can be solved by turning off feedback to the device in Loopy Pro's Control Settings panel)
-==== Troubleshooting ====
-If you get surprising response when controlling Loopy via MIDI, there are a few things to check.
-The first thing to check if things seem really strange is if turning Loopy's feedback to controllers solves the problem. Some of these problems seem connected to messages that Loopy sends out (possibly to update status LEDs). In the MIDI Control panel, find your MIDI controller in the list of MIDI sources at the top of the MIDI Control window and display Loopy's settings. Turn off the setting labeled **Feedback Enabled** and see if that solves things.
-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.
-**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.
-**For the Morningstar pedals**, use the pedal's global configuration menu to turn //Cross MIDI Thru// **Off** and //Ignore MIDI Clock// **On**.
-{{:morningstarpedalimiditips.jpg?600|}}
-Here's a helpful video for the Morningstar pedal from John Paul Music UK
-{{youtube>7Gfz-PqIZwg?large}}
-===== 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.
-{{tag>loopy_pro}}
+{{tag>loopy_pro troubleshooting }}