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.
I asked Korg about AUv3, the Korg app team respond...
So I made a detailed case for AUv3 to Korg for their standalone synths (instead of IAA) and this was their reply:
Hi Nicholas,
thanks for your great comment!
I've shared your comment with dev team.
Decision around AUv3 is really complex and difficult to explain.
The most apparent obstacle for it is UX -- optimizing everything for AUv3 is quite a tough work.
Anyway, your comment on AUv3 is most valuable we've ever seen. We will examine more on the topic.
Excuse me but please remind that this comment does not intend to promise AUv3 support at this moment.
Best regards,
KORG app team
So promising at least, but not a definite commitment 
And shows they do listen but don't often engage with public posts. But it's also good to show them some appreciation for their work and they are more likely to respond. (Like most people).
Fingers crossed.
Comments
I bet the decision is complex because they dont want it, but people do.
Never say never I guess eh? I mean Reason finally ended up supporting VSTS soooo
Well I don’t think Gadget UX is that complex...they should have a look at Lorentz or Poison that are much more complex than any gadgets and are beautifully rendered in AU<3
interesting. But not definite enough for me to drown more money into Korg.
Maybe more should direct contact and reach out to Korg that way!?
Also, you could have simply said: 'reason finally ended up supporting VSTS...'
@Cambot Wohoo, You got a reply congrats!
Maybe next step is to ask for a rudimentary Files.app support to finally cut the cord with the need to use a computer to manage files for good?
Suggestion for folder structure (to keep it simple) could be
/Projects/ (Ie. Gadget Session Folders)
/Wav/ (For user samples and exported *.wav files)
/Exports/ (Live sessions etc.).
/REX/ (Rex-Files)
/Misc/ (Misc stuff, Midi-Files etc.)
And simple renaming of files unless using the Files.app?
WAV & REX folders could support nested folders with management handled with the Files.app.
Refresh/Re-Scan inside Gadget could be done with a swipe down gesture or something similar.
Currently everything is just stored at the 'root' level which might shock some users and could be the potential reason why Files.app support is not enabled yet?
Also a bit curious as to why AudioShare support is limited to 16-bit 44.1 while export to 'iTunes' has no such limits?
With Files.app support enabled export to 'iTunes' would be sufficient as we could pick up the files without the need to use a computer or send them to the cloud(Dropbox) only to bring them back down to the same device.
And well, a 'proper' Sampler Gadget with 'Resample Track & Scene' options and recording external sources
(Export Track & Scene would be handy too)
It would be super bonus to be able to use user-samples in all Gadgets that are sample-based (London, Recife, Amsterdam etc) and also be able to use all the included samples from the Gadgets in for example Vancouver
And on the top of the list is a Linear Sequencer and Curves for editing the automation with optional 'step quantise'(think of this as the 'Smooth' & 'Stepped' automation options on the Electribe).
I do have a 'love & hate' relationship with Gadget...
Cheers
/Samuel
I think it's just a matter of time, but it could be a looong time before they decide to commit. And by that stage Apple may have even decided to remove IAA from iOS15/16/x etc so they may have to.
They wanted to know more about Full screen AU and so think weren't aware of recent developments and this is Apples fault for not making developers more aware of the feature.
I've been doing Apples work in promoting the format for them. I recently managed to get Chris Randle to implement Files access to Quanta AU, because he wasn't aware that it was possible and he's one of the most experienced AU devs out there. So if he missed it it's no wonder companies like Korg are deciding to hold back on AU until it's more well documented and mature.
So this lack of documentation by Apple is making things take a lot longer to progress than they should.
The community pages are here https://support.korguser.net/hc/en-us where you can post feature requests.
Good job!
I had similar positive sounding responses from them around iOS vs Desktop pricing some time ago....nothing changed !
Are we talking Gadget as AUv3 host? Or making their synths AUv3 to use in other apps?
Gadget as it is, is already a CPU hog. I personally don’t want this to get worse. AUv3 for all their synths is fine of course.
I asked (again) about the status of the cpu/battery problem and requested Files app support.
They replied today:
I just want the gadgets as windows VSTs
when’s that gonna happen...
Korg standalone synths as AUv3s. I don't want Gadget as an AU host personally, think that's unnecessary.
I would like to see my org gadgets as an AU in AUM too, so both and
Okay, that’s what i thought. But some replies gave me the impression it was about Gadget as host.
At some point I'll try to collect all the ideas into a message that fits the form (it has a limited number of characters so when 'free-styling' a message I bump into the limit quite easily).
For 'resampling' the solution would be to be able to export selected track(s) and scene(s) as one file instead of the whole track to 'iTunes' as the destination since that makes the exported *.wav file directly available for Bilbao, Abu-Dhabi and Vancouver Gadgets.
With Files.app support it would be possible to fetch those exported *.wav files from any app that supports Files.app/DocumentPicker on iOS11.
Another idea is about being able to use user-samples 'everywhere' where samples are used and also be able to use the stock-samples in any Gadget, not just the one they were created for.
For example use the sounds from Amsterdam, London, Bilbao, AbuDhabi and Receife with for example Vancouver.
Technically it can be done since they are just *.wav files but Vancouver Gadget doesn't 'know the path' to those files, so there could be 'path buttons'(Just like the Factory & User) but they would just point to the folders in the other Gadgets.
These few additions alone would increase the sonic scope of Gadget by a large margin
Next If one can wish would be a new 'synth/sampler gadget' that could use user samples and be based on the iWavestation and iM1 again with access to all the samples available inside Gadget, say hello to wave-sequences with user samples. Oh and it should be able to 'sample' as well and provide basic editing tools.
Korg could add separate audio outputs and AB state saving if AU is so much trouble .
Don’t have Gadget (prefer the lightning fast but old Caustic instead) , but reading comments,I don’t know how useful an AU version would be since it seems cpu heavy for iPads .
Yeah I see the confusion, I updated the first post. It was mainly in response to IAA being inconsistent so having AUv3 as a better implementation for their standalone synths when connecting to hosts.
Seems like a polite: not at this point in time due to financial/time constrains.
I’d rather see a proper audio gadget TBH.
Korg AU would be nice, but there are so many alternatives coming out now
I probably should have made it clear at the beginning the AU feature request wasn't about Gadget.
I agree there are lots of alternatives coming out but if/when Korg do do AU they will be very good because their UX is always very well done, maybe why they have avoided so far as they are still finding how to do it successfully.
Would love to see iMonpoly/Wavestation/Oddyssei/iMS20 as AUv3
If Apple drops IAA support probably Korg will abandon Gadget as is and start selling AUv3 gadgets without any reburfish or offer for old users. Any other scenario will be a miracle.
Sad but true
Personally I don't even need IAA-Support in Gadget as I mostly use it as a stand-alone and export the audio to other apps when needed. When Gadget gets Files.app support this process will be even smoother. Ie. just export to 'iTunes' and fetch the files from Cubasis, BM3 etc.
True true. This accounts for 90% of my Gadgeting these days, the old export stems pipeline. Although there are occasions when I pipe it through fx and noodle in realtime. Maybe it could be an AU like Beathawk?
We'd need iPads with humongous amounts of RAM if we wanted to run multiple instances of the full Gadget as an AUv3.
I do feel IAA will be around for quite some time so there's no need to worry...
Now if we had something similar to SoundFlower on iOS we could pipe the audio from any app to any app more easily without the need for IAA. Each app would just pop up as an Audio Input
Who knows what Apple is cooking for iOS13 or so...
Heck, maybe they will have an AU router path?