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
No, the list in Live of the Send instances in AUM.
That was expression if highest level of surprise cause just 10 minutes ago i tried again AUM+ApeMatrix combo on kick drum and it was tight as much as it can get ..
cool.. glad to hear that ! It's 22:35 here, so i can go to sleep
)
Expression of any kind of emotion is firmly against forum policy. Please refrain from use of punctuation other than period and comma. Your post has been flagged.
Oh this, yes i noticed this, I think this one is on Ableton's side, i just propagate change name to their API. I noticed that often it takes some time until send disappears and sometimes just keep stucked there.
At least until i didn't missed someting, but re-checked it multiple times and don't see any bug on my side.
But again, my Impostor syndrome is kicking in so after some nap will recheck again if i am doing all like i should do.
YESSS SIR !!
Interestingly, latency doesn't seem to increase when adding multiple channels (to Live). That's good.
Good to hear that, anyway, I somehow don't believe too much to transfering audio via network
)) It's strange as somebody who made such plugin but I would never use this tech for making real music, I just refuse to believe this technology can be really reliable LOL.
Agreed. Start transferring audio and who knows what else people might start using this demonic network thing to do. It's a slippery slope.
I'm feeling heretical today (in the name of science). Busting out the network switch, ethernet cables, and adapters for some evil experimentation.
i'm going to bed before i learn something i doesn't want to know. good night (with cables&stuff)
Ethernet works well. I had iPhone, iPad, and MacBook sending all over the place, to and from each other, with under 10ms latency. I tore it all down 'cause my lab is also the dining room table. 😬
So then I switched to WiFi ... and Live is able to manage about 25ms latency with no dropouts. That surprises me very much.
...oh, I forgot what I started out to mention @dendy - AUM is still showing a constant 150ms latency for the receiver plugin, and applying that to the latency compensation.
UI Problem: If the channel selector needs to scroll, the scrolling constantly gets reset to the top making it difficult to select anything below the scroll point. If this is due to the pulsing effect, I'd be happy if you just turned that off. It's a bit annoying tbh.
In AUM, on the same device, I am seeing only about 7 ms latency on my iPhone 16…that is in phasing, not flamming range. In Loopy Pro, I am seeing something like 24ms in the recorded audio but live it is less. So, it could be a latency compensation error on our side.
I notice that if audio pipeline is put into IDLE it doesn’t re-sync when coming out of idle.
I'm curious - what's the utility of having both a Link and Link Audio toggle? How do they interact?
I see that if I turn off Link, audio stops and peers go to zero. If I turn it on, but turn Link Audio off, the peers stay connected.
[edit] ... huh. Now I can't get my iPhone to show up on the iPad, but it does show up and connect to Live. The iPad connects to Live as well. Oh well, that's enough messing around for me for one day. I'll try to sort it out later. I suspect it has something to do with a confused network router, which I can't reboot at the moment.
[edit 2] as soon as I said the above, it started working.
Hm these two comments are indicatomg you are still runnijg old build (0.1.0 (5)) or 0.2.0 (1) not new one 0.2.0 (2)
Cause new one has some problem with popup but different one ..
when there isn’t iťs like this and scroll doesn’t work - will be fixed soon
(pushing new build 0.2.0 (3) to TestFlight with this one fixed)
!
don’t expect this to be sample accurate synced, it’s just inherentn limitstion of this technology.. It's definitely not for syncing drums ;-)
if you mean disconnecting/reconnecting plugink in AUM - will be fixed in build 0.2.0 (3) .. soon in TestFlight
good point.. first one enables/disables completely detection of peers, second just enables/disables streaming audio to peers.
I overthinked here. Think is default LinkKit SDK presents their entire stanrd Link view controller with even morebttons, but the desktop SDK i used doesn't have any UI so i needed to build this for my own... we need really just one
button here which does both. Will be updated in new build.
I said it !! Networking is witchcraft !! This plugin opens gates of hell, what i created ?!
0.2.0 (3) in testflight, thanks @wim @espiegel123 for thoroug testing !
I'm still not getting Audio Pipeline - now on 0.2.0 (3) - showing up as a Link audio peer in Ableton 12.4 on Mac, from iPhone 12 wired (lightning to usb-c) or wireless with AUM as host. LinkEffekt does show up and work. Is there a permission setting for Audio Pipeline I've missed somewhere?
I can get it to work internally on my device from AUM to Loopy Pro, but not to Ableton on Mac.
SUCCESS. I don't know if this was the actual cause, but I went into iPhone settings for Audio Pipeline and turned off 'Allow AudioPipeline to Access: Mobile Data'. Then I went back to AUM and toggled 'Enable Link' off and on again in Audio Pipeline, then I got the 'Allow audio pipeline to access local network' pop up, I allowed and now all working, can see as a Link Audio Peer in Ableton. Major morning troubleshooting result and I haven't even had a coffee yet
Also, to clarify, this definitely works iPhone to Mac over lightning to USB-C cable, all my wi-fi is off, no ethernet connections at this moment.
These apps are starting to become popular!
https://apps.apple.com/gb/app/link-audio-bridge/id6759808732
everybody just sending, looks like i’m the only one with courage to use desktop C++ SDK on iOS for receiving 😆😆
also workingn on one surprise in receiver
big surprise 
lot of apps - good chance at least one nails it in terms of stability and reliability, competition is good thing, I wish to all competitors to be better than me
Some send/receive glory.... In to the future and back to the past. I've just tried sending audio from Ableton into Samplr and back again - needs to go via AUM and Audiobus 3 - it works, can't quite believe it
Only snag is app switching doesn't work (already known) in Audiobus 3, so you have to swipe around apps manually, but that's a minor inconvenience - once set up you can stay on the Samplr screen. Note, using Audiobus has always been necessary to get audio in and out of Samplr (other than standalone), you can't do it with AUM alone.
Here's some really poor pics to show setup in AUM and Audiobus:
super glad to see my baby handles even such complex setup ✌️👍👍
You ain't seen nothing yet
Thank you, I've just been told to get rid of an old wooden pallet, I'm using this as clear evidence that it's worth holding on to old things without an immediate use, as you never know what might become possible. 👍
Great work. The latency is much improved from Note to Loopy down to 15 ms for me from 24 ms in the previous build with a buffer of 64. Fwiw, the Loopback plugin manages to get latency down to under 5 ms sending from AUM to Loopy Pro. I don't know how much overhead link adds but it might be worth looking at.
Sometimes when I choose Note's MAIN in the audio pipeline instrument, sometimes I get silence. No idea if this is a Note or Audio Pipeline issue.
I am trying to solve one bug where i am getting crash directly in Link library (related to other bug - stucked Sender instances) and honestly I am starting to be skeptical to this desktop SDK.
All other “competitors” are using iOS SDK “LinkKit” (thaťs why they are sender only) but i am starting to think choosing this desktop SDK just to make also Receiver was just bad choice. It just doesn’t work that good as LinkKit on iOS.
Maybe this my entire experiment stops and I’ll just wait until they actually update LinkKit with Receiver code so i can switch SDK core.
To release only sender makes not much sense to me considering that there are already two other sender apps in appstore.
I give it one or two days more and if i fail to fix these 2 bugs (which may be really in Link lib not in my code) then i will return back to my main big project.
Will keep beta active anyway, in case anybody finds this usefull.
@dendy : fwiw, even with those issues, this seems like a worthwhile plugin to me as receiving is a valuable contribution. That’s my opinion anyway.
just nailed those annoying bugs;)
finally i can go back to “surprise” in receiver i mentioned .. maybe something nobody needs but i want it, and i am still doing this for myself for the fun in first place🤣
Feedback knob? Yes please 😁