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.
Comments
Only if your Mac is an Apple Silicon one though. This plugin won't run on Intel Macs. There is however a different plugin available for non Apple Silicon Macs that should work.
I’m a bit lazy and I haven’t read the whole entire thread, but I just wanted to share that I just attempted to use this wonderful plugin in Cubasis.
I wanted to see if I could use it to create an extra send bus for fx (ie turn an audio track into an fx send)…I haven’t checked latency, but it works great and I can send multiple tracks to the one receive channel 🙂
Then I wondered what would happen if I armed the channel with the receiver on it to record.
and hit record in Cubasis.
I successfully recorded the audio I sent!
This could be one of the biggest brightest changes I have encountered since the days of Audiobus.
I hope people understand what this means for audio routing in the iPadOS, iOS world.
Thank you so, so much for creating this. This is pure brilliance.
To add a little more information to my results.
I wouldn’t use this as a live fx send unless I was looking to add a little pre delay to a reverb.
What I have witnessed in a few short recording runs is that the latency is more consistent at the shorter buffer times. I found that if you push the latency out to the 42 ms setting in Cubasis the timing starts to get a little inconsistent. At shorter buffer times it’s pretty sharp.
Here are the timings that I did with two drum channels sent into one receiver channel.
Each recording was around 10 seconds in length.
I checked the timing at the start and then of the recorded section. If I noticed anything weird I checked a few more sample points.
Cubasis latency 1.3 ms (the shortest time you can set)
.026 ms
Cubasis latency 5.3 ms
.057 ms
Cubasis latency 10.7 ms
.058 ms and .052 ms
Cubasis latency 42.7 ms ( over two recorded runs)
Ranges from around .146 ms to .177 ms with an odd one at 0.349ms
So I think I could get away with this to create an FX channel where I record the combined parts on the receiver channel and then adjust the part. It’s quicker than bouncing down a mix of parts as I can adjust them live and if I’m doing a reverb thing might be able to just tweak the pre delay a little to suit.
My assumption is that this is sending the audio out and back in. I realised I can use this as a quick way to see what propagation delay is being applied when I add a number of plugins to a channel.
Super cool. Thanks heaps once more….🙂
@Mountain_Hamlet
Then I wondered what would happen if I armed the channel with the receiver on it to record.
and hit record in Cubasis.
If you are using all sender and both recivers just within SAME host, then host does perfect plugin delay compensation (sender doesn't produce latency, just receier, and that one reports the latency to host, so every proper host does PDC (which means it "adds" latency to all plguins based on plugin with highest latency in project - so all plugins, all audio, everything is perfectly in sync ...
Actually - this one (to add more complex routing capabilitirs to host on iOS) was for me use case number one for this plugin
Imagine you can use it to do complex grouping / routing even in GarageBand 
I’m not sure if many of the hosts on the iOS platform actually do PDC - particularly Cubasis. I know that I have issues if I start putting limiters on individual tracks. I know that Auria Pro might, AEMS has it as a Beta option and Logic does, but that is the limit of my known hosts. Maybe now I’ll have a look again at Garageband. I’ll do some more tests.
Are you saying the audio remains inside the host when sending it between channels?
AUM does PDC.
I didn’t know AUM did. That’s very good to know.
>
Ah ok, I thought this is absolutely essetial basics of any host on iOS. If it is not then another of many sad showcases that iOS is still unmature playground when compared to desktop world.
AUM does for sure, Loopy Pro too.. Nanostudio2 also has excellent PDC ..
Well, this is a tricky question and complicated answer. But a bit simplified answer - yes, for all practical purposes you can imagine audio is staying inside host
To have it all in sync within same host is ALL competence just of host to do proper PDC.
I don’t believe Loopy Pro has PDC. AUM sound pretty tight though.
what ? Are you sure ? That would be massive surprise for me ..
@Michael any comment to this ?
PDC is surely sitting at the top of the Cubasis missing technical features list. (Eh, @LFS )
(Total aside Lars, but as I tagged you, do you happen to know if the playhead return to start, or is it marker, works with Link if stop is hit in another app?)
My jury is still not fully convinced about AUM either, but if others who appear to have knowledge in this area say it does then I will reserve any judgements for now.
AUM does PDC and also provides detailed information .. of course host can compensate latency only in case that plugin itself reports to host correct latency (there is mechanism for that in AUv3 API). My Receiver reports that (Sender doesn’t introduce any latency to host cause it just passes audio from input bus to output bus)
AUM is definitely BEST AUv3 host on iOS - massive benchmark of coding quality, insane respect to dev !
Here you can see PDC based on list of plugins which actually report some latency in your project:
The App Store version uses latency information when recording But not in real-time output (pdc makes everything later which can be a bit of a disaster for realtime performance .
In a coming update, Loopy Pro implements pdc in a way that won’t increase perceived realtime latency.
not sure that is possible until Michael doesn’t have time machine to send audio stream back in time 🤣🤣
It is done by sending recorded audio early to compensate for delays downstream I believe.
As an aside, this app solves an issue in Auria Pro where there is a limitation on aux channels. Also signal can now be sent back out from a sub group to another audio channel which is handy for setting up parallel processing and extra fx channels.
It works really well.Now here is hoping that Auria Pro keeps working OK 🤞as I still find it a very handy place to mix in.
Audiopipeline is a great software. However, I was not able to send audio from iPad or iPhone to Ableton Live on the computer. From Ableton I was able to send audio to the iPhone, but not to the iPad.
It should work. It works for me. This must be some networking problem, maybe some wifi router setting which blocks streaming. Try connect iPad to you computer with USB-C cable .. Also when you install app firt tome and open standalone app (tap on icon on home screen) IOS asks you of you want to allow app access local area nerwork - try delete app and install it again and then first run standalone app and and choose allow acces to local area network
try delete app and install it again and then first run standalone app and and choose allow acces to local area network
Yes, that did the trick. Thank you very much for your assistance, and for the app. Great work.
I wonder if it might be possible to add a settings page so network access could be toggled at any time? Given that needing to set this is likely to be a persistent ongoing issue…
It should be in
iOS Settings > Privacy & Security > Local Networkalready, along with all other app's permission settings. Apps get a one-time chance to ask for it on first launch, but it's the OS that handles the actual setting of the permission, not the app itself. It probably wasn't necessary to do a delete and re-install to enable that.I could be wrong, but I don't think it's possible in the app to have such a setting. It's a protection for you. If an app could have such a toggle, it could also have an invisible toggle, and that would be a huge security hole.
A warning could be thrown up though, probably.
Good news! I didn’t remember the correct place to look for this.