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 have an unstable 10 Mbit connection that costs 1 Euro per GB 😉 (it might be 50 cents or so, can't remember)
But I still find it kinda outrageous that an IDE and compiler is 12 GIGABYTES. I mean, 12 MEGABYTES would be plenty!
(yes yes, I know it includes all the damn simulators and documentation and whatnot, but why isn't that optional and why are there no delta updates?)
But that's a fixed line connection right? I'm on an LTE connection because I always have to move house so a fixed contract doesn't make any sense...
I use https://makeappicon.com for that! Auto-generates all sizes (the whole "asset catalog") from one high-res image.
(yeah, for being a 12 GB download, they could've included that functionality in Xcode itself 😂)
Frankly, I wonder if this disarray is a side-effect of the programmers working at home and not being in the office together. Things can quickly spin out of control if people are not in constant contact with each other, even in this age of FaceTime and Zoom.
Could be I guess, it could at the very least be making moving forward with the changes more difficult for them. My general cynical feeling though is that some in the audio team really don't see the move to Swift or even Objective-C as the right way to go so the disarray in the template is reflective of this. (I don't actually disagree with this mindset either. My own personal feeling is that these interfaces should be defined in C and then made available in higher level languages.)