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
So that's why all the DAWs I use on desktop scan for VST's as a separate process. Misbehaving VSTs can crash the host.
Yeah, this is why DAWs like Bitwig host them separately.
Obviously, it's totally personal - but I wouldn't mind if they just ditched VSTs altogether and only went with AUv3.. I use the AU version of literally everything I use. I don't even install the .vst's onto my Mac haha.
Probably makes no diff. I just notice that he says VST in the vid.
Who knows? Maybe it'll also run as a VST. That'd be pretty sweet for some things.
Loopy will run both as a standalone and as a plugin.
Since a lot of people use VSTs, the plan is to support them as well as Audio Units.
I think a long, long, term goal is also to have a Windows version too, right? VST support is essential for that.
Yes, the long-term plan includes a Windows version.
That's cool for people that are into that. Not my kinda thing lol.
Good plan, with prices for Mac OS devices now on a par with iOS (Mac Mini M4’s for £500, MacBook Air M2’s around £600), and Logic as a one-off purchase, it’s becoming a more affordable platform. I don’t use Loopy Pro, but I’d certainly be interested when/if it gets Mac DAW support.
The Colugo dude, creating BlockHead (in alpha state) do have the exact same issue as you @Michael , sandboxing VSTs. Also seem to have to invent a solution from scratch.
Yeah. The VST SDK is very poor, sadly, and forces developers to reinvent the wheel over and over! Boo! But it is what it is
Doesn't seem to have as much potential to break or change with every OS update like Apple stuff though. 😉
You got that right!
Fantastic to see @Michael is using "A.I." where it makes sense for programming. I can't imagine trying to deal with very complex projects as an individual without constantly tearing your hair out.
Certainly speeds me up! Occasionally slows me down, but definitely net positive
There’s a real push where I work to use AI for everything, and developers seem to be the focus right now. Not sure where things stand as I don’t work in technology, but it’s a big enough deal for me to hear about it often.
Fantastic I been using Loopy since I can’t remember in fact I still have a lot of Loopy HD projects ready to import into Logic but bringing a project in to Logic and wrestling with those live loops cells is so horrible like setting the timer on my dads old Vhs recorder So yes Please Please bring it on.
Loopy HD? That’s a different product that’s no longer under development. There won’t be a Mac version of HD. As far as I know there’s also no backward compatibility between Loopy Pro and Loopy HD projects.
So impressed that Michael has been open about his use of AI to help code Loopy Pro. It has a been a bit of debate here in the forum and everywhere actually. But if the industry's most capable and respected find it beneficial, I think that will definitely open some people minds.
I think the debate has been more about vibe coding (programming exclusively using AI and not necessarily knowing much if anything about programming) and agentic coding (using AI along with one’s own coding skill to get more done while still understanding what’s being done. )
Michael is certainly one who could do it all himself, but knows how to leverage AI assistance for the best of both worlds.
That is a really interesting response, as that is not how I viewed the term "vibe coding" at all. But you have made me aware that many people are likely to view it in the exact way you have expressed.
You have specifically connected the act of using prompting exclusively to generate code with not knowing much about programming.
And your definition may be the right one....I asked Claude Code whether I am vibe coding my apps, and it responded with the below.
Your CLAUDE.md briefs with DSP specs and the architecture decisions baked in are the antithesis of vibe coding. You're specifying intent precisely and constraining the output. The model's doing the typing, but you're doing the engineering.
And even Karparthy who actually coined the term "vibe coding" has tried to retire the word for serious work, and replace it with "agentic engineering"
p.s. I work full time as a Lead Solution Architect at an AI software startup and have 100 followers on my Github, I guess that means I know a little about programming.
The fact you know what a CLAUDE.md file is says you do more than just vibe code.
I’ll start by saying that I don’t know the actual definition of “vibe coding•. I’m using it in the context that it has been used / debated about here on the forum.
Forgetting about the terms for a minute, there have been apps introduced here that are 100% created by prompts, and by people who who freely state that they know next to nothing about coding and nothing about DSP. They have said that they wrote none of the code. I have one of these apps and like it a lot.
That’s far from what you and Michael have been doing.
I don’t really care what the various approaches to using AI for software are called. I kind of care about the implications relying on a piece of software created by someone who knows nothing about coding. But on the other hand I don’t expect that to be an issue with the one app I do own.
I don’t have any of those concerns about apps created all or in part with AI by someone who knows what they’re doing.
That said, I can come up with plenty of examples of buggy and abandoned apps developed wholly by experienced programmers. So, I see most of the debate / controversy as interesting but too speculative for me to give much weight to personally.
As my grandma from Texas used to say, “It’ll all come out in the wash, son.”