Frequently Asked Questions/Troubleshooting
Q: I'm having issues using Echo Pad with Inter-App Audio,
what should I do?
A: Please have a look at this video tutorial for using Echo Pad
as an IAA effect, and read the IAA tips section below.
If you are still having problems please fill out a support ticket with
as much detail as possible HERE.
Inter-App Audio Tips
Using Auxiliary Sends
- Inter-app audio apps can only load one instance at a time, so if your host has auxiliary sends you might want to use Echo Pad in an auxiliary channel.
This allows you to apply Echo Pad's effects in parallel, effecting multiple tracks in your mixer by adjusting each track's corresponding Aux send level. This also happens to be a classic mixing technique for delay and reverb effects.
- To conserve CPU power as well as being able to apply different effects to individual tracks, consider freezing tracks to bounce down the audio in place where available. Auria is one example DAW application that allows you to freeze tracks with the effects applied.
Use larger buffer sizes when recording while monitoring effects on less powerful iOS devices
- When using an app such as Auria to record while monitoring through Echo Pad and other IAA effect apps, you should try using a recording buffer size of 512 frames or higher on older devices such as the iPad 2.
This will minimize chances of audio glitching/stuttering and other problems on older, less powerful devices.
Avoiding "stuck" IAA apps and crashes
- To avoid Echo Pad and other Inter-App Audio apps becoming "stuck" and hidden in the background, please remove them from tracks and close the app completely when you are done using them. This prevents the app from being connected but hidden in the background, which can cause problems and crashes when you try to load the app in another IAA host, channel, or project.
What to do if Echo Pad or another IAA app becomes "stuck" in the background
- If Echo Pad or any other IAA app becomes stuck and hidden in the background, leaving it unable to connect to a new IAA host or channel, don't panic! Simply take the following steps to fix the issue.
1.) Launch the app directly from it's home screen/folder in iOS by tapping it's icon.
2.) Once the app has come to the foreground, close it, then remove it from the multi-task bar by double tapping the home button, then swiping the app upwards to remove it completely.
3.) You should now be able to load the IAA app in your host.
Q: Whenever I close Echo Pad, I see a red bar at the top of the screen that says "Echo Pad Recording". Why? How do I get rid of it?
A: Echo Pad supports background audio, which allows you to continue processing audio in Echo Pad while using another audio app, like a synthesizer or DAW.
If you close Echo Pad when background mode is ON, you will see a red bar at the top of the screen that says "Echo Pad Recording". This is a bit confusing, as it does not actually mean that Echo Pad is recording, this is simply a default setting that all iOS apps display if they are processing audio in the background.
To close Echo Pad completely when background audio is enabled, you must do the following steps.
1.) Double tap the home button to bring up the iOS taskbar.
2.) Tap and hold down Echo Pad's icon in the taskbar until it begins to shake/wiggle.
3.) Press the (-) minus button to close Echo Pad and remove it from the taskbar.
! - NOTE that when Echo Pad is connected to Audiobus, it will automatically override this setting and enable background audio. This is normal behavior, as all Audiobus apps must allow background audio when connected
Q: Echo Pad does not work with Audiobus! How do I get it work?
A: Please close Echo Pad, Audiobus and any other music/audio apps that are currently open,
then follow the steps below.
!!! Step 1 is the most important, and usually resolves most problems you may have with Echo Pad and/or any other Audiobus compatible apps.
1.) Launch Audiobus FIRST. This is important!
Seriously, just launch Audiobus first. DO IT!! :-)
2.) Once Audiobus is open, connect Echo Pad and other apps inside the Audiobus connection panel.
(You did open Audiobus FIRST, right? Right!.)
3.) Make sure you have an OUTPUT app connected. Even if you are not recording into an app like Auria, Cubase, Multi-track DAW, etc. you still need to connect the "Speaker Output" app.
If you have followed these 3 steps in the correct order, there's a very, VERY good chance you are now having fun with Audiobus and Echo Pad.
If you are still experiencing problems, please contact support.
You may also find more info in the "Using Echo Pad with Audiobus" section of the manual.
Q: I'm getting some snap, crackle and pops in audio, how can I fix this?
A: Older generation devices will struggle when using several effects at once in Echo Pad.
iPhone 4s, iPad 2, iPad Mini and higher recommended
- If you are using Echo Pad within Audiobus, and experience excessive glitches in audio, please set the buffer size to 512 samples in the Audiobus app.
- If you are not using Echo Pad within Audiobus and you are experiencing audio glitches, try using a larger buffer size such as 512 or 1024 samples. Tap the Latency button in the options menu to select a buffer size.
Q: I'm only hearing my input sound out of one channel, what do I do?
A: There are 2 possibilities that can cause the sound to only come out of only 1 channel in Echo Pad.
1.) The audio has been panned all the way to the left or right using the Stereo Panning control ring (white). Try adjusting this control ring to the center of the screen, this will output to both left and right channels equally.
2.) You are using a 2 channel audio interface with a single microphone/guitar/etc. connected to either channel 1 or channel 2, and need to select the appropriate Audio Input option in the Utility menu.
For example, if you are using the new Apogee ONE's built in microphone, Echo Pad will see it as INPUT 1. This means if you are using the default setting of Input 1+2 (stereo), you will only hear the sound from the microphone coming in on the left channel. In this case you should select INPUT 1 (mono) so that the sound from the microphone is processed in both left and right channels in Echo Pad.
1.) Audio Input (input 1+2 stereo) - This is the default setting for Echo Pad's audio input, which uses both left and right channel inputs of audio interfaces with 2 inputs. When connected in the effect or output slot in Audiobus, Echo Pad will receive both left and right channels from apps connected in the Input slot in Audiobus.
2.) Audio Input (Input 1 mono) - Selecting this option uses Channel 1 (left) of audio interfaces with 2 inputs. When connected in the effect or output slot in Audiobus, Echo Pad will receive only the left channel from apps connected in the Input Slot.
3.) Audio Input (Input 2 mono) - Selecting this option uses Channel 2 (right) of audio interfaces with 2 inputs. When connected in the effect or output slot in Audiobus, Echo Pad will receive only the left channel from apps connected in the Input Slot.
Q: Can I set the global BPM using MIDI clock sync?
A: As of version 1.8, you can now sync Echo Pad's delays to external MIDI clock.
Tap the "MIDI Input" button to enable MIDI, then make sure "BPM Sync" is also enabled. Then, in the app that you wish to receive MIDI clock from, select "Echo Pad" from the app's list of available destinations.
Q: How can I avoid loud microphone feedback when using Echo Pad?
A: Please use headphones!!! Echo Pad is not designed to be used with the iOS device built in speakers. Using the built in speakers on iPads or iPhones can lead to feedback, as any live microphone and speaker can produce. If you absolutely, positively MUST use the built in speaker, please make sure to reduce your device's volume to below 70% to minimize the potential for feedback.