Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
loopy_pro_troubleshooting [2022/01/09 07:13] – add morningstar pedal stuff 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:// | 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:// | ||
+ | Related Troubleshooting articles: | ||
+ | * [[loopy_pro: | ||
+ | * [[loopy_pro: | ||
+ | * [[loopy_pro: | ||
+ | * [[loopy_pro: | ||
+ | |||
+ | ===== No Audio Input or Output ===== | ||
+ | See [[loopy_pro: | ||
===== Audio Levels Of Recorded Tracks Seems Too Loud ===== | ===== Audio Levels Of Recorded Tracks Seems Too Loud ===== | ||
Line 10: | Line 18: | ||
To turn off Echo Cancellation, | To turn off Echo Cancellation, | ||
- | ===== Using a MIDI Monitor to Examine | + | ===== MIDI Pedal/ |
- | + | ||
- | 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. [[https:// | + | |
- | + | ||
- | To use the MIDI Monitor: | + | |
- | * 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' | + | see: [[loopy_pro: |
- | **Streambyter Note**. If you are new to Streambyter, | + | ===== MIDI Controlled Effects Not Responding ===== |
- | ===== Morningstar (and other) | + | 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. |
- | Some people are finding that they have troubles with MIDI Learn and MIDI Control using their footswitches. Some of these problems seem connected to messages that Loopy sends out (possibly to update status LEDs). If you find that your pedal is behaving strangely, you may want to see if your pedal has a setting to ignore incoming MIDI. | + | ===== Loop Beginning Truncated or " |
- | NOTE: These issues seem likely to be resolved in a Loopy Pro update -- but these steps will be useful | + | 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 |
- | For the Morningstar pedals, use the pedal' | + | * **Loop Boundary Crossfade** - crossfades the loop beginning |
- | {{: | + | * **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). | ||
+ | **Sync issues**. If you are recording something that is MIDI-synced, | ||
- | {{tag> | + | {{tag> |