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
I'll put a +100 to the request for an AUv3 Sector!
Yes would love AUV3 Sector!
I mean it’s an expander, compressor, limiter, gate, So it’s multi functional
And soft/hard clipper/distortion
+1,000,000 for AUv3 Sector!
oh yes
I wouldn’t say no to SectorAU but I personally can’t wait for PeakQ.
One tiny request if I may for Push - ‘Bypass’ directly from the plugin, please
Thanks!
None of the AU3FX plugins have bypass directly in the plugin. Do you know of any host that doesn't have bypass?
That said, in Push you can simply drag the Dry Mix slider to 100%
It's random. It's random who you get. It's random if they bother to look at the app. It's random who it goes to when you appeal. This has become worse since they added the video thing. Now they can not bother by either passing the app or give you a rejection saying they need a video. Either way, an easy don't bother to look.
Parts of the process seem to be automated. They do virus and malware checks and parse the code, graphics, and plist files to see if there is anything in violation of the terms there. If a crap app then passes all of the other stuff on a checklist, they go through. The malware/scammer crap gets through this stuff by hitting the reviewers with multiple apps and they don't care if most get rejected as long as a percentage get through. They've figured out how to game the review process.
Even the automated checks are being gamed and avoided now. There was an article recently out on some banking scam apps on Android where the code was incrementally added to updates of apps over time and in combination of multiple apps that eventually let them steal peoples' banking credentials and empty their accounts.
The audio apps would end up being reviewed by the team responsible for Spotify and apps for fans of music stars. Apple can't even figure out how to put apps into categories on the app store. There's no way the could get a valid set of knowledgable experts for all the possible categories of software. And, they basically don't care about anything outside of entertainment and games anyway.
@j_liljedahl I've been refusing to add videos for the reviews because of the little note that says that once you have an approval based on a video then you have to add one for every update. I'd been getting the through the rejection by nicely asking the appeals team to please get a copy of GarageBand for each reviewer and train them how to use it. From your experience on this one, it sounds like that might not work anymore. Maybe if we start adding a little pointless crap game to the container app and put the AU in the games category it can get through the reviews.
Yeah, the interesting fact was that they just closed my appeal because it was rejected "waiting for more information" (the video, which they already got). So they closed the case saying I must start by providing the reviewer the information asked for. As if they didn't even read my appeal, since if they did it would be clear that the reviewer was having trouble understanding and that the "information" asked for did not make sense.
Last time though, it got fully rejected (not asking for information) so I'm hoping the appeal will go through this time.
It’s only for convenience. I don’t miss bypass from the rest of your plugins but when dialling in compression I always compare dry/wet... All hosts provide bypass, but usually it requires some gymnastics (move plugin out of the way etc.)
Yep, I’m using Dry Mix for this atm, but my understanding is that doesn’t bypass the Lim/Clip/Sat section.
Like I said... it’s only for convenience... their nonexistent cpu toll makes up for it
Yes, you're right, the Dry Mix is before the lim/clip. I'll consider adding a bypass toggle in all of them.
Is there a way you could ask to reviewer to see Dub and Space which were recently approved and have similar uses? (Trying to build a path from reviewerBrain to your apps.)
I don't think that would do any good. They do this kinda stuff to everyone. They'll do it to Adobe and Microsoft. I suspect that it's at least a little bit a part of the security theater aspect of the review process.
True. Good point.
Toggling the bypass with cc or a midi note at specific intervals can be quite useful.
lol 😂
That could have described most of the vast amount of time wasted with auditors in my IT career.
Can anyone confirm if Push AUv3 ext. side-chain feature works in Drambo (App Store version) or any other host that supports s/ch, please?
When trying to enable ext s/ch on Push loaded in Drambo (beta) I’m getting a message ‘The host does not provide an extra input bus’ even though the port is there (visible and labelled) and fed with audio signal...
Strangely, other s/ch capable AUv3 plugins work fine in D (beta), and Push ext s/ch works fine in AUM.
@j_liljedahl
I can confirm, same behavior here with Drambo's app store version
Not at the code right now, but I think AU3FX:Push requires the side-chain input bus to be enabled by the host.
This could explain it then.
Drambo does not enable additional bus. It’s automatically present for plugins that can utilise it, even if the feature has to be enabled separately in the plugin.
I recall something similar in the initial implementation of multibus support in AUM (maybe only during beta though). IIRC, NYComp worked out of the box as soon as multibus support was added in AUM, but TBEq required some tweaks.
As far as I understand the developer documentation, hosts are supposed to enable the input busses they intend to use. That way, the plugin can know if it needs to allocate additional resources etc needed for the extra input(s).
https://developer.apple.com/documentation/audiotoolbox/auaudiounitbus/1387634-enabled?language=objc
So, it's actually a bug in Drambo and in the plugins that make use of disabled input busses.
Thanks, will pass the info on to giku