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.
Gadget going haywire in Auria via IAA and other Gadget issues
Noticing a few Gadget related problems:
Having issues with Gadget as an IAA instrument in Auria. I just tried and it went haywire - the sequencer window froze and it was impossible to add notes to the sequencer. I could play the keyboard and use the synth controls though.
Also noticing that Gadget isn't saving my tracks properly. I was a bit suspicious of this yesterday so before saving my last track I made an audio copy first. Lo and behold the drum sounds are completely different, so it seems to have changed the preset and lost the individual drum sound edits I'd made. This is despite manually saving the song after every single change I make, because of the previous night's issue which was:
Also crashed on me last night, losing half an hour's work.
I was hoping to use this more, but it's behaving like a bad dog at the moment. Wondering if anyone else is having as bad a time as I am with the thing.
Comments
Make sure you have enough disk space, clean reboot, and do some more testing.
Plenty of disk space - over 40gb left. Tried again and sequencer window still freezed when played in Auria. I'll try again after a reboot.
Just done a test with Auria running Gadget as an IAA and had no problems, although I've never tried this before so can't say my tests have been extensive. The Auria clock seemed to easily control Gadget and I could add notes to the sequencers, had about 8 Gadgets instruments open.
which drum machine gadget are u using?
London. I'm having continual issues with Gadget, Auria and Audiobus so I'm starting to wonder about this iPad again. At the moment Auria is stuck trying to exporting an AAF file to Dropbox, and in fact just reported an error connecting - though all my other apps don't have a problem with Dropbox and I gave Auria access. Gadget won't stay open at all, just closes as soon as I open it.
Trying yet another reboot but getting seriously f***** off with this ipad
I always had problems with gadget as IAA or in AB,no matter which device or iOS.I gave up on it a while ago and use it just standalone and export the stems.I'll give it another try tomorrow as IAA (first time under 8.3) and report back.
Thanks, rebooted but no improvement (see screen photo). Problem is, with the crashing and not saving properly I don't trust it for composing either.
Tried this out earlier then went on a tangent, everything seemed to work but was just playing a song through auria, my gadget does crash from time to time, not as much as animoog though.
Does the sequencer still wirk as normal? I can play the synths live fine, and hear the sequence ok but the sequencer view itself freezes. I'll get a decent screen grab up once i'm sober
This post had me concerned so I just used Gadget as IAA in Cubasis. It worked fine; no problems encountered...was able to add notes to the sequencer as it played, including the London gadget. All other controls seem to operate as normal.
iPad-mini Retina iOS 8.3
Thanks for testing. I just checked the app settings and Gadget didn't have background audio selected. I enabled this and tested it again - still got the sequencer window to freeze, but this time only when I went from this view, to Auria, and then back to the sequencer window again. And managed to get it working again by going to the Gadget mixer and then back into the Gadget synth. Still does it but not as bad, and I can unfreeze it by a bit of Gadget hopping.
Personally Gadget crashes as soon as I ever run it with Auria.
Always has (ios7) and still does (ios8).
Not sure why. I don't use Auria much though. But plan to.
I have this problem, but not so much if Gadget is opened first.
I think that's true with some of my AB issues too - seem to work better being launched separately then loaded into AB or Auria.
+1 here. And go ahead and extend that right out over pretty much every app I use in IAA. Not 100% consistent, but nearly every app I've ever tried to open directly from IAA has eventually shown me some problems. Crashes, freezes, etc. I got into the habit of opening them first and realized this made them more stable, so I just do it out of habit now. No clue if it's still needed or not, but why not...works for me.
Just tried it again, sequencer in auria worked, I recorded something, loaded gadget first, thought hold on he might mean the sequencer in gadget, so loaded it back up again gadget first and got a blast of noise. Restarted my device, same thing, harsh digital noise, open and closed gadget, then I started auria first and loaded gadget from the iaa menu, everything was cool, could change notes in the sequencer in gadget and record into auria via the sequencer view.
One odd thing that has happened to me with iaa, used ilectric as an iaa instrument, can't remember the host, it crashed and for days kept popping up in my midi menus for midimux and animoog, even after a restart.
Yeah it's the Gadget sequencer view that freezes when switching back to Auria, still plays though. Seems better since turning on background audio and opening it first, and can be cleared by switching apps in Gadget.
It's a pain though - there are no Auria IAA recording controls in Gadget so I have to switch to Auria to start recording, then switch back to Gadget to play. And that's when the display freezes. Sometimes.
Thanks for all the testing and confirmations though - I'm slowly ticking off my issues being specific to my device and they all seem to be general (though not consistent) issues so far, so no need to hassle Apple for a refund