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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

New Aqeel Aadam app Coastline. Out now

12346»

Comments

  • @ChimmyChungaFace said:
    I see some people saying this has a lot of depth, videos suggest otherwise. Reminds me of PaulXStretch: Kind of cool, everything ends up sounding similar. Hey, prove me wrong!

    As I’ve said in previous posts, I too am interested in finding other ways other than the obvious to use Coastline. Everyone’s budgets are different but £12 isn’t low enough for me for it to be a throwaway purchase unfortunately. I shall have to experiment to decide whether I’ll get real, repeated use out of it and, if not, I’m afraid I’ll have to request a refund. As such, I can understand why you might want to ask this.

    It seems owning Waymaker gives you the easiest way to do everything with it, but that’s another £15. I think everything can be done via external automation if you don’t have it but obviously that’s an extra bit of setting up.

    I asked about the two pitch values not being available for the internal modulators and it seems Aqeel sees Waymaker as the way for pitch related things so it’s deliberate that they’re not available. Fine and dandy if you own Waymaker but if not it’s a bit of a shame. I can understand the impulse to tie things into your own app ecosystem though.

    As to it sounding similar on everything, I’m still experimenting but I’d also be interested in hearing examples of the different things it can do. It may turn out to be that it only really does what it’s designed to do though - how dare it! - and it certainly does that superbly well.

  • @Gavinski said:

    @oldsynthguy said:

    @wim said:

    @wim said:

    @ChimmyChungaFace said:

    @wim said:

    @ChimmyChungaFace said:
    Hey, prove me wrong!

    Why?

    It’s a way to engage and elicit further discussion and examples. People say there’s depth, I have yet to see it. On face value and from descriptions this sounds like a nice multi fx app, in practice doesn’t really seem like it. So which is it? That’s what forums are for, no?

    If you watched the videos, particularly the developer’s hour long demo of every feature, and that’s your conclusion, then I can’t fathom what else to say that would be relevant.

    That said, it is true that Aqeel's video is more about just covering all the features than demonstrating all you can do with the app. Also, the audio input he used was kind of same-same across the board, and didn't do as much to demonstrate depth. As a "video manual" it seems to be mostly focused just on covering the mechanics of all the features. If he treats this one as he usually does, there will be follow-up videos that show a lot more of the creative potential.

    That’s probably what I’m waiting for. The background harmony drones are a nice effect, and sound great in the @Gavinski demo a few posts above, but I quite like doing that bit myself with a synth or guitar. Plus it’s a relatively easy thing to do in building a track.

    Interested in hearing more complex sequenced/rhythmic/modulated stuff (if it can do that), though I reckon I’m missing the point of this app!

    I guess I’m trying to talk myself into buying it, as I really enjoy the devs UI/UX, but think this one probably isn’t for me. I haven’t got his sequencer yet, so might just grab that one instead.

    Sure it can do the rhythmic modulated stuff, it has all those LFOs and other mod sources built in. Mod the Tide level, for example, with a fast square lfo and you have interesting gating fx. Set that to a free rate and mod its rate with other modulators etc etc. The sky is the limit.

    Good to hear, need to see some examples though.

  • @Robin2 said:

    @ChimmyChungaFace said:
    I see some people saying this has a lot of depth, videos suggest otherwise. Reminds me of PaulXStretch: Kind of cool, everything ends up sounding similar. Hey, prove me wrong!

    As I’ve said in previous posts, I too am interested in finding other ways other than the obvious to use Coastline. Everyone’s budgets are different but £12 isn’t low enough for me for it to be a throwaway purchase unfortunately. I shall have to experiment to decide whether I’ll get real, repeated use out of it and, if not, I’m afraid I’ll have to request a refund. As such, I can understand why you might want to ask this.

    It seems owning Waymaker gives you the easiest way to do everything with it, but that’s another £15. I think everything can be done via external automation if you don’t have it but obviously that’s an extra bit of setting up.

    I asked about the two pitch values not being available for the internal modulators and it seems Aqeel sees Waymaker as the way for pitch related things so it’s deliberate that they’re not available. Fine and dandy if you own Waymaker but if not it’s a bit of a shame. I can understand the impulse to tie things into your own app ecosystem though.

    As to it sounding similar on everything, I’m still experimenting but I’d also be interested in hearing examples of the different things it can do. It may turn out to be that it only really does what it’s designed to do though - how dare it! - and it certainly does that superbly well.

    Honestly, from the demos I’ve skimmed… I kinda feel the same about this app and will pass on it for now.

    I know this is an excellent/innovative developer and I’m sure it’s a great app I’d get some interesting use out of, but at $12 it’s something I’ll likely hold off for a sale or bundle thing instead.

  • @skiphunt said:

    @Robin2 said:

    @ChimmyChungaFace said:
    I see some people saying this has a lot of depth, videos suggest otherwise. Reminds me of PaulXStretch: Kind of cool, everything ends up sounding similar. Hey, prove me wrong!

    As I’ve said in previous posts, I too am interested in finding other ways other than the obvious to use Coastline. Everyone’s budgets are different but £12 isn’t low enough for me for it to be a throwaway purchase unfortunately. I shall have to experiment to decide whether I’ll get real, repeated use out of it and, if not, I’m afraid I’ll have to request a refund. As such, I can understand why you might want to ask this.

    It seems owning Waymaker gives you the easiest way to do everything with it, but that’s another £15. I think everything can be done via external automation if you don’t have it but obviously that’s an extra bit of setting up.

    I asked about the two pitch values not being available for the internal modulators and it seems Aqeel sees Waymaker as the way for pitch related things so it’s deliberate that they’re not available. Fine and dandy if you own Waymaker but if not it’s a bit of a shame. I can understand the impulse to tie things into your own app ecosystem though.

    As to it sounding similar on everything, I’m still experimenting but I’d also be interested in hearing examples of the different things it can do. It may turn out to be that it only really does what it’s designed to do though - how dare it! - and it certainly does that superbly well.

    Honestly, from the demos I’ve skimmed… I kinda feel the same about this app and will pass on it for now.

    I know this is an excellent/innovative developer and I’m sure it’s a great app I’d get some interesting use out of, but at $12 it’s something I’ll likely hold off for a sale or bundle thing instead.

    I believe this is the sale (intro)

  • @Squishy said:

    @skiphunt said:

    @Robin2 said:

    @ChimmyChungaFace said:
    I see some people saying this has a lot of depth, videos suggest otherwise. Reminds me of PaulXStretch: Kind of cool, everything ends up sounding similar. Hey, prove me wrong!

    As I’ve said in previous posts, I too am interested in finding other ways other than the obvious to use Coastline. Everyone’s budgets are different but £12 isn’t low enough for me for it to be a throwaway purchase unfortunately. I shall have to experiment to decide whether I’ll get real, repeated use out of it and, if not, I’m afraid I’ll have to request a refund. As such, I can understand why you might want to ask this.

    It seems owning Waymaker gives you the easiest way to do everything with it, but that’s another £15. I think everything can be done via external automation if you don’t have it but obviously that’s an extra bit of setting up.

    I asked about the two pitch values not being available for the internal modulators and it seems Aqeel sees Waymaker as the way for pitch related things so it’s deliberate that they’re not available. Fine and dandy if you own Waymaker but if not it’s a bit of a shame. I can understand the impulse to tie things into your own app ecosystem though.

    As to it sounding similar on everything, I’m still experimenting but I’d also be interested in hearing examples of the different things it can do. It may turn out to be that it only really does what it’s designed to do though - how dare it! - and it certainly does that superbly well.

    Honestly, from the demos I’ve skimmed… I kinda feel the same about this app and will pass on it for now.

    I know this is an excellent/innovative developer and I’m sure it’s a great app I’d get some interesting use out of, but at $12 it’s something I’ll likely hold off for a sale or bundle thing instead.

    I believe this is the sale (intro)

    I think so, I think 15 is regular price

  • The visual change when Pause is pressed is a nice touch.

  • edited June 28

    @Squishy said:

    @skiphunt said:

    @Robin2 said:

    @ChimmyChungaFace said:
    I see some people saying this has a lot of depth, videos suggest otherwise. Reminds me of PaulXStretch: Kind of cool, everything ends up sounding similar. Hey, prove me wrong!

    As I’ve said in previous posts, I too am interested in finding other ways other than the obvious to use Coastline. Everyone’s budgets are different but £12 isn’t low enough for me for it to be a throwaway purchase unfortunately. I shall have to experiment to decide whether I’ll get real, repeated use out of it and, if not, I’m afraid I’ll have to request a refund. As such, I can understand why you might want to ask this.

    It seems owning Waymaker gives you the easiest way to do everything with it, but that’s another £15. I think everything can be done via external automation if you don’t have it but obviously that’s an extra bit of setting up.

    I asked about the two pitch values not being available for the internal modulators and it seems Aqeel sees Waymaker as the way for pitch related things so it’s deliberate that they’re not available. Fine and dandy if you own Waymaker but if not it’s a bit of a shame. I can understand the impulse to tie things into your own app ecosystem though.

    As to it sounding similar on everything, I’m still experimenting but I’d also be interested in hearing examples of the different things it can do. It may turn out to be that it only really does what it’s designed to do though - how dare it! - and it certainly does that superbly well.

    Honestly, from the demos I’ve skimmed… I kinda feel the same about this app and will pass on it for now.

    I know this is an excellent/innovative developer and I’m sure it’s a great app I’d get some interesting use out of, but at $12 it’s something I’ll likely hold off for a sale or bundle thing instead.

    I believe this is the sale (intro)

    Gotcha… will revisit maybe when there’s deep discount Black Friday sales then - thx

  • Adding one copy to a fairly simple project (Aum) really put the heat on i.e on the iPad. It gets worrisome warm. I did turn off the motion but it made no big difference. Anyone else noticed this (iPad M1 - - 26.5)

  • edited June 29

    Really have fallen for this one here.
    Sonically it’s just what I’m looking for and lets the imagination soar. After demoing it for some people through monitors; it just didn’t click with them. But…
    In my headphones I’ve put a lot of hours away with this. Thanks for something new Aqeel.

    All your stuff is inspiring, and I keep finding new intricacies in how to make the headphones sing with any noise I throw at it. Ie panning!

    Anyone who loves this experimental stuff in our small noise lover’s community that reside here at loopyforum, owe it to themselves to spend a twelver and get this new new.

    Either way tho I’m glad I jumped. Makes me smile when it swirls.

  • @Pxlhg said:
    Adding one copy to a fairly simple project (Aum) really put the heat on i.e on the iPad. It gets worrisome warm. I did turn off the motion but it made no big difference. Anyone else noticed this (iPad M1 - - 26.5)

    I noticed spikes when upping the feedback on the filter. iPad Pro 10.5

  • @Pxlhg said:
    Adding one copy to a fairly simple project (Aum) really put the heat on i.e on the iPad. It gets worrisome warm. I did turn off the motion but it made no big difference. Anyone else noticed this (iPad M1 - - 26.5)

    Same here. Really love the app, but yeah, it’s a heater. Strangely, no CPU stress.

  • @torrescampalans said:

    @Pxlhg said:
    Adding one copy to a fairly simple project (Aum) really put the heat on i.e on the iPad. It gets worrisome warm. I did turn off the motion but it made no big difference. Anyone else noticed this (iPad M1 - - 26.5)

    Same here. Really love the app, but yeah, it’s a heater. Strangely, no CPU stress.

    Yes, it definitely runs a bit hot, I've seen worse but it could be better in that regard, wonder whether that can be optimized

  • wimwim
    edited June 29

    @torrescampalans said:

    @Pxlhg said:
    Adding one copy to a fairly simple project (Aum) really put the heat on i.e on the iPad. It gets worrisome warm. I did turn off the motion but it made no big difference. Anyone else noticed this (iPad M1 - - 26.5)

    Same here. Really love the app, but yeah, it’s a heater. Strangely, no CPU stress.

    Probably there is a lot of CPU use, which is causing the OS to bring more and faster cores online. When you see a CPU meter, it's reporting the percent of available processing power at that time. The OS throttles back processing power when not needed to conserve battery and heat generation. You can actually get lower CPU use reported when the device is working harder, and vice-versa.

    The only way an app can cause heating is by making the processors work hard, but the CPU meter isn't particularly useful for showing that quantitatively.

  • To make “cpu” meters even less of an indicator, they often are only telling what % of the audio thread’s processing is being used. Some apps/plugins do a lot of processing that aren’t in the audio thread which is why, for instance, you can have a lot of AU that are idle in Loopy Pro (or AUM) using no DSP resources (so CPU is low) but still consuming considerable battery power.

    That’s probably not relevant here, but worth knowing when trying to decipher CPU usage.

  • wimwim
    edited June 30

    Good point about the non-DSP overhead. Sometimes when people report over-heating, developers have found the culprit elsewhere. Gadget was one of those if I remember correctly.

  • @wim said:

    @torrescampalans said:

    @Pxlhg said:
    Adding one copy to a fairly simple project (Aum) really put the heat on i.e on the iPad. It gets worrisome warm. I did turn off the motion but it made no big difference. Anyone else noticed this (iPad M1 - - 26.5)

    Same here. Really love the app, but yeah, it’s a heater. Strangely, no CPU stress.

    Probably there is a lot of CPU use, which is causing the OS to bring more and faster cores online. When you see a CPU meter, it's reporting the percent of available processing power at that time. The OS throttles back processing power when not needed to conserve battery and heat generation. You can actually get lower CPU use reported when the device is working harder, and vice-versa.

    The only way an app can cause heating is by making the processors work hard, but the CPU meter isn't particularly useful for showing that quantitatively.

    Thanks. So instructive


  • 6 short "jams"

  • Nice demo @eylvy 👍🏼

    (For those who feel like this is a one-trick pony, it's worth getting to the later parts of the video where less "default" sounds are explored.)

  • As I experiment more with it, it seems to me that it would be useful to have a sync mode (to increments of host tempo) for the Hold time and the Sustainer buffer size (and possibly the sustainer fade in/out times too).

    Before I suggest it, am I missing something as to why this wouldn’t be a helpful option?

  • @Robin2 said:
    As I experiment more with it, it seems to me that it would be useful to have a sync mode (to increments of host tempo) for the Hold time and the Sustainer buffer size (and possibly the sustainer fade in/out times too).

    Before I suggest it, am I missing something as to why this wouldn’t be a helpful option?

    That sounds like a good idea, surprised that, even though the plugin is geared at ambient etc, that's not an option.

  • @Robin2 said:
    As I experiment more with it, it seems to me that it would be useful to have a sync mode (to increments of host tempo) for the Hold time and the Sustainer buffer size (and possibly the sustainer fade in/out times too).

    Before I suggest it, am I missing something as to why this wouldn’t be a helpful option?

    I'm a little surprised too, especially since this exists in Ridgewalk and Weeping Wall. My guess is it'll come in an update.

    In the meantime, I think I'd use one or more of the LFOs - square + sync. There's also the step sequencer, which IMO is even more interesting.

  • Thanks @Gavinski and @wim, I’ll email Aqeel and ask if there’s any chance of it being added. Cheers.

Sign In or Register to comment.