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.
Blocs wave - Pro Features bundle
Blocs wave now has a Pro Bundle available that contains the Audio Import, Slicer and EQ IAP's
Comments
I've got all the 3 extras installed already but still the 'Pro' bundle is available for purchase?!
This must be a glitch unless the Pro bundle includes more 'hidden' features...
I think it is a glitch...the promo email only mentions the 3
I hope they don’t muck this up with their fiddling.
They keep adding stuff and do not fix what is broken.
I placed a bug-report with Ampify at the end of last year: basically IAA no longer worked. AUM says it’s an IAA Generator and loads it but the audio does not route back to AUM. I am running a 12.9 Pro 1st gen and interestingly a mate running on an Air 2 was not having the issue.
They acknowledged that this was a high priority bug and they were working to solve it. Several updates later - still not fixed. Now IAA compatibly is no longer listed in the AppStore.
What is going on. This cannot be something that cannot be reproduced therefore fixed. Is anyone else having this issue?
Start Blocs first then load into AUM. That should fix that problem. But the AB Link problem is still a problem.
Hey @ageezz, we have still been working on this. Honestly. However we're clearly letting you down by not getting the fix out yet. We're sorry for the delays.
extremely disappointed that this still does not work properly in AUM, sad face
@AmpifyxNovation - Any chance of a fix for your Launchkey app? I bought one of your Launchkey keyboards, and amazingly it doesn’t work with the app. Your app hasn’t been updated for over two years to work with your current Launchkey range, so long overdue an update. Surprised the keyboard doesn’t connect to Blocs too.
Exactamundo. Santa's losing face in my house too
Thanks for the tip - yes that works.
@MonzoPro Our plan all along has been to replace Launchkey app with Groovebox. So the Launchkey app will no longer receive any updates, and will be removed from the App Store shortly. I can only encourage users to switch to the free Groovebox download. The synth in Groovebox is a vastly superior engine. By vastly, I really mean it. The synth engine in Groovebox took us 2 years to make, and is the foundation of our tech. In addition has swift 4 framework, with song sections, Link, Drums, etc etc.
I hope that fact that it is free to download encourages this.
The Launchkey Hardware will work with Groovebox to play the keyboard, and deeper harder support is planned.
@AmpifyxNovation - thanks for you response. The fact that you have responded in such an honest way means a lot. Blocs is such an important App for me. I can certainly live with @CracklePot’s workaround.
The Launchkey app looks custom built to work with the keyboard - 8 knobs, automapped etc. I’m sure Groovebox is a nice enough app, but I can’t see any special connection to your hardware. There’s no reason for Launchkey owners to use Groovebox over, say, any other synth/beatmaking app.
I also don’t understand why the 8 pads in Blocs, aren’t mappable to the 8 pads on the Launchkey keyboard, or any MIDI control at all, yet Launchpad is fully controllable.
Weird inconsistencies in your product range, and with Groovebox now taking over from Launchkey it’s as if your hardware/software departments aren’t speaking to each other.
Thanks for the reply, but it’s disappointing for recent buyers of your hardware.
Yep, not regret, but a bit of buyers concern creeping in...
Please tell me Blocs won't meet the same fate
It's my favorite iOS app, and I've purchased literally every IAP. But it's still not working properly with AUM.
I love Groovebox, the synth engine is killer, and the time and hard work you all put into it really shows. But I've got a lot of grooveboxes. There's only one Blocs.
"I also don’t understand why the 8 pads in Blocs, aren’t mappable to the 8 pads on the Launchkey keyboard, or any MIDI control at all, yet Launchpad is fully controllable."
ooh, that sounds like a master plan. i'd love that to be the case. and ... i'd buy all the remaining soundpacks
I feel like I could have written this post.
It was, around 4 years ago when we launched it.
There are 8 pads in Groovebox, and song sections. We have kept this in mind. Also Launchkey has full integration with Launchpad for iOS
If you mean Blocs Wave, then this is technically possible but we think users might want support in Groovebox first.
I think this is actually more down to user request prioritisation. Tthe designs of the apps afford a hardware support, however we've been tracking user requests for this, and they are lower than things like: Patch saving on Groovebox, User Library management in Blocs Wave. I think users want this a lot more.
We're sorry you're dissapointed,, and hope you stick with us.
@AmpifyxNovation the latest version of Blocs crashes every time you press the "i" or info button in the top right corner. No big big deal, but a bit disturbing
On dear. That's not good. Can you pm us? We'd love to get some more info. It doesn't seem to crash on my iPad.
@AmpifyxNovation Thnaks for the info about LaunchKey. I own the LaunchKey Mini keyboard and have always enjoyed how it integrates so well with both the Launchpad and LaunchKey apps. I hope the knobs and pads will be available for use in all of your apps moving forward. Groovebox is an pretty decent app, but I don’t love it. Maybe with more keyboard integration I’ll fall for it, but it’s gonna be tough to replace the sheer joy I get with the current configuration. I do appreciate your efforts and wish you much success.
@AmpifyxNovation
Y'know, it sounds like you could really benefit from putting out a survey/questionnaire on what your entire customer base would like to see across your apps and hardware. Rather than culling that info from forum posts and support tickets from those who have the patience to get in touch?
This would provide an easier and more uniform data set to work from.
You ask, we'll answer.
"If you mean Blocs Wave, then this is technically possible but we think users might want support in Groovebox first."
well, its the samples, really. the sample packs and how easy it is get something going- stretching plus key change. nothing out there that's as user friendly for samples imho.
Can confirm this crashes the app.
iPad Pro 12.9
Latest Blocs Update
iOS 11.1.2
Happy to Beta test with Testflight.
PM me if you need details.
Hey @SpookyZoo, just open the Launchpad for iOS and check out the news, and you can find the survey there. The Survey closes this Friday.
App users on iPad maybe, but I can’t believe hardware owners don’t consider Launchkey keyboard support essential.
“If you mean Blocs Wave, then this is technically possible but we think users might want support in Groovebox first.”
Why? Groovebox is a relatively new app, surely Blocs should have been supported either at, or shortly after release? Why does a newer app jump the queue?
“Also Launchkey has full integration with Launchpad for iOS”
I know, but none of your other apps support your current keyboard in any fashion. I have better support from other app developers for your keyboard, than I do from you.
As I said above, inconsistent development, and a big void between your software and hardware products that doesn’t sound like it’ll be filled any time soon.
Do you have a link for that survey?
EDIT: Found it....
Ok found it.
There's another 'Tell Us what You Think Link' on the website.
https://ampifymusic.com/survey
Come on Peeps, let them know!
The Survey closes this Friday.
If you have launchpad for iOS, we are running another survey also, and that one closes on Friday.
The sad true is even filling that survey and mailing them with ideas @AmpifyxNovation seems more focused on young Madeon copycats than make Blocs hardware or add arranger features to Groovebox which made users like me keep loyal.
It seems focus lost but I still hope they see how iOS is evolving. Apple is going to have a crash soon due it’s quality mistakes (and iPhone centric strategy) and pursue that mentality will make fall with them.
Now is time to think twice the strategy, call me mad but we will see over this year and next.
@AmpifyxNovation Groovebox is like other apps that already exist and not that interesting to me, whereas Blocs is quite unique and my most used app by Ampify. Launchpad should have been number one (I wanted to use it in live performances), but the fact that you can’t trigger it unless it’s the focussed app led to me ditching it and getting Group the Loop. I’d love it if Launchpad could be triggered via midi while I’ve got another app open. I’d love to be able to drag and drop to reorder pads, and trigger a whole row with those big arrow buttons on the right on the launchkey mini. Thank you for listening.