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.

AUM 1.4.6 is out!

12346»

Comments

  • @Samu said:
    AUM Search works fine under iPadOS18.5...

    Good. Do you see the list option to sort by Last Used? On loading AUM, do you see the option to restore Last State?

  • @uncledave said:

    @Samu said:
    AUM Search works fine under iPadOS18.5...

    Good. Do you see the list option to sort by Last Used? On loading AUM, do you see the option to restore Last State?

    No "Last State" seen here. Ipad Pro 12.9" 2nd Gen. iPadOS 17.7.7.

    "Last State" is visible on iPad Air 3rd Gen iPadOS 18.5

  • @uncledave said:

    @Samu said:
    AUM Search works fine under iPadOS18.5...

    Good. Do you see the list option to sort by Last Used? On loading AUM, do you see the option to restore Last State?


    Yeah, I'm usually pretty vocal when sh*t breaks down for me and so far it's been very smooth ride with 18.5...

  • @uncledave @Samu @toneman88 Thanks for checking this out.. seems iPadOS 17.7.7 has done something to the normally faultless AUM..
    I just sent an email..

  • @royor said:
    @uncledave @Samu @toneman88 Thanks for checking this out.. seems iPadOS 17.7.7 has done something to the normally faultless AUM..
    I just sent an email..

    If your device can handle it 18.5 is pretty neat...

  • @Samu sadly it can’t.. patiently waiting to update to a newer, faster, more powerful iPad.. soon..

  • There are a lot of people saying that 17.7.7 had critical bugs that cause a lot of problems

  • @royor said:
    @uncledave @Samu @toneman88 Thanks for checking this out.. seems iPadOS 17.7.7 has done something to the normally faultless AUM..
    I just sent an email..

    Sorry to hear that. Indeed, it seems iPadOS 17.7.7 broke something with NSUserDefaults. I would expect you see issues in other apps as well that uses this to store user settings etc? Hopefully Apple releases a fix soon.

    Does "Restore Previous State" still work from the FILES menu?

    Unfortunately I have no way of testing iPadOS 17.x, my newer devices are on 18.x already and my older is stuck on 12.x and 16.x.

  • @j_liljedahl said:

    @royor said:
    @uncledave @Samu @toneman88 Thanks for checking this out.. seems iPadOS 17.7.7 has done something to the normally faultless AUM..
    I just sent an email..

    Sorry to hear that. Indeed, it seems iPadOS 17.7.7 broke something with NSUserDefaults. I would expect you see issues in other apps as well that uses this to store user settings etc? Hopefully Apple releases a fix soon.

    Does "Restore Previous State" still work from the FILES menu?

    Unfortunately I have no way of testing iPadOS 17.x, my newer devices are on 18.x already and my older is stuck on 12.x and 16.x.

    Update: Yes, known problem with 17.7.7, not related to AUM in any way: https://discussions.apple.com/thread/256060025?sortBy=rank

  • @j_liljedahl Yes, "Restore Previous State" still works from the FILES menu.. I never even noticed that option before..

    I don’t know why I rushed into this Apple update.. normally I do wait for a while to see if issues pop up.. thanks for checking into all this..

    Oh Apple dear Apple.. can we please stop breaking shit..

  • Ironically 17.7.7 was supposedly only needed to plug some extremely serious security issues related to AirPlay and CarPlay. Absolutely a critical update.

    I can kind of see how they managed to hose up NSUserDefaults as the issues were centered on sloppy parsing of Plist files. I'm kind of surprised they didn't break it in iOS 18 as well, but maybe they took more care there as it's the current version they prefer everyone to be on.

  • @wim said:
    Ironically 17.7.7 was supposedly only needed to plug some extremely serious security issues related to AirPlay and CarPlay. Absolutely a critical update.

    I can kind of see how they managed to hose up NSUserDefaults as the issues were centered on sloppy parsing of Plist files. I'm kind of surprised they didn't break it in iOS 18 as well, but maybe they took more care there as it's the current version they prefer everyone to be on.

    Yeah, I'm amazed how they can let something like this slip through testing.

  • @j_liljedahl said:

    @wim said:
    Ironically 17.7.7 was supposedly only needed to plug some extremely serious security issues related to AirPlay and CarPlay. Absolutely a critical update.

    I can kind of see how they managed to hose up NSUserDefaults as the issues were centered on sloppy parsing of Plist files. I'm kind of surprised they didn't break it in iOS 18 as well, but maybe they took more care there as it's the current version they prefer everyone to be on.

    Yeah, I'm amazed how they can let something like this slip through testing.

    Given the urgency of that needed fix, I can kind of understand (though not excuse).

    The real mind flogger is the incredible laxness that lay behind the issue. Not type checking core variables, and that in an over the air protocol?!

  • @wim said:
    Ironically 17.7.7 was supposedly only needed to plug some extremely serious security issues related to AirPlay and CarPlay. Absolutely a critical update.

    I can kind of see how they managed to hose up NSUserDefaults as the issues were centered on sloppy parsing of Plist files. I'm kind of surprised they didn't break it in iOS 18 as well, but maybe they took more care there as it's the current version they prefer everyone to be on.

    Actually, the AirPlay fixes were included in iPadOS 18.3, released Jan. 27, and iPadOS 17.7.6, released March 31. The reported problem features in AUM are working fine with iPadOS 17.7.6. iPadOS 18.5 and 17.7.7 contain a bunch of other fixes, not related to AirPlay.

  • @uncledave said:

    @wim said:
    Ironically 17.7.7 was supposedly only needed to plug some extremely serious security issues related to AirPlay and CarPlay. Absolutely a critical update.

    I can kind of see how they managed to hose up NSUserDefaults as the issues were centered on sloppy parsing of Plist files. I'm kind of surprised they didn't break it in iOS 18 as well, but maybe they took more care there as it's the current version they prefer everyone to be on.

    Actually, the AirPlay fixes were included in iPadOS 18.3, released Jan. 27, and iPadOS 17.7.6, released March 31. The reported problem features in AUM are working fine with iPadOS 17.7.6. iPadOS 18.5 and 17.7.7 contain a bunch of other fixes, not related to AirPlay.

    Interesting. Thanks.

  • Ok, I guess clock sync from midi input is something that will never happen at this point 😞

Sign In or Register to comment.