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
It can do more than what iElectribe does, but it can't do what iElectribe does in as musical a way as iElectribe does it.
First thanks for the kind words on the track! Second, this is basically the final word on the issue, couldn't say it better myself. It's also why I prefer the VA version of the hardware to the sampler, it's simply a musical instrument.
This is a great read! I'm still working through it. But AWESOME. Thanks so much for digging in and sharing.
You certainly have!!
Wow... This article on rhythm is simply brilliant. Thank you so much for writing it.
http://lieslavish.tumblr.com/post/139820760048/the-anima-on-genre-how-styles-are-defined-2-of
I would recommend everyone read this.
One of the best pieces of its kind out there. It was really great to read someone walking through ideas I have a fair knowledge of but bringing it together in such a well explained way. The history of the 1, 2 and 4 beat 'cell' was certainly new on me. And makes a lot of sense.
I look forward to catching up on the rest of the theory articles.
Thanks for the response, lieslavish..The volume button in Beathawk is one way of doing it, I guess. But I'm just a fan of old Skool hardware drum machines that were multi layered like the Alesis sr16 (dual layered and the competing Yamaha drum machine which at the time was layered four deep. Ditto for Korg Kronos, Yamaha Motif, etc. I'm waiting for Beatmaker 3 to come out.. Personally I don't want to hear the same sample playing as I get louder and softer, even in a synth drum tone. But that's just me. Thanks again for your response.
Thank you for reading. It more than justifies the digging-in!
I really appreciate that; I've been putting a lot of energy into the theory articles, but I understand that they can appear a bit overwhelming -- probably more-so than my app overviews. 'The Anima' is about writing on traditional music theory from a much more abstract perspective, since, from my own style of learning, I think that it's easier to get a better grasp of them, that way.
I write about subjects that took me a very long time to really wrap my head around (and there's still so much for me to learn) because nobody (or just one or two people, which finally made something 'click' for me) really illuminated these concepts from the right perspective.
So, I'm not saying that my posts represent the only or even the best way to understand the concepts that I'm writing about, but it's how I understand them and I hope that it might be of use to somebody out there that thinks kinda like I do. I'm really glad that you got something out of it. Like, really really glad, haha.
I hear you, dude. Also, I'm eagerly waiting for Beatmaker 3 as well, but, as far as I know, there's no news about it.
If you want to hack your own velocity-layering, it actually would be very doable using sweet, sweet MIDIFlow. It can filter and reroute MIDI messages based on logic tests, so you could use Beatmaker (or any other sampler app) to set up your 'multiple layers' across multiple pads. Set up MIDI Flow to send a different MIDI note when you tap the same pad with different velocities, and voila.
I guess one issue with putting apps head to head is that often one comes out on top making the other look 'bad' or unneeded to some. Developers might not be crazy about that but I guess then again any review less than positive could have the same effect.
Might depend on what kind of relationship you want to have with developers?
Still I like reading them just like I love seeing software vs hardware videos.
All depends on how you do it. If it's an arena match, that's one thing, but comparisons are hugely useful in so many ways, thinking for example about the ielectribe v. ispark comparison we were discussing above, it's helpful because that lets somebody familiar with one have a starting point for what the other does. The Juno 60 and Korg Polysix were both great polysynths, but comparing them can be a great way to figure out preference, which is not the same as one app winning. (I found the polysix to sound warmer than the juno but the juno chorus is wonderful.... anyhow off topic).
What @lieslavish said in comparing the ielectribe and ispark is a perfect example of a comparison that is tremendously useful and not denegrating to either app. The electribe is more musical in what it does, but far more limited in what it can do. Head to heads like that, fleshed out into a full article could be great.
But you are 100% right, some developers simply won't like it if their app doesn't sweep every column, and sometimes, if your are editorially honest, you will have to say "this app is superior." That's the risk.
I got a better idea for the beat flutter.
In the header bar where it says beat flutter (waste of space) replace with 4 buttons labelled 1-4. When you hit on a flutter square you like hold one of these buttons down to set it. Can set 4 of these then can Select it to play back that coordinate.
Problems with that idea? Is that a lot of work for Korg?
How do I get them to implement?
It's a great idea, but KORG is a large corporation with their fingers in a lot of products; asking them to dedicate resources to updating an already finished product with a feature that they might figure won't generate more sales than they're already getting -- it's unlikely to happen, but you can try shooting their customer support an e-mail!
With smaller developers -- well, for one thing, they tend to approach development more as an art, and they take more individual pride in their product because they're solely responsible for it (unlike larger development houses, where there are large teams involved with the project, from development to production). Furthermore, smaller developers have more to prove since they don't have the name-recognition that comes from just putting "KORG" in the front of the app's title, so I think that they tend to be a bit more interested in perfecting their apps.
Just a thought, but my point is that you're not going to have a lot of luck getting KORG to implement a new feature in any of their apps; they'll implement what they're gonna implement, haha.
@lieslavish
So I need to get a job at Korg. Which is pretty unlikely I reckon and even then I agree good luck getting iElectribe updated with that.
Anyway I might as well fire off an email. What's the worst that can happen? I get a job at Korg?
Do that, and, if you do get a job at KORG, let us know so that you can be our inside man. >:3