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
Looks like the Several Bug Fixes does not include a fix for the wonky automation/modulation of AUv3 parameters
I've not had probems with automating parameters in AUM, haven't tried other hosts with them.
It's mostly when using the plug-in UI to record automation into a DAW.
Assigning a modulation source to a parameter or drawing automation works as expected.
Not for me. I have a Chicago gadget in Drambo. I draw in an animation curve for the filter freq; sometimes the gadget responds to the curve, sometimes it ignores it.
Drambo’s LFOs have unpredictable effects on the same parameter.
Just to check, I replaced the Chicago with Pure Acid, and it acts as expected.
Drawing automation mostly works, it's when you tweak the plug-ins UI elements to recording automation that things don't aways work as expected
In my experience it doesn’t matter how i enter in the automation…record it with the gadget knob, the Drambo knob, or draw it in as lines. The gadget still just ignores the automation sometimes.
It’s auv3…Use another drum machine/sequencer..BAM or EG node.
But I’ve already got the whole song built in Drambo 😂 I’m still hopeful it’s a bug they can fix.
Yeah I can see why that might have slipped through the final testing...
Make sure to report it to Korg. You may want to include a screen recording and project to simplify reproducibility. I wouldn’t assume they know about it.
👍 I thought this was the same problem described by Samu and others, but I guess it’s not.
The gadgets resize very nicely in Logic Pro for iPad. No stuttering for me and like that.
it’s generally a good idea to report even if you think it is the same since the number of reports can be important in prioritizing fixes.
That's if Korg are even aware of the problem. They probably don't even know it exists.
Not-but-kinda related, I've faced some strange behaviors in Garage Band when a knob in the plugin has the same CC# of the Garage Band's Pitch bend or Mod wheel.
Totally agree. The support channel link:
https://support.korguser.net/hc/en-us/requests/new
I don't understand. Pitch bend isn't a CC. It's a different midi message. Are there cases where pitch bend is assigned to parameters other than pitch in the Korg AUv3?
Sorry, not trying to be picky - just trying to understand.
Stupid question that may have already been covered, or indeed a question so stupid that it doesn’t deserve coverage - can Gadget itself be used as an auv3 inside a daw?
You mean the entire app sequencer and all? If so, then no. It’s only for the individual gadgets.
Thanks HotStrange. Yes I did mean the whole app
Shees. Substitute one problem for another
Goin to say a couple things here. They are my opinion.
Is Korg Gadget 3 better than 2, Yes…by miles not so much…
Cons for me:
1. Never been a fan of top to bottom tracker flow clip sequencers, not a deal breaker
2. Similar Gadgets…I.E. The drum machines that couldn’t compete with Koala even if they were voltron
3. The drum synth that has no tuning references at all…what key is it in ever ever? And no tuner in Gadget?
4. Sydney is like throwing 10-15 bucks in a fire…it’s quite useless…once again no pitch stretch is a big no no
5. The effect Gadgets would be better if there were slot for effect gadgets? There’s more money KORG
6. Zurich is mostly useless…I mean yea you can record something audio I guess…no edit or anything though
7. Gadgets in AuV3 mode crash if you touch them…some of them if you load them
8. Some Gadgets could just be sound libraries for module…maybe make a drum module instead of Amsterdam
9. Sample import from files as well as drop box…is this too much?
10. No User sounds in AUV3 plugs?
11. Bad use of iPhone screen resolution…it’s bad on iPhone, but could be better
Pro’s:
1. The sound category browser is awesome! THIS is great!
2. using Gadget, I create different music than I do with everything else
3. The IFX & interfaces have definitely improved, especially the EQ
4. When they get it working, the gadgets as AUV3 plugs
5. Gadget Cloud does make you want to use Gadget better to enter its charts!
6. THE BEST THING IN GADGET…automation of everything!! This is gadgets super power as it’s easy as it gets.
7. Flicking a knob for fine tune is better than nothing.
I like Gadget, but it remains decent….it could be great, but it’s not quite there.
Do I think it’ll all be fixed…nope
Will I lose sleep if it isn’t fixed…nope
What will definitely cheer me up is when iM1, Iodysee, iMono/Poly, iWAVESTATION, and etc become AUv3 instruments, and I can use them as plug ins!!! That will be more exciting. Even if it’s a small IAP update..I’m in.
Oh and give me a KORG Kaos Effects auv3…now we are really talking.
..
..
I haven't had a crash with any of'em so far (17.2 / M1 Pro).
Me either. Not a single one. And I've used almost nothing else since they came out just for the heck of it. I haven't used any of the new IAP ones that came out, but have all but 2 of the previous gadgets.
(17.2 iPad 9th Gen)
That was AWESOME @MrSmileZ … Thanks !
I am not having frequent crashes with the AUv3 either under 16.x
Just in case anyone missed it: The Stockholm AUv3 can now import REX files!
It needs to be done from inside the plugin though, no sharing of the same loops folder with Gadget and no Files.app integration (yet).
While 'full folder sharing' is not yet implemented the files can be imported from the Gadget folder into the AUv3 keeping the 'source files' in one place it and I kinda understand Korg as 'folder linking' is a hit or miss depending on which iOS/iPadOS is being used.
It would 'confuse' new users if they had to pick a folder first time launching a Gadget AUv3 and point to towards the Gadget root folder and even then since the 'presets' are not visible in the Gadget root folder it would be tricky access them.
Ideally Korg could make all user created content (presets, sample-folders etc.) in Gadget visible thru the Files.app.
Then it would make sense to point the Korg AUv3's to Gadgets root folder and share the user content between the stand-alone Gadget and Gadget AUv3s.
But it's tricky since there's so many iOS/iPadOS they still support...
I've included suggestions regarding the Files.app integration in my bug report and they've forwarded it to the developers. Let's hope for the best 😊
Goodie! It's good Korg has a proper bug-reporting system and they do actually send follow up questions if/when needed
(And if it's quiet, just reply to the mail with the ticket number to push it a bit, that is what ZenDesk is so good for).
I'm waiting for them to fix AUv3 automation in LogicPro for iPad. Stability was sorted out with the 6.0.1 update, automation remains
.