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
To be fair, at an average compression ratio, that's probably several hours of audio that first have to be decoded, which will then probably occupy around 7 GB (!). So it's kinda understandable.
👍
Have you heard about Media Assistant ( free )?
New update out yesterday…
-Auto slicer enhanced
-zero cross option
-drop audio samples from files
-bugs fixed
If you don’t have this app you should get it. I have every audio editor for iOS and this is by far the most user friendly and functional. A few more changes would make this app perfect but still use this more than any other editing app. Tools for bpm would really make this app amazing. That’s the only thing i still do in auditor. I’m probably going to put together a longer post about why this app is so useful because Ilove it so much. I think it was a bit buggy on release so may have not made a good impression on some, but now is stable as anything for me.
A couple small bugs….
-If you try to drop an audio file on the splash screen a plus symbol will appear but there will be an error. If you start a session and drag it works so not a big deal. (Just a warning for those who think drag from files is broken.)
-autochop skips the first transient which is fine if the audio starts at the beginning of the file but not fine if there is some air at the top.
The app is free to download, but can you do much with the free version?
It looks like there are a lot of IAPs:
-Audio Editor Vocal Removal $9.99
-Audio Tagger & AUv3 $19.99
-Audio Editor Utilities $6.99
-Read Aloud & AUv3 $3.99
-Audio Converter & Joiner $4.99
-Browser AUv3 + IAA $22.99
-Audio Editor Basic Features $6.99
The file browser with audio preview when you touch a file is free.
This app is my goto sample slicer.
OK, thanks!
Love Wavebox. No sure if he’s still giving it away, but I paid for it with absolutely no regrets. Excellent developer too.
One thing he added a long time ago is that if you want to share your audio edits on Social, you have the option to export in video compression and add your own image to it. Very handy for social media sharing. I used this feature a lot while traveling.
You can also start recording, hit pause, the re-engage recording by unpausing. You can also set Wavebox to auto crossfade between your record/pause/record sections. You can even pre-set the length of your crossfades.
Very cool for walkabout environmental recordings.
It even supports AUv3s!
And, it’s even completely universal, including native macOS!
It’s insane that this dev feels like he has to periodically give this app away. It’s absolutely worth paying for. IMO
I like the simplicity of the Meow editor too, and am hoping it continues to be developed further, but for lightweight, full featured, universal, and fun 🤩 it’s my favorite on iOS, iPadOS, and macOS for that matter!
Recording using both Internal Mic and 'Screen Recording' work fine here, 11" M1 iPad Pro, iPadOS18.
Hi - would like a bit of help from a Wavebox user, if you're willing please.
I've had a report that my latest (from 2025) AUv3 plugins aren't loading in Wavebox on iOS. Anyone else experiencing this, or willing to try?
Here's one of my freebies if you don't have any of my plugins.
https://apps.apple.com/us/app/faketake/id6743768308
I've contacted the developer with a view to debugging the issue together, but in the meantime, if someone's willing to give it a go, pick one of my plugins you'd like, and I'll ping you a code as a little thank you.
Cheers, -Rob
Hey @Rob_Jackson_Music
I just recorded background noise from my bus ride in to work and tried to add PolyDelay to it and the app crashed twice.
I then did the same thing and added Klevgrand’s Grand Finale and the app did not crash.
I hope this helps!
Thanks @timelining - good to get a one that's crashed for someone, as it doesn't seem to be all of them. Which is strange, as the basic AU wrapper code I use is identical. Anyhoo...
Message me if you'd like a freebie. No rush, offer remains valid forever
@Rob_Jackson_Music Bitclip, DimChorus and PanDualay all loaded fine on my iPhone in wavebox and applied the effects as expected to a loaded WAV file…
One thing that could eventually be an issues here is that many AUv3s expect a two channel input and when they get a one channel input they crash, and crash hard.
(AudioKit Rackreverb AUv3 is one plug-in that can't handle one channel input and just dives).
So my guess is that the user who got the crash tried to process a one-channel mono-file...
Cheers @Krupa. Message me if you'd like a freebie.
Thanks @Samu. All my plugins should handle mono or stereo input, and convert them to stereo, but that's definitely worth checking out.
Oh interesting, I did try a stereo wav, I’ll try a mono one…
Could be that the it's conversion part that fails?
Honestly a mono effect should not automatically convert the file to stereo if it's fed with a one channel input.
The file in the audio-editor doesn't automagically become 'two channel file' when processed by a plug-in so the plug-in (if it processes internally in stereo) should respect the input format and convert the output back to one channel.
Tried again with the same file converted to mono, two loaded and ran fine while PanDualay crashed instantly to Home Screen..
@Samu / @Krupa - yeah... looks very much like this could be the source of the problem. Nice work guys!
So... in case you don't know...
There are safegaurds in the AU protocol around this. Often referred to as "channel configuration" every plugin provides the means of allowing its channel configuration to be queried by the AU host, i.e. mono / stereo input / output at the very least. The AU host can then decide whether it's appropriate to allow the fx to be insterted or whether mono / stereo conversion needs to take place.
This is why for example, you might see in Logic when you insert one of my fx on a mono channel, you'll see something like Mono->Stereo.
My guess is that Wavebox isn't querying / respecting the channel configuration properly, and perhaps assuming mono in should be mono out. An AU host cannot / should not assume that imho.
That's why every plugin has to provide its valid channel configurations to the host, so it can handle it appropriately.
I agree, but the plugin doesn't know it's a file, right? Wavebox should handle it, not "me".
Also, in some (arguably the majority of) cases, I do want to convert a mono input into a stereo output. Whether I should add support for a mono->mono channel configuration is a separate, albeit related topic.
The host should be smart enough to filter out plugins that don't support the desired channel configuration. That's the whole point of it being there.
But the plug-in 'knows' what the input formats it gets so why change it?
TwistedWave behaves the same on iOS. When you're editing a mono-file it sends 1 channel to the AUv3.
Personally I've only bumped into ONE plug-in that 'bails' when fed with a mono-file and it's AudioKit Racreverb.
Solution in those cases is to temporarily convert the file to stereo, process it and convert back to mono.
LogicPro for iPad is one of the few hosts that does this (You get a Mono->Stereo option) for some plug-ins that 'tells' the host what channel formats they support.
But unfortunately not all plug-ins report what channel configurations they support and this when fed with something they don't expect they will bail...(ie. AudioKit Rackreverb crashes pretty hard in Logic too and I get something like 'Illegal Channel Count' in the crash logs).
When I bump into things that 'crash' I usually contact the developer(s) and if there's no fix within a reasonable time-frame (~3-6months) I usually end up deleting the apps and move on...
Wavebox is still my go-to audio-editor on iOS partly because it also allows loadings files stored within document bundles (think digging out audio-recordings from old GarageBand and Logic projects etc.).
As for how different hosts handle plug-ins, many just convert mono-input to 'dual mono' which in some cases ends up wasting disk-space when processed...
Because sometimes that's the whole point of a stereo effect, i.e. converting a mono input to a stereo output.
Bottom line is that it's a contract between the host and the plugin. I've kept my end of the deal
As a plugin, if I say I only support stereo output, it's not my responsibility to generate mono output. How would I know?
We should probably also remind ourselves at this point we don't know for sure (or certainly I don't) as to whether this is the actual issue in Wavebox...
edit: I've pinged the Wavebox developer with another email with our theory.
That is when you report back that you only process stereo signals
But only supporting stereo is kinda short-sighted to be honest...
TLDR; wavebox / all AU hosts should query and honour the plugins channel configuration - short-sighted implementations included
Joking aside, if mono->mono is requested enough, I'll add it to the list. So far, I've had zero requests.
Totally agree here
What I've learned over the years is to never assume anything when it comes to iOS or apps in general and it all boils down to this classic quote (ie. Assumption Is The Mother Of All Fckps) being very, very real