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
HOLE _ AYE _ ISHT
Every so often I hit refresh on the available android audio apps, nothing has really stood out to me. This is something else. Still learning the workflow so I'll get more familiar before weighing in too heavy but even from the git go, love the way social is built in from the start. This is how a social daw should work! Incredible...
Naming is a bit unfortunte, I get the pun but searching for "bandpass" gets you everything audio related that isn't it.
I think you're missing the point. Even if the app wasn't using cloud storage, it was "built with a social focus so you can collaborate with others and make music together"... I guess that could be anon, if you wanted it to devolve into an audio 4chan
I would even go so far as to say I'm glad the dev has deprioritized offline features, there are so many offline daws, this one is something different, I'm excited to see where it goes by focusing on the social horizon.
If anyone else made it through the login process my alias in bandpass is k9d and I've got one ditty started. Would love to connect with some others to try the more collaborative features. If the collab bit is as tight as the latency, this is going to blow Gadget on Switch (and the rest of the collaborative daws I've tried but dropped) out of the water.
Ah, it has a feed! It would be nice if there were audio previews in the feed before downloading the whole track. Maybe first tap brings up a preview that you can then go back from or load?
The tutorial did hang up on me once, right before I was supposed to try drawing drum notes in. It froze on a screen that had 4 looping arrows as the background (forget what that view is called)
Amazing latency and quantization for an Android app... running great on my old 1st gen Pixel (not the XL).
Can you do a bit of a summary on the right Android device for the DAW and it's cost?
Are there audio interfaces... would my Presonus AudioBus work? Bluetooth Pedals and Keyboards? Just curious if you have the opinions it could be interesting to learn.
I suspect Android "hardware" offers interesting options to get closer to the hardware and install optional OS'es, etc. It has to be since it's multi-vendor by definition: a blessing for some and a curse for others.
Unless I misunderstood what you mean by "getting closer to the hardware" I suspect Android isn't going to fit the bill. If anything, there's more likely to be a big fat abstraction layer between the hardware and the OS, because the OS is made to be agnostic of the hardware. iOS is optimized for specific hardware architectures and will always be more efficient than Android in that regard.
Right, that makes sense!
With my tin foil hat on, I’d just like to point out that the feds love usb access to your devices
This Bandpass beta, and the 2 G-Stomper apps (Studio, and the Producer beta), the very cool Drum Pad Beats, and the older other Android-only items like Phoenix Studio, Milkytracker, and the cross platform ones that I already love (SunVox, FLM) convinced me to buy into the Android ecosystem. I went with a Huawei Mediapad 5 tablet. Cool shit!
My general thought was similar to the early days of the Intel-based PC taking on Apple's
Apple II (with the Motorola Processor). IBM sold the rights to the PC design to manufacturer's and what followed was a users ability to make more and I would state better use of the hardware. You could get products from multiple sources and run a variety of OS'es on it.
Thinking of Android as an OS (which it most certainly is) puts it in the Microsoft version of that history as a dominant OS supplier for multiple hardware vendors. As we know that was not a good fit for getting control of your hardware but it played a huge role by routing investment towards cheaper, open hardware.
So the success of MS gave us robust and cheap hardware to get closer to the hardware (by not loading DOS/Windows but something like Linux). Android is doing that buy bringing us more and better hardware options to control using other Non-Android options.
Android is doing that with Mobile devices that we can get closer to and own the hardware as ours and not something we need to beg the OS vendor to open up for better access to the
hardware.
Obviously, the virtuous circle Apple has created its IOS for Music is powerful and the stability of Android for music is questionable (I would guess). But I prefer open approaches and competition from multiple suppliers to have the best outcomes.
The "cloud" runs on Intel-based chips using open source OS'es and tools and the hardware it a generalized layer of obstructions for a developer who doesn't care to get close to the hardware but for music we want the best realtime experience we can get and that means better access to hardware in many cases. So, I'm hoping Android funds the development of billions of open hardware devices like MS Dos did for the Intel PC design.
FYI: Google ended up buying Motorola (Apple II) for their chips and phones in the Big Fish Eat Little Fish history of Tech.
IMHO going with Google devices is the thing to do. Then the creator of the OS and hardware are one in the same and able to closely tie the software to the hardware, much like Apple does with their eGosystem. Having access to software updates before any other manufacturers has been great for me on this og pixel. The fact that the phone is 3 years old now and still kicking... and I don't feel a need to upgrade... really says something.
BUT! I am super curious to hear how that Huawei Mediapad @Littlewoodg picked up is doing! Some people swear by their Samsungs, and samsung took their own approach to low latency audio (haven't checked into see how that is doing).
I'm still addicted to Korg Gadget on my iPad, it feels like home. But finding an inspiring Android app to bust some beats, collaboratively?! Does have me excited
@staRpauSe
The Huawei tablet is a beautiful object, and performs beautifully. I got the Huawei because it has the fastest processor of available android tabs in my price range, (the G-Stomper apps are pretty demanding)
The Apple II used a 6502 CPU by MOS Technology and was a completely open system with even the firmware of the ROM documented officially.
That chip ran at 1 Mhz clockrate and has nothing in common with Motorola products for which Google aquired the company.
Apple closed the system with the release of LISA and the Macintosh, and went the (now common) way of an abstract software layer between hardware, OS and applications.
They added strict developement guidelines which you had to follow as a developer, but these guidelines established a degree of compatibility (with future releases of the OS) that was never achieved again.
In the early days you even had to qualify as a developer, you couldn't just simply buy an SDK.
Long story short - without that approach we wouldn't have iPhones and iPads and a flavour of Unix that can be handled by even the most stupid end-user.
The 'bad guys' at Apple dumped about 1 third of the company's revenues into research and developement for decades.
Most of the results aren't visible, but in recent years Apple published a lot of code and the core of the historic developement system... after getting patents on practically everything.