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
This worked fine on my iPad Air 2 on 9.2.1
iPad Air 2 != mini 2 though @johnfromberkeley
about iOS 9.3: I am totally surprised by how much I like the "night shift." it seems like a compete gimmick on paper. But it is actually way better.
Ah, ah, sorry. Wow. Still good news
Anyone know if this resolves internal mic latency issue on Air2
Having problems activating my iPad
seems that the activation servers are unavailable
iPhone 6s is recording great on iOS 9.3. Loopy HD in Audiobus with ToneStack. No latency issues on Focusrite 2i2.
Nice warm display, easy on the eyes.
Derek thanks for doing this testing work for the community. I have been one of those hold outs hesitant to update to iOS 9 (my Air 2 is on 8.4 now).
As a newer Apple user, coming from 5 years experience with Android devices and it's wonky updates, I have been curious to step up but all of the latency issue reports, AudioBus breakdowns, etc. have kept me from it.
I've said here before that I sometimes feel a device operates best with the OS generation it was introduced (and optimized) under (Air with iOS 7, Air 2 with iOS 8, the new Pro 9.7 with iOS 9, etc.). But when cats with iPad 2's & 3's are on the current OS talking of improved performance it makes me question that logic.
I'll give it a few more days, a week...hell, I've waited this long; but from the short time you've spent with 9.3, do you feel in your gut they finally got it right for us iOS music producers and it's time for guys like me to make the jump? Or do you think if my workflow and app performance are fine with 8.4 should I not fix what's not broken?
Appreciate your opinion and feedback brother....be cool.
Anyone else notice that iOS 9.3 now leaves less free Ram when no apps are running. I am using iDoctor Device and now can reclaim about 10% less free ram than I could on iOS 9.21 yesterday (iPad Air) I was led to believe this update would have a fix to be less resource hungry, Lots of bugs fixed in 8.3 but overall very disappointed.
In good news, the master clock priority bug has been fixed in iOS 9.3 and El Capitan 10.11.4. This means that iConnectAudio4+ now functions perfectly when both a Mac and iPad are connected. I tested it out in Ableton Live, and there was no crackle or drop-out when recording the audio stream from the iPad to the Mac, which was not previously the case with iOS 9.2 and El Capitan 10.11.3.
Usually Apple tends to enable some services you already had disabled prior to update, so check it out.
seriously,i've read so many times that this apps are totally bullshit.There is no reliable way (if you are not apple) to measure free Ram on ios and that's the reason why rim has thrown out the ram meter in auria.All this"doctor"apps can do is making panic.Similar to many real doctor
I would ignore this stuff and just work with the device until you face real problems...
I also noticed a higher ram usage and a constant cpu of 9-20%? This is at idle...
Shouldn't it idle @1%?
Is there a way to deactivate more services etc. More in depth? Or is it a completely closed system?
I downloaded a few cpu monitoring apps just to "see" and noticed that I have over 1.3 GB of RAM active!?
Why ?
I rebooted, everything is closed...
There seems to be something weird in all this...Air 1 has 1gb memory and leaves 300 mb free.
Air2 has 2gb memory and leaves 700mb free? Same iOS but double waste of Ram...
Are they activating more shit in background to waste the extra resources?
On PC I got same availability of RAM regardless how many GBs I installed.
Any ideas?
i give up
Totally agree @Crabman
Stopped using these doctor type devices an age ago. Sensible restarts before major session changes and my iPad barely has problems not of my own making
I was down to 200 mb free space, cleared some old projects to get enough space for the update, I actually cleared to 850Mb free.
After the update I now have 1GB free
Don't know why, don't know how. Don't care !
Hi all. So, my tests on a mini 1 are not so encouraging. If you have a mini 1 (and I suspect this will hold for an iPad 2 as well) that is on 7.1.2 and have older ipas (including older Audiobus), then it seems like that is still the better option. It may have something to do with the mini 1 / iPad 2 being 32 bit devices.
In any case. Setting up an AB chain - Addictive -> Crystalline -> AUFX:Dub -> Audioshare - I was getting crackling with 9.3 but in 7.1.2 I could not only do that but also add AUFX:Space without crackling (all tested at 512 frames).
So, although things seem better with 64-bit iPads like the mini 2 I tested, if you are on an older 32 bit iPad that's stable with 7.1.2 and older ipas it still might be better to hold off on 9.3
Thanks for the advice
Update to above: On an iPad 3, I can do Addictive -> Crystalline -> AUFX:Dub ->AUFX:Space-> Audioshare without an issue. So, the extra memory there seems to be making a difference in spite of the heavier Retina graphics loading.
Still on iPad 2 so I'll stick with 7.2. Anyway it hasn't things like btLE at HW level so a OS upgrade won't be a game changer. Which would mean also to upgrade my late 2009 iMac at the price of losing my FastTrackPro driver support. Life sucks.
First iConnectivity test with iConnectMIDI4+
Mac on port 3 - audio clock master for iConnectMIDI4+
9.3 iPad mini 2 on port 1
9.3 iPad 3 on port 2
Tested with
A.)
1.) iMini on mini 2
2.) AB chain on 3
B.)
Same AB chain on 3, Audiobus as an outboard FX running AUFX:Space on the mini 2. I.e. sending audio from the iPad 3 into the Mac out through AB on the mini 2 and back to the Mac. (I use Pipeline Stereo in Studio One Pro 3 to do this, but you could be using some other DAW equivalently.)
No crackling in either case. Appears to be resolved.
I'll try later with the iCA4+ as I have time.
After jamming with a pretty complex setup for a while, iOS 9.3, AUM, AB, Modstep, iSpark, Loopy, iMini, Tera Synth, Ableton Link... something bad happens after a while.... A glitch of death. All of a sudden the tempo sounds like it drops almost in half and the audio sounds like it's being shredded apart. No way to stop it but to kill all the apps and restart the whole session. iPad Pro (do I have to start saying "the big one?")
I'm going to try removing things from the equation to see if I can find the offender but I'm afraid it's iOS 9.3. I removed my Akai MPD226 USB midi controller and haven't gotten the death-glitch yet.
OK. More good news on the iConnectivity front with the iCA4+. Just set up the following:
9.3 mini 2 (atop the iCA4+) running Auria Pro.
9.3 mini 1 in front running Animoog.
Live audio routed from
Mic on 1
Guitar on 2
Stereo synth on 3&4
Animoog also routed from mini 1 to mini 2
Audio clock set to internal
No glitches :-)
Apologies for the less than stellar pic cap - I was using my older 4S.
Apparently, some models (iPad 2 among them) can't be activated after updating to 9.3. Apple's support forums are flooded with such reports. I wonder what happened to their quality control in the last 5 years. It's like one f@ck up after another
Restoring to 9.2.1 in the DFU mode now...
Thanks @MusicInclusive. I have a mini 2 and a 4s and am holding off for now. Almost ready to go ahead with the mini2. Probably will leave the 4s alone.
Edit: so far no problems. seems a little snappier overall (?)
And...love the night shift coloring(have been waiting for this). Wish I could have it on my iphone 4s
Updated my Air 1 and was running Modstep with Poseidon, Patterning, TF7 and iSem without crackles this morning!
What isn't supposed to work with older devices? My iPad Air 2 is obviously fine, but I also updated an iPhone 5 that appears to be fine. What should I test to see if the iPhone 5 running 9.3 fails?
UPDATE: Just as a test on the updated to 9.3 iPhone 5... ran AB, one chain had a launchpad comp & blocs wave 8 pad loop going with apeFilter in fx slot and output into MiMix. Second chain with a figure loop and gestrument going while both mangled by Deregulator in the fx slot, output to MiMix. 3rd chain MiMix into AudioShare.
All worked fine. Couple of crackles but I also had Bluetooth, wifi, cell signal & 7 other apps open including mididesigner, Safari, mail, iMessage, Podcasts, Flickr, and Binaural.
Before 9.3, that would've crashed my iPhone 5 for sure.
No problems in sound or performance with 9.3 on my iPad-Mini2, running through a Behringer iStudio interface. Everything checked out as it has on previous iOS releases (yay). Had Patterning in AudioBus out to AUM. AUM handled the hardware: midi keyboard in, keyboard sounds in, and microphone in, along with Viking synth (AUX), iM1 (IAA). Also had AuFx:Space(IAA) on one bus and Voice Rack effects (AUX) on the microphone bus.
So they finally got it right?
I'm now seriously considering updating from 8.2 (iPad-Mini2). If the latency/audio interface issues are fixed I'm in.
...How about iFunbox for this update?