Loopy Pro: Create music, your way.
What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.
Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.
Download on the App StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Routing with Audiobus, loopy, physical interface (presonus)
I am having issues with signal routing when using loopy iniside of Audiobus.
What I am doing is signal comes into my presonus interface. It’s a two in two out. Then I have the USB from the interface going to a USB hub. The hub then connects to a iOS camera kit. Then I run loopy iniside of audio bus. I pick the first channel on the interface as the input in Audiobus output to audio bus.
Then I use the channel one out output from the interface to the DAW in my computer.
The problem is if I try to start using Chanel two for another instrument it bleeds onto the outputs of the opposite channel.
So in a bit shell I am trying to control the routing specifically through loopy (so I can loopy multiple external instruments) but then feed their output back through and out my interface out puts into separate tracks on the daw. I have everything worked out besides the bleed between outputs.
Any idea on how separate the audio?
Comments
Confused a bit.
Where does Loopy enter into your described setup?
Sorry maybe this will help:
Bass -> channel one of presonus interface -> usb out of presonus -> usb hub -> out of usb hub into iPad camera kit -> Audiobus with Chanel one from the interface is selextect as input on the Audio screen and loopy is the out put -> then from the line out for Chanel one on preaonus interface I got to my daw. So the signal I get at the daw is essentially just like an input from any guitar.
The issue is if I try to feed the second channel on the presonus, routing through AB and loopy. Even if I pick separate inputs for each channel or path in Audiobus when the signal is returned to the interface Chanel one and two are mixed. It’s as if the paths are respected all the way until it gets back to the interface. And when the signals come out of the interface channel one has a mix of its audio and then channel two is the same (channel one is mixed in).
Also having issues where at times with the same setup listed above we can record a guitar or bass into loopy and playback works perfect. Other times we can’t get a signal into loopy. We can hear the bass and play old sessions fine.
Seems as if boot order might be a factor. Or the interface is bad or I need to use AUM in conjunction with AB and make even more specific routing???
Are you making sure to send the signal back hard panned? It is possible that the mono inputs get turned into stereo and if you return the signal like that you will seem to have bleeding between the channels.
I think you need to show us the complete signal path by showing us how you have Audiobus configured.
Loopy is mixing your separate L/R inputs to 2 channel mono, so you lose the stereo separation.
You have to record your L and R to 2 separate loops in Loopy, and pan them hard L and R in Loopy.
Sorry but your description is still a little confusing, and what you’re trying to accomplish, a screenshot of your audiobus setup as @espiegel123 said would surely help.
Are you trying to send the the output from Loopy on separate channels? Or just pass the live audio through to your DAW (which sounds like you’re saying is something external?) maintaining separate chanels?
You can only control which outs Loopy sends to either as a whole mix by choosing Loopy Main Out, or by routing each individual Loopy track where you want it to go. In the second case this way if you chose to only use certain Loopy tracks for certain instruments (for example: tracks 1-6 for guitar, 7-12 for bass) you could keep them separated in that way.
If you’re just talking about keeping your monitored live input/instruments separate then you just need to send the input to Loopy (with monitoring off in Loopy), and then ALSO to whatever Chanel you want them to go out of your interface on.
Hopefully that makes sense...
Your comments make perfect sense and I did try to specify the out puta at the AB level and hard pan there but it didn’t work. I will try within loopy to see if that fixes the issue.
There is one last oddity with this setup. From time to time the iPad will stop getting a signal from the instruments plugged into the interface. However a signal can be seen flowing through the interface and reaching my DAW. I know that some times the order in which things are plugged in makes a difference, and as well does adequate power to the iPad. In my case the ipad is getting power by a usb powered hub as well as all the interface. So there is no competition for power.
As far as the details of my setup and goals. The purpose of this configuration is to make up for looping short comings by a lot of physical pedals. We use a helix and the loop length is very short. Further there are other devices and apps in the mix that need to stay in time. Link is superior to midi for this as there are other iPads (nothing physically connected to this routing issue) that use like and midi link sync to keep time on all devices.
The setup devices having issues is exactly this:
Guitar (or any instrument), -> plugs into port one on input of the interface. Then the interface takes the signal to an iPad via the USB output of the interface. The USB out of the interface is plugged into a powered USB hub. The hub is plugged into the iPad using a CK from Apple. Then on the iPad we use Audiobus with channel 1 or input one from the interface. From there the output of this path or Chanel/chain within AB has its output set to loopy. Then we take the output of loopy and assign it to a specific out put on the interface. Let’s just say for the above example it’s output 1. From there the signal goes to a different interface and this interface is the one actually connected to a laptop and does the recording. The second issue besides the blending of tracks (unwanted) is that randomly part of the way through a performance loopy stops getting a signal from the instrument plugged into the interface with the config listed above. We can play back previously recorded loops and we get an uneffected by the ipad signal start the Dae From the instrument through the interface to the DAW.
What can cause AB or loopy you stop getting a signal when it works at least 50% in this config and the interface works perfectly with other config or a computer etx
@Keef_gifford : maybe it wasn't clear, if you post screenshots of how you have everything configured, it will help.
Have you already tested by having a simple setup with two Audiobus lanes without Loopy. Send one lane to one output and the other lane to the other output?
I have not tried that, but I will. I will work on the screen shots and get them up here.
Do your hard panning in Loopy. Loopy records mono loops, so panning in Audiobus will not affect how Loopy records. It just records a mono loop, and outputs the loop back to a stereo mix so you can place/pan the mono loop in the stereo field upon output.
You cannot use L/R tracks to record a stereo loop in Loopy. It will mix the L/R to mono when recording the loop. You need to record L to one loop, and pan the loop to the L Loopy output in Loopy, and do the same for R, but using a second loop slot in Loopy, and panning the recorded loop to the R Loopy output.
For the ‘signal to Loopy cutting out’ issue, not exactly sure.
One thing I suggest is in Audiobus Settings, turn off Multiroute audio feature. You don’t need it in this case, and it can cause more confusion if it is on.
Another thing is make sure you have Input monitoring on in the Loopy settings. It may be that you only hear the Input after it is recorded as a loop, but are not hearing the Input pass through Loopy. Turning on Input monitoring should allow you to hear the Input signal all the time.