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.

Audio Damage Enso

1202123252630

Comments

  • @espiegel123 said:
    @BroCoast and @zilld2017 : what hardware are you running on?

    2016 9.7" ipad pro.

    The only issue I really have is that I have to reload an instance to start over. If I clear the loop in Enso it does a crazy feedback loop.

    I can still run AUM to send audio from AB3 through an FX chain and back. The crashes only occur when Enso is hosted in AUM.

  • @wim said:
    Here’s a video showing how Enso can be used to reduce CPU utilization in quick jams. There are many, many other ways to accomplish the same thing, but I find this kind of handy...

    FWIW, Loopy HD is even better for this than Enso. I just did a session in AUM building 12 long loops swapping heavy CPU AUs (and the IAA CPU hog OdysseI for good measure) in and out on an iPad 6th Gen. CPU load when the AUs were ejected was about 26% with Bleass reverb running on a bus. This was a setup in which each Loopy track had its own channel in AUM.

    I wouldn’t be surprised if I could get even more tracks by also running the iPhone Loopy though I can’t imagine needing to.

  • Can’t argue with you there. Loopy is definitely more robust.

  • edited May 2019

    Here’s a video of the very repeatable issue with the record head stopping after changing record speed.

    Happened on Air2 and Air3, regardless of long recording on/off

  • @MonkeyDrummer said:
    Here’s a video of the very repeatable issue with the record head stopping after changing record speed.

    Happened on Air2 and Air3, regardless of long recording on/off

    Because you have Quantize on.

    Messing with the play and record speeds with Quantize on causes problems.

  • @BroCoast said:

    @MonkeyDrummer said:
    Here’s a video of the very repeatable issue with the record head stopping after changing record speed.

    Happened on Air2 and Air3, regardless of long recording on/off

    Because you have Quantize on.

    Messing with the play and record speeds with Quantize on causes problems.

    @BroCoast said:

    @MonkeyDrummer said:
    Here’s a video of the very repeatable issue with the record head stopping after changing record speed.

    Happened on Air2 and Air3, regardless of long recording on/off

    Because you have Quantize on.

    Messing with the play and record speeds with Quantize on causes problems.

    I don't recall reading that in the manual...

  • @MonkeyDrummer said:

    @BroCoast said:

    @MonkeyDrummer said:
    Here’s a video of the very repeatable issue with the record head stopping after changing record speed.

    Happened on Air2 and Air3, regardless of long recording on/off

    Because you have Quantize on.

    Messing with the play and record speeds with Quantize on causes problems.

    @BroCoast said:

    @MonkeyDrummer said:
    Here’s a video of the very repeatable issue with the record head stopping after changing record speed.

    Happened on Air2 and Air3, regardless of long recording on/off

    Because you have Quantize on.

    Messing with the play and record speeds with Quantize on causes problems.

    I don't recall reading that in the manual...

    No but you're experienced with iOS and know how buggy even the best apps are.

    It's the small downside to having cheap access to highly innovative music making tools. It's also not uncommon for apps to be abandoned because there is no possible way to fix all of the bugs that may cause users to request refunds and rage on forums. (I'm not saying you're doing that just to be clear :) )

  • Haha, what the hell? I had no idea Chris was the guy behind Sister Machine Gun. I had one of their albums when I was a young Wax Trax disciple. Guess he last released an
    album in 2015. Too weird.

  • @BroCoast said:

    Could it be hosting in AUM might be an issue?

    6 instances in AB3 at 128 samples. Won't crash :)

    Just to follow up on this, I've done a little more testing with non Audio Damage AU and AUM.

    In Audiobus I can pile on AU until it's a crackling mess. I can make adjustments in the AU windows and it won't crash.

    In AUM I can load up the same amount, bring it to a crackling mess but as soon as a I adjust anything in the AU windows or in some cases even bring them up = crash.

    It's clearly an AUM issue.

  • @BroCoast said:

    It's clearly an AUM issue.

    I can second that. Runs well in Apematrix with 4 instances, with an occasional freeze when quitting the app but never while in use.

  • edited May 2019

    Maybe noob question but:

    Is there any way to x-fade start-end looping points to avoid clicking?

    Actually quite buggy even when i use only one instance. AUM/iPad Pro 10.5 2017.

  • @frthcomingstorm said:
    Maybe noob question but:

    Is there any way to x-fade start-end looping points to avoid clicking?

    Actually quite buggy even when i use only one instance. AUM/iPad Pro 10.5 2017.

    sadly, no way to guarantee smooth loop transitions at the moment.

  • @frthcomingstorm said:
    Maybe noob question but:

    Is there any way to x-fade start-end looping points to avoid clicking?

    Actually quite buggy even when i use only one instance. AUM/iPad Pro 10.5 2017.

    A workaround I’ve found for the click is to set the trigger to overdub straight out of recording the first loop. That way it continues to record the tail of the last note/chord and it doesn’t have that click. Triggering again will then put it in play mode. A cross fade would still be a better solution, but this has worked pretty well for me.

  • @zilld2017 said:

    @BroCoast said:

    It's clearly an AUM issue.

    I can second that. Runs well in Apematrix with 4 instances, with an occasional freeze when quitting the app but never while in use.

    If so, then probably a good idea to tag @j_liljedahl unless he has been informed of this issue.

    @SquareKid thanks for the tip! It sounds so obvious when you state it like that:)

  • Unfortunately I can't reproduce this. I'm stacking a lot of Enso's here but it runs smooth and without crackles at 64 frame buffer size on my iPad Pro 1st gen.

  • @j_liljedahl said:
    Unfortunately I can't reproduce this. I'm stacking a lot of Enso's here but it runs smooth and without crackles at 64 frame buffer size on my iPad Pro 1st gen.

    Are all those instances actually full of recorded loops though? If they were and you interacted with the AU window... It would crash!

  • edited May 2019

    ED oops, I was talking about Quanta :s
    Im really enjoying this update.
    Going to do an app store review, I think the AD guys deserve it.

  • @BroCoast said:

    @j_liljedahl said:
    Unfortunately I can't reproduce this. I'm stacking a lot of Enso's here but it runs smooth and without crackles at 64 frame buffer size on my iPad Pro 1st gen.

    Are all those instances actually full of recorded loops though? If they were and you interacted with the AU window... It would crash!

    Yup... for shits and giggles I tried it. Red Cross hatching of death all around...

  • Fun to play the sectors on this:

  • Does anyone know how to map a controller knob to the Feedback or sector settings? I know he mentioned that on/off buttons work best for midi but I’m looking to change those values over time. Would like to turn the feedback up or down with a knob without reaching all the way over to the iPad screen! 😅

  • edited June 2019

    @sketcherazzi

    It's not in the list inside the app for CC# but it is available in the list of parameters.

  • Ah, thanks - I was looking so hard for it in the app settings that I forgot to check AUM’s settings - thanks again!

  • edited July 2019
    The user and all related content has been deleted.
  • @BroCoast said:

    @BroCoast said:

    Could it be hosting in AUM might be an issue?

    6 instances in AB3 at 128 samples. Won't crash :)

    Just to follow up on this, I've done a little more testing with non Audio Damage AU and AUM.

    In Audiobus I can pile on AU until it's a crackling mess. I can make adjustments in the AU windows and it won't crash.

    In AUM I can load up the same amount, bring it to a crackling mess but as soon as a I adjust anything in the AU windows or in some cases even bring them up = crash.

    It's clearly an AUM issue.

    Interesting, so is enso stable in another hosts? I had terrible issues with AD Quanta and developer took a year to fix most of them. Even now it doesn't work correctly for me so I'm very dubious about buying AD apps now.

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

    @EyeOhEss said:
    Where are recorded Enso audio files stored after I save with buffer? Can’t see an Enso folder in Files?

    Bumpety bump.

    Have you checked the manual? If I recall,you have to export the buffer for use in other apps.

  • The user and all related content has been deleted.
  • I really need to read the Enso manual. No joke, so few buttons, beautiful... Yet I'm always clicking everything like a doofus and praying it does what I think it's going to do. Still not sure how to get the layers working. It's my fault. RTFM, right?

  • The manual is great.

    Also, AD made a very good video walkthrough on their YouTube channel. 40 minutes, but very informative and well done.

  • The user and all related content has been deleted.
Sign In or Register to comment.