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.

OT: Cellular+iPad chatter split off from iOS 12.4 bug PSA

Comments

  • SamuSamu

    @rs2000 said:

    @Michael said:
    For those technically minded: the problem is that iOS is incorrectly refusing record permissions to the output app, until it is manually brought to the foreground. Even then, the audio system of the output app will only start working if the app starts its audio engine on UIApplicationDidBecomeActiveNotification. Some apps do this on UIApplicationWillEnterForegroundNotification (including Loopy), and this seems to experience the same problem.

    Reporting this to Apple now and having a think about how I can work around the problem from my end: probably by requiring manual "Tap to launch" of all output apps, so that they launch into the foreground.

    Stand by.

    Apple should really stop treating an iPad like an iPhone.
    On the iPhone, security is very important and I welcome such decisions.
    On the iPad, we want the opposite: Freedom for apps we choose to trust. :D

    Yeah, and the Phone.app would be a very welcome addition at least on the iPads that have cellular connectivity ;)

  • rs2000rs2000

    @Samu said:

    @rs2000 said:

    @Michael said:
    For those technically minded: the problem is that iOS is incorrectly refusing record permissions to the output app, until it is manually brought to the foreground. Even then, the audio system of the output app will only start working if the app starts its audio engine on UIApplicationDidBecomeActiveNotification. Some apps do this on UIApplicationWillEnterForegroundNotification (including Loopy), and this seems to experience the same problem.

    Reporting this to Apple now and having a think about how I can work around the problem from my end: probably by requiring manual "Tap to launch" of all output apps, so that they launch into the foreground.

    Stand by.

    Apple should really stop treating an iPad like an iPhone.
    On the iPhone, security is very important and I welcome such decisions.
    On the iPad, we want the opposite: Freedom for apps we choose to trust. :D

    Yeah, and the Phone.app would be a very welcome addition at least on the iPads that have cellular connectivity ;)

    Good point. Who wants a second mobile contract just to feed the iPad's SIM slot? ;)

  • SamuSamu

    @rs2000 said:

    Good point. Who wants a second mobile contract just to feed the iPad's SIM slot? ;)

    No need for second contract, just an additional SIM to the existing contract ;)

    This is the only way to overcome the current limitation of 200MB per App when not using Wifi and use the other device as a wifi-hotspot.

  • MichaelMichael

    Split this OT discussion off from original thread (@rs2000, @Samu)

  • rs2000rs2000

    @Michael said:
    Split this OT discussion off from original thread (@rs2000, @Samu)

    Oh, sorry for that.

  • MichaelMichael

    NP!

Sign In or Register to comment.

© Vanilla Keystone Theme 2024