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 do get it @Simon , but if I got outraged at every app developer over the years who didn't tell me what was in an update, I'd be institutionalized by now. My take is similar to @Gavinski, that the developer didn't think things through. Didn't think through making AUv3 free, and changed course by paywalling it. Didn't think through the reaction to the silent change to paywall it. It is sloppy but independent developers sometimes have to make choices they don't fully understand, and I cut them a lot of slack.
Let's put it in perspective too. The total possible damage is $5 ... $.99 if you wait for the next iAP sale.
I'm glad that you get it.
I hope you don't think that I'm "outraged". Far from it.
I bought the $5 IAP because I really love the app. I don’t need the AUv3 functionality or the extra in-app effects and personally I think it’s a bit ridiculous that AUv3 hosting is in there at all. I don’t think it works that great and I’d much rather just add AUv3 effects in a proper host anyway.
He probably added it because some here were demanding it without even thinking through that this is simply an elegant audio recorder editor that would’ve been better if he’d not added AUv3 at all.
The in-app effects are just fine. This is another instance of users demanding features that don’t really make sense, but the developer caving and adding feature bloat to satisfy the peanut gallery.
I just hate it when this happens.
I bought the IAP anyway because I think this developer has created 2 great audio apps. I bought the IAP in Dawnbeat too, even though I didn’t really need it.
People really need to start laying off with all the aggression and unreasonable demands toward these developers. What finally ends up happening is they simply give up and great apps are abandoned. Those of us who’ve been here awhile have seen this happen countless times.
Then the peanut gallery wonders why there haven’t been any new apps or updates in a while.
It’s no wonder why.
Yeah this place could really ease up on devs. Most these apps don’t cost that much and you can’t realistically expect them to have the time to cram every possible feature and outcome imaginable into a $5-10 app. A lot of devs have come on here and left because of it, I can only imagine how overwhelming it can get to get bombarded like that.
Applying AUv3 on wavebox is a delight
Both are there since release… and the in-app fx are really nice…
I’ve only been editing screen grabs thus far, but what kind of files will Wavebox open? There’s no mention of it in the manual.
I’m getting an error trying to open a wav recorded at 48k and 24 bit. Only two bars long.
Try File > Import Audio
I was able to import a 48k 32 bit file
@anickt thanks, your suggestion works. I forget about that sometimes. I think it’s an audioshare thing, right? Or is it just app dependent? whatever you’re trying to share.
Finally got around to installing Wavebox on my Mac. It's by no means perfect. The window resizing is a bit janky for example. My iAP carries over, which is very generous.
I'm going to compare what I can do in Wavebox with ocenaudio and Amadeus on the desktop. Time for a change. Been using Fission for years for quick little trims of audio clips but it doesn't handle multitrack files, so that's out. Used older v1 Amadeus before that. I've never gotten along with Audacity, which I'm sure is capable.
Not necessary to load plugins for my needs, but desktop version loads some Audio Units. All the AUs installed on the system show in the pulldown, but only native M1 versions actually launch, not Rosetta ones. Among those that launched include Kushview Element and Metaplugin, plugin chainers. Tried loading a few Rosetta VSTs in via Metaplugin and the plugin windows opened, so that's a good sign. Not sure what happens when music passes through or a load is applied. Will find out.
I don't get the sense that the dev intentionally exposed the depths of these audio unit loading functions, just selected to allow it. Makes me happy to know there will be a lot more cross-over capability between ios and macos as new developers start and older ones update their toolchain. Seems to be made available through a few compilation switches and use of certain libraries and functions, is how I understand these features are being exposed. One pitfall, something about how the application must be sandboxed in the OS, because a few plugins were complaining about licenses. Metaplugin applied the license file just fine, but that's where I stopped. I wonder how iLOK behaves in this scenario? Or machine-locked licenses? Seems like a batch of future problems for plugin developers.
Is wavebox tempo aware?
Not as far as I can see.
I fear I’m spreading misinformation, lol.
I just told someone else in another thread that it is. Maybe my understanding of tempo aware is wrong.
What I did was create a loop at 127 BPM in AUM.
I imported it into wavebox.
Chose time stretch and without actually stretching it did show 127 after I input the correct amount of bars.
Is that considered to be tempo aware? Or was it simply cause the original recording was cut at exactly the end of the bar?
I’m guessing tempo aware may be the ability to detect transients and derive the tempo that way? Just wanna be on the same page since I’m not well-versed with audio editors.
I'm assuming tempo aware means that it has some way of detecting/inputting BPM and ideally also setting the workspace up to use beat scale rather than time scale. Amadeus can do that but neither Wavebox nor Ocenaudio can. I have seen nowhere in Wavebox interface or docs to input, detect or otherwise work with tempo.
In Wavebox load a file, go to Actions, select Time Stretch, enter number of bars. You will get BPM in the Tempo display. It was accurate for every loop I tried.
Interesting. Thanks for the heads up. I didn't dig down there yet. So I guess it is tempo aware ish.
Hit & miss on the 6 loops I tested. Worked with 100bpm drum loop and 70 dobro, but failed on pad at 125 and cello at 130. Perhaps works through transient detection? Doesn't seem to be anyway to override with manual BPM.
I did a couple more tests. Seems to be dependent on the region. So if you import perfectly cut loops, it’s accurate, but that’s to be expected. . I gather bpm detection and time stretch are two different things.
I imported a loop I made that was recorded with a record quantize to the bar, and the instrument was randomly played plus had no transient. After import, the proper BPM was calculated.
Then I imported a simple 4/4 loop I made with a midi sequencer using drums for pronounced transients, but purposely made the recording not to the bar quantize. After importing, the calculation is off, unless you manually make the region to end by ear where the bar would have ended.
This is not beat detection.
I’m interested on having a beat grid and snapping to it. So for example cutting a file at 4 bars at 120Bpm
+10000 I would reaaaaalllyyyy like this too, it’s prob the only major drawback for me atm
I gave Wavebox another spin…
It’s missing basic things like snap to zero-crossing and options to view/edit loop meta-data for instrument samples.
And like mentioned snap to grid and set ‘down beat’ when chopping loops to specific lengths.
The AUv3 implementation is nice and way more stable than TwistedWave which has a tendency to fail rendering the ui of some plug-ins and hard crash on others… (I’ve reported this to the dev and get the constant ‘too few requests for this, yadayada’).
In my comparisons of desktop editors I found Wavebox wanting. Ocenaudio is a real beast though. On ios, I can see using Wavebox for quick trims and edits of audio only and nothing more. I hope the developer keeps on improving it.
Does anyone know how to adjust the recording sample-rate in Wavebox on iPhone or iPad?
It seems to default to 44.1k (on a 48k only device like the iPhone 8) and no way to select which microphone or input to use?
I'm wondering the same thing, it's such a pity because this could be the perfect field recording app for me...
I'm mostly using TwistedWave for my 'field recordings' as It allows me to monitor using a lightning headset (or headphones connected to the Lightning -> 3.mm dongle) and select any of the devices built-in microphones (Back, Front or Bottom) for recording using a long-tap on the record button which is super handy (It does NOT allow input selection when using an USB-Interface with multiple inputs, for that I need to use either Auditor or a 'DAW').
AUv3 processing in Wavebox is a bit more straight forward compared to TwistedWave but both work for those duties.
I'm actually quite impressed by the free Dolby On app for field recording. The editor only allows trimming but the built-in processing is top notch! (it defaults to using the bottom microphone for recording).
Well maybe I should give TW another chance, I have a tense relationship with its UI, unlike the orange & teal in WB that makes me feel focused on the recording. Sure I will have a look at the Dolby app, many thanks Samu!
Downloaded and opened it for the first time, import a file — “file too big”
Cool 👍
How big was it?
337mb mp3
No “open in” functionality either. And since we all use AudioShare as a file browser for audio, this is a dealbreaker.