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.

RE-1 Virtual Tape Machine & Looper - Amazing for Dub

1679111214

Comments

  • @skiphunt said:

    @kinkujin said:
    Quick question - why do animations stop sometimes? Is there something I'm missing? I'm not asking because I need the spinning animations (though it is cool!) just wondering if I'm missing some setting or if when it's stopped something else has been reset? [using iPad Pro 12.9, in ApeMatrix]
    Thanks!

    That’s a buggy behavior. It was doing it more in earlier builds but got much better before launch. Sometimes just closing the AU window and reopening gets the spinning going again.

    I haven’t seen them stop at all in the latest beta builds though. Getting more and more solid.

    Thanks, i sort of figured.

  • edited August 2018

    @MonzoPro said:
    Is the heat/cpu issue completely sorted now?

    5 posts up 👆🏼
    or 7 if yr not quick enough at typing ;-)

  • @skiphunt said:

    @kinkujin said:
    Quick question - why do animations stop sometimes? Is there something I'm missing? I'm not asking because I need the spinning animations (though it is cool!) just wondering if I'm missing some setting or if when it's stopped something else has been reset? [using iPad Pro 12.9, in ApeMatrix]
    Thanks!

    That’s a buggy behavior. It was doing it more in earlier builds but got much better before launch. Sometimes just closing the AU window and reopening gets the spinning going again.

    I haven’t seen them stop at all in the latest beta builds though. Getting more and more solid.

    For those who haven’t bought it yet, and aren’t scared of the occasional bug that gets squashed reasonably quickly... only a couple days left of the launch sale. And the betas are already universal :)

    Are we able to buy it from our iPhones yet?

  • @kinkujin said:

    @skiphunt said:

    @kinkujin said:
    Quick question - why do animations stop sometimes? Is there something I'm missing? I'm not asking because I need the spinning animations (though it is cool!) just wondering if I'm missing some setting or if when it's stopped something else has been reset? [using iPad Pro 12.9, in ApeMatrix]
    Thanks!

    That’s a buggy behavior. It was doing it more in earlier builds but got much better before launch. Sometimes just closing the AU window and reopening gets the spinning going again.

    I haven’t seen them stop at all in the latest beta builds though. Getting more and more solid.

    Thanks, i sort of figured.

    could be because you have ‘link to transport’ selected.. in which case it stops n starts when yr host stops n starts..
    or, as mr hunt says, could be residual bug.. i usually saw this when i put the app into the background.. though it wasn’t predictable... haven’t seen it yet in newest beta..

  • @Audiojunkie said:

    @skiphunt said:

    @kinkujin said:
    Quick question - why do animations stop sometimes? Is there something I'm missing? I'm not asking because I need the spinning animations (though it is cool!) just wondering if I'm missing some setting or if when it's stopped something else has been reset? [using iPad Pro 12.9, in ApeMatrix]
    Thanks!

    That’s a buggy behavior. It was doing it more in earlier builds but got much better before launch. Sometimes just closing the AU window and reopening gets the spinning going again.

    I haven’t seen them stop at all in the latest beta builds though. Getting more and more solid.

    For those who haven’t bought it yet, and aren’t scared of the occasional bug that gets squashed reasonably quickly... only a couple days left of the launch sale. And the betas are already universal :)

    Are we able to buy it from our iPhones yet?

    I don't think so... since it's not officially universal yet. And whether or not it'll be officially universal before the launch sale ends... only the dev knows. The latest beta build works as universal, but I don't know how much more tweaking and testing it needs for small screen scaling, etc. before he releases it. I would guess not, but who knows? He's made great leaps in tweaking/bug squashing in very short periods of time before... but I couldn't say for sure if it'll be ready for iPhone use before the sale ends.

    Best to ask the dev.

  • The user and all related content has been deleted.
  • @RockySmalls said:

    @MonzoPro said:
    Is the heat/cpu issue completely sorted now?

    5 posts up 👆🏼
    or 7 if yr not quick enough at typing ;-)

    Ah ok, great!

    Is it fixed in the current release, or just the beta?

    Looks like I need to make a decision as the offer ends soon.

  • tt> @MonzoPro said:

    @RockySmalls said:

    @MonzoPro said:
    Is the heat/cpu issue completely sorted now?

    5 posts up 👆🏼
    or 7 if yr not quick enough at typing ;-)

    Ah ok, great!

    Is it fixed in the current release, or just the beta?

    Looks like I need to make a decision as the offer ends soon.

    yeah, the optimisations for the heat stuff / automations are in the current beta 1.02 and the version in the store is 1.01 ..
    so you would have to take a punt and maybe wait a few more days for it to be all ‘cool’
    I haven’t found any issues yet with new beta but then i am only testing it in cubasis and as stand alone... I don’t have an iphone so the ‘universality’ testing is a distant land to me.

  • edited August 2018

    I’ve found the saturation quite harsh on the ears and lacking warmth, was this in the design? Very low levels of the effect cause harsh harmonics. I’m digging the app apart from this one aspect.

  • I just noticed that when you save your loops in RE-1 that it saves them as 32-bit files. Does anyone know of a trick to get them to save at 16 or 24 bit instead?

  • @espiegel123 said:
    I just noticed that when you save your loops in RE-1 that it saves them as 32-bit files. Does anyone know of a trick to get them to save at 16 or 24 bit instead?

    Fixed in beta. Now saves 2chan 24bit

  • edited August 2018

    @skiphunt said:

    @espiegel123 said:
    I just noticed that when you save your loops in RE-1 that it saves them as 32-bit files. Does anyone know of a trick to get them to save at 16 or 24 bit instead?

    Fixed in beta. Now saves 2chan 24bit

    @ka010 Please can the 32bit save be left as an option. Makes sense when recording sometime out of control volume swells. Can always bring back an above 0 dB audio file in post.

  • edited August 2018

    I think I’m going to stop commenting on anything related to the beta. It's kind of awkward, likely inappropriate, and it ultimately just muddies the waters.

    Just one final comment though... this dev is obsessively working to forge this into a rock solid app that incorporate most of the requested features that make sense. The beta updates are coming regularly and the dev is most certainly on the case and committed to making this app as near to perfect as he can.

  • @kinkujin said:

    @skiphunt said:

    @kinkujin said:
    Quick question - why do animations stop sometimes? Is there something I'm missing? I'm not asking because I need the spinning animations (though it is cool!) just wondering if I'm missing some setting or if when it's stopped something else has been reset? [using iPad Pro 12.9, in ApeMatrix]
    Thanks!

    That’s a buggy behavior. It was doing it more in earlier builds but got much better before launch. Sometimes just closing the AU window and reopening gets the spinning going again.

    I haven’t seen them stop at all in the latest beta builds though. Getting more and more solid.

    Thanks, i sort of figured.

    That was just a visual glitch, audio processing should not have been affected. It's fixed with the new animations though.

    @[Deleted User] said:
    I’ve found the saturation quite harsh on the ears and lacking warmth, was this in the design? Very low levels of the effect cause harsh harmonics. I’m digging the app apart from this one aspect.

    It can get quite harsh rather fast, opinions vary though most seems to like it the way it works at the moment.

    @[Deleted User] said:

    @skiphunt said:

    @espiegel123 said:
    I just noticed that when you save your loops in RE-1 that it saves them as 32-bit files. Does anyone know of a trick to get them to save at 16 or 24 bit instead?

    Fixed in beta. Now saves 2chan 24bit

    @ka010 Please can the 32bit save be left as an option. Makes sense when recording sometime out of control volume swells. Can always bring back an above 0 dB audio file in post.

    It's still 32bit actually but 2ch instead of just one like it was originally. That said, I've been meaning to add an export dialogue do allow for some options like setting bitdepth or applying a crossfade. Currently thats It's on my list for the 1.1 update.

  • Also, +1 for weird cat shirts :smile:

  • The user and all related content has been deleted.
  • @[Deleted User] said:
    I’ve found the saturation quite harsh on the ears and lacking warmth, was this in the design? Very low levels of the effect cause harsh harmonics. I’m digging the app apart from this one aspect.

    It can get quite harsh rather fast, opinions vary though most seems to like it the way it works at the moment.

    @[Deleted User] said:

    @skiphunt said:

    @espiegel123 said:
    I just noticed that when you save your loops in RE-1 that it saves them as 32-bit files. Does anyone know of a trick to get them to save at 16 or 24 bit instead?

    Fixed in beta. Now saves 2chan 24bit

    @ka010 Please can the 32bit save be left as an option. Makes sense when recording sometime out of control volume swells. Can always bring back an above 0 dB audio file in post.

    It's still 32bit actually but 2ch instead of just one like it was originally. That said, I've been meaning to add an export dialogue do allow for some options like setting bitdepth or applying a crossfade. Currently thats It's on my list for the 1.1 update.

    Thanks for the intel :-) I do like the app.
    Maybe in a far off future update a less distortion like saturation switch could be added to this parameter.

    Thanks for listening.

  • @ka010 said:
    Also, +1 for weird cat shirts :smile:

    LOL :)

  • Been having a lot of fun with this. Haven't done much 'deep tweaking' yet but the sounds I've gotten running the Moog Model D app through it as an effect are fantastic. Will be exploring looping more deeply in a bit today.

  • loving this app so far, but getting lots of crackles, even in low cpu usage. like under 50. need to figure out this crackle thing. sometimes it seems it's the actual re-1. have only tried it in aum so far.

    anyways, plugged my prophet in last night and looped a little, going through some presets i had saved. thing sounds amazing.

  • Lots of crackles on my 2018 iPad, too, with rather low CPU according to AUM. I consider asking for a refund for this one, which would be a first time for me.

  • @bleep said:
    Lots of crackles on my 2018 iPad, too, with rather low CPU according to AUM. I consider asking for a refund for this one, which would be a first time for me.

    well, I'm not sure where the issue lies. because I can have some pretty intense gadget sessions and intense mixing sessions in auria with no crackle. I guess problem arises because I bring buffer to 128 if I'm playing in so the lag doesn't throw me off. but again, didn't even reach 50% on this video. and I was getting the crackle without the screen recorder as well

  • edited September 2018

    I had a problem at first with CPU use (which seemed to build over time) but after adding/removing some different apps and doing a bit of tweaking, had a setup running between 78-92% for 4-5 hours with very little crackling (and that was only from GUI interaction). After that, did a bit of trimming to get me to into the sub 50 range (including Moog Model D, Sugar Bytes WOW and 2x RE-1) and ran for 6+ hours without an issue. Definitely more processor hungry than Kosmonaut though.

    EDIT: Air2 at 512/2 frame buffer, iCA4+ (this gives me a realtime latency which is acceptable for performance)

  • FWIW: in 3 months of testing on iPad Pro 10.5, I've never had any crackling at all. Mostly use apeMatrix, but sometimes AUM as well.

    There's a new version 1.1 that should be dropping soon. Jus' sayin...

    But, do what ya gotta do.

  • The beta versions have seen a STEEP improvement in processor efficiency for me. Hopefully it will continue to improve in that regard but it's already to a level that I'd perform with it. I've never had a crash with the app with any version either (we're not talking about that right now but it came to mind while I was typing!)

  • @OscarSouth said:

    EDIT: Air2 at 512/2 frame buffer, iCA4+ (this gives me a realtime latency which is acceptable for performance)

    before digging in I think this is the main issue, buffer. I can't deal with 512 if I'm playing guitar or keys. I constantly fixate on the late attack and it takes me out of the moment. m I can try 256 but have been pushing 128, which is what I was used to in the computer world..

    just checked and gadget on my phone is 512, but I never record real instruments, just a bit with my korg nanokeys studio. and then usually slide notes or quantize. but I don't feel too much lag there.

  • @vpich said:

    @OscarSouth said:

    EDIT: Air2 at 512/2 frame buffer, iCA4+ (this gives me a realtime latency which is acceptable for performance)

    before digging in I think this is the main issue, buffer. I can't deal with 512 if I'm playing guitar or keys. I constantly fixate on the late attack and it takes me out of the moment. m I can try 256 but have been pushing 128, which is what I was used to in the computer world..

    just checked and gadget on my phone is 512, but I never record real instruments, just a bit with my korg nanokeys studio. and then usually slide notes or quantize. but I don't feel too much lag there.

    512 on iOS software is atrociously delayed and un-usable, but 512 with an iCA4+ and hardware frame buffer of 2 is really pretty quick -- pretty much un-noticeable with a MIDI controller and not enough to be a problem with a live instrument (such as guitar) or vocals. We perform with these settings.

  • @OscarSouth said:

    @vpich said:

    @OscarSouth said:

    EDIT: Air2 at 512/2 frame buffer, iCA4+ (this gives me a realtime latency which is acceptable for performance)

    before digging in I think this is the main issue, buffer. I can't deal with 512 if I'm playing guitar or keys. I constantly fixate on the late attack and it takes me out of the moment. m I can try 256 but have been pushing 128, which is what I was used to in the computer world..

    just checked and gadget on my phone is 512, but I never record real instruments, just a bit with my korg nanokeys studio. and then usually slide notes or quantize. but I don't feel too much lag there.

    512 on iOS software is atrociously delayed and un-usable, but 512 with an iCA4+ and hardware frame buffer of 2 is really pretty quick -- pretty much un-noticeable with a MIDI controller and not enough to be a problem with a live instrument (such as guitar) or vocals. We perform with these settings.

    hmmm. I had a ca4+ and hated dealing with it, user error most likely but I totally killed my vibe when I would want to use it. never thought that latency buffer issues would be different depending on the device used (I use the zoom u-44).

  • @vpich said:

    @OscarSouth said:

    EDIT: Air2 at 512/2 frame buffer, iCA4+ (this gives me a realtime latency which is acceptable for performance)

    before digging in I think this is the main issue, buffer. I can't deal with 512 if I'm playing guitar or keys. I constantly fixate on the late attack and it takes me out of the moment. m I can try 256 but have been pushing 128, which is what I was used to in the computer world..

    just checked and gadget on my phone is 512, but I never record real instruments, just a bit with my korg nanokeys studio. and then usually slide notes or quantize. but I don't feel too much lag there.

    When recording just on the iPad 128 is required .... 256 max. Playback you can raise it to 512.

  • @vpich said:

    @OscarSouth said:

    @vpich said:

    @OscarSouth said:

    EDIT: Air2 at 512/2 frame buffer, iCA4+ (this gives me a realtime latency which is acceptable for performance)

    before digging in I think this is the main issue, buffer. I can't deal with 512 if I'm playing guitar or keys. I constantly fixate on the late attack and it takes me out of the moment. m I can try 256 but have been pushing 128, which is what I was used to in the computer world..

    just checked and gadget on my phone is 512, but I never record real instruments, just a bit with my korg nanokeys studio. and then usually slide notes or quantize. but I don't feel too much lag there.

    512 on iOS software is atrociously delayed and un-usable, but 512 with an iCA4+ and hardware frame buffer of 2 is really pretty quick -- pretty much un-noticeable with a MIDI controller and not enough to be a problem with a live instrument (such as guitar) or vocals. We perform with these settings.

    hmmm. I had a ca4+ and hated dealing with it, user error most likely but I totally killed my vibe when I would want to use it. never thought that latency buffer issues would be different depending on the device used (I use the zoom u-44).

    The enormity of the difference shocked and pleased me.

Sign In or Register to comment.