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.

miRack - vcvRack on iOS

2»

Comments

  • espiegel123espiegel123

    @EyeOhEss said:

    @espiegel123 said:

    @EyeOhEss said:

    @espiegel123 said:

    @syrupcore said:

    @cian said:
    Audiobus isn't going anywhere, so it could be fine.

    I don't understand this. Does this mean an app could not be written as an AUv3 and still work in AudioBus for connecting audio to other apps? I though AB was forced to use IAA APIs (which is going away) for this?

    IAA isn't going away any time terribly soon so no big deal but still curious to understand if there will still be another AB enabled method for app-to-app audio (other than AUv3).

    Michael has explained that when IAA goes away (which could well be years from now) that he will find a way to replace IAA so that AB will continue to work

    Why would Apple allow a ‘new’ IAA alternative, after they nuke the old one? If they’re hell bent on AU then this wouldn’t make any sense?

    I will leave it at this: there is no iOS audio developer more knowledgeable than @Michael. If he expresses confidence that he will be able to implement Audiobus without IAA, I would be inclined to believe him. Michael knows his stuff.

    Yep, Michael is great. But equally, Apple can be difficult/unpredictable as hell ;)

    All I can say is this. Michael would not have spoken with such confidence if there wasn't something to it. He has a lot of experience including dealing with Apple and has been at this a long time -- since well before IAA even existed.

  • [Deleted User][Deleted User]
    edited June 2019
    The user and all related content has been deleted.
  • david_2017david_2017

    My guess is that he would eventually develop some sort of his own connectivity thingy (e.g. hundred of lines of codes), which other devs can insert in their apps and will enable them to communicate with AB4 (will it be by now then ;)). This wa its completely indipendent of apple - except apple will not allow such „inner communications systems“

    Whatever @michael is the pro :)

    @espiegel123 said:

    @EyeOhEss said:

    @espiegel123 said:

    @EyeOhEss said:

    @espiegel123 said:

    @syrupcore said:

    @cian said:
    Audiobus isn't going anywhere, so it could be fine.

    I don't understand this. Does this mean an app could not be written as an AUv3 and still work in AudioBus for connecting audio to other apps? I though AB was forced to use IAA APIs (which is going away) for this?

    IAA isn't going away any time terribly soon so no big deal but still curious to understand if there will still be another AB enabled method for app-to-app audio (other than AUv3).

    Michael has explained that when IAA goes away (which could well be years from now) that he will find a way to replace IAA so that AB will continue to work

    Why would Apple allow a ‘new’ IAA alternative, after they nuke the old one? If they’re hell bent on AU then this wouldn’t make any sense?

    I will leave it at this: there is no iOS audio developer more knowledgeable than @Michael. If he expresses confidence that he will be able to implement Audiobus without IAA, I would be inclined to believe him. Michael knows his stuff.

    Yep, Michael is great. But equally, Apple can be difficult/unpredictable as hell ;)

    All I can say is this. Michael would not have spoken with such confidence if there wasn't something to it. He has a lot of experience including dealing with Apple and has been at this a long time -- since well before IAA even existed.

  • [Deleted User][Deleted User]
    edited June 2019
    The user and all related content has been deleted.
  • icsleepersicsleepers

    AB existed before IAA - He’s already said if there’s interest he will go back to developing the SDK/API for other devs to use should they choose to implement in their apps (like how it originally was). It’s really no different than how Link works, or before that WIST, etc etc, and not really anything Apple would care about, or should..

  • [Deleted User][Deleted User]
    edited June 2019
    The user and all related content has been deleted.
  • CarnbotCarnbot

    @EyeOhEss said:

    @icsleepers said:
    AB existed before IAA - He’s already said if there’s interest he will go back to developing the SDK/API for other devs to use should they choose to implement in their apps (like how it originally was). It’s really no different than how Link works, or before that WIST, etc etc, and not really anything Apple would care about, or should..

    Just all very backwards from a user POV :( Apple should definitely care about the same hole repeatedly having to be plugged by outside devs. First time around because the solution didn’t exist. 2nd because they removed it. Not very impressive....

    I think that overall, it makes sense to remove IAA as an official plugin, it needs too much support from developers and they want to promote the better format of AUv3 which most people will prefer and use over any alternative. It's also very confusing for new users. But I don't see why they'll mind if there's a "backdoor" for old apps to use.

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • CarnbotCarnbot

    @EyeOhEss said:

    @Carnbot said:

    @EyeOhEss said:

    @icsleepers said:
    AB existed before IAA - He’s already said if there’s interest he will go back to developing the SDK/API for other devs to use should they choose to implement in their apps (like how it originally was). It’s really no different than how Link works, or before that WIST, etc etc, and not really anything Apple would care about, or should..

    Just all very backwards from a user POV :( Apple should definitely care about the same hole repeatedly having to be plugged by outside devs. First time around because the solution didn’t exist. 2nd because they removed it. Not very impressive....

    I think that overall, it makes sense to remove IAA as an official plugin, it needs too much support from developers and they want to promote the better format of AUv3 which most people will prefer and use over any alternative. It's also very confusing for new users. But I don't see why they'll mind if there's a "backdoor" for old apps to use.

    Either way, in the meantime apps like this aren’t going to have audio connectivity (assuming it isn’t AU) because they aren’t allowed to use IAA in new app submissions and there’s no replacement. It’s a pretty amateur state of affairs really...

    Yeah I know what you mean :). But there's nothing stopping someone making an AU version of this or using it like a hardware module and plugging it into another ipad/desktop.

  • bobbfettbobbfett

    Helooo
    Does anyone know if it is in the pipeline for sound card support, I would love to be able to use my expert sleepers es-8 with mirack on my iPad, what an awsome rig it would be.
    Bobb

  • espiegel123espiegel123

    @bobbfett said:
    Helooo
    Does anyone know if it is in the pipeline for sound card support, I would love to be able to use my expert sleepers es-8 with mirack on my iPad, what an awsome rig it would be.
    Bobb

    I believe so. But don't know where it is on the priority list.

Sign In or Register to comment.