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.

IAA Apps are fine.

13»

Comments

  • @ecou said:

    @espiegel123 said:

    @ecou said:
    Personally,I do not care to invest time and money in app (and IAP) that could stop working at anytime. Yes dev can abandon AU as much as IAA but less likely. In IAA case the cutoff could come from Apple, the DAW dev or the app dev.

    For me, there are IAA apps important enough to me that I'll freeze my current iPad to use them and get another for non-IAA.

    At what point you joined the game makes a big difference in this debate. I joined the game in 2017. AU was very popular at that point. As soon as I understood the difference I stopped buying IAA. For reference I am not a jammer, I don’t use AUM.

    I think it is less a matter of when you started (I started doing iOS music in 2018) as what apps you love. I have plenty of AU that I love and there are some IAA apps that were popular (and now) that are just amazing instruments that I gel with and for which I don't PERSONALLY find a satisfying replacement.

    Different people have different preferences -- which is cool. It just bugs me when people act is if people that don't have their preference are somehow objectively wrong -- or that the apps they don't like should be shunned. I rarely see people with IAA faves saying "don't use AU" but there plenty of people that are AUv3 purists (again: totally fine if that is their preference) who feel the need to be dismissive of IAA apps and discourage people from using them.

  • @espiegel123 said:
    who feel the need to be dismissive of IAA apps and discourage people from using them.

    Sometimes it all comes down to ECOOL

  • Oscar, if you don’t mind, how are you loading both Koala and Samplr on one screen? AudioBus?

  • @espiegel123 said:

    @ecou said:

    @espiegel123 said:

    @ecou said:
    Personally,I do not care to invest time and money in app (and IAP) that could stop working at anytime. Yes dev can abandon AU as much as IAA but less likely. In IAA case the cutoff could come from Apple, the DAW dev or the app dev.

    For me, there are IAA apps important enough to me that I'll freeze my current iPad to use them and get another for non-IAA.

    At what point you joined the game makes a big difference in this debate. I joined the game in 2017. AU was very popular at that point. As soon as I understood the difference I stopped buying IAA. For reference I am not a jammer, I don’t use AUM.

    I think it is less a matter of when you started (I started doing iOS music in 2018) as what apps you love. I have plenty of AU that I love and there are some IAA apps that were popular (and now) that are just amazing instruments that I gel with and for which I don't PERSONALLY find a satisfying replacement.

    Different people have different preferences -- which is cool. It just bugs me when people act is if people that don't have their preference are somehow objectively wrong -- or that the apps they don't like should be shunned. I rarely see people with IAA faves saying "don't use AU" but there plenty of people that are AUv3 purists (again: totally fine if that is their preference) who feel the need to be dismissive of IAA apps and discourage people from using them.

    For sure I don't know peoples' motivations here, but I kinda suspect that this is just old versus new perspective. It is for me too, but for me the new is the touch interface and what it brings and the old is the plugin.

  • @AlmostAnonymous said:
    I don’t mind IAA. I usually end up dedicating an old iPad to just the app tho in a live setting and send a midi clock to it. These also work wonders for ipads with no home button:

    (One mapped to command, the other mapped to tab)

    Is that a key tester?

  • @wawelt said:
    Oscar, if you don’t mind, how are you loading both Koala and Samplr on one screen? AudioBus?

    Samplr full screen and Koala in slide over mode. That’s a level of multi app fluidity that AU is years away from!

    I also have dedicated buttons to switch between Koala and Samplr on a hardware controller (facilitated by audiobus).

  • @OscarSouth said:

    @wawelt said:
    Oscar, if you don’t mind, how are you loading both Koala and Samplr on one screen? AudioBus?

    Samplr full screen and Koala in slide over mode. That’s a level of multi app fluidity that AU is years away from!

    I also have dedicated buttons to switch between Koala and Samplr on a hardware controller (facilitated by audiobus).

    That’s sweet, thanks!

  • @OscarSouth said:

    @wawelt said:
    Oscar, if you don’t mind, how are you loading both Koala and Samplr on one screen? AudioBus?

    Samplr full screen and Koala in slide over mode. That’s a level of multi app fluidity that AU is years away from!

    I also have dedicated buttons to switch between Koala and Samplr on a hardware controller (facilitated by audiobus).

    I want to see a video!. Do you move samples back and forth between the 2?. Did i say I want a video?.

  • Just to understand: does the fullscreen argument have to do with eliminating all distractions? I've found that maximizing a plugin in AUM/CB3/Drambo is "fullscreen enough" for me, but maybe my combination of device size (12.9") and expectations could make me not see a problem others have.

  • @NoiseFloored said:
    Just to understand: does the fullscreen argument have to do with eliminating all distractions? I've found that maximizing a plugin in AUM/CB3/Drambo is "fullscreen enough" for me, but maybe my combination of device size (12.9") and expectations could make me not see a problem others have.

    For apps that make full use of the screen real estate on 9.7” iPads, the seemingly small amount of space they give up as “full-screen” can be (negatively impactful). On devices with larger screens this might not be an issue.

  • edited March 2021
    The user and all related content has been deleted.
  • edited March 2021

    @NeonSilicon said:

    @AlmostAnonymous said:
    I don’t mind IAA. I usually end up dedicating an old iPad to just the app tho in a live setting and send a midi clock to it. These also work wonders for ipads with no home button:

    (One mapped to command, the other mapped to tab)

    Is that a key tester?

    It’s just a usb 2 key keyboard. Was about 20$ on Amazon. Something small so you could command+tab cycle through open apps on the iPads without home buttons without having to fuss with the touchscreen. Worked great for cycling through open IAAs in a live situation.

    Just brings up the app switcher for open apps without having to have a full keyboard attached.

  • @BCKeys said:
    Edit : oh and I like this workflow a lot, I feel like my DAW breathes, and I have the feeling that iOS handles several open apps much better than a DAW with several plugins loaded in it.

    Interesting that someone else has observed this too!

  • @espiegel123 said:

    @NoiseFloored said:
    Just to understand: does the fullscreen argument have to do with eliminating all distractions? I've found that maximizing a plugin in AUM/CB3/Drambo is "fullscreen enough" for me, but maybe my combination of device size (12.9") and expectations could make me not see a problem others have.

    For apps that make full use of the screen real estate on 9.7” iPads, the seemingly small amount of space they give up as “full-screen” can be (negatively impactful). On devices with larger screens this might not be an issue.

    For me it’s more about app design and flow. AU apps tend to be embedded in a GUI diving/switching workflow while full screen apps are generally designed to minimise the need for flicking between different apps — you work in one specific flow per app and changes in flow fit well conceptually with moving to a different app (which these days is a one button push experience).

    I do use lots of AU apps too, but they’re usually set up in advance and/or operated by MIDI, rarely in the foreground.

  • edited March 2021

    @tahiche said:

    @OscarSouth said:

    @wawelt said:
    Oscar, if you don’t mind, how are you loading both Koala and Samplr on one screen? AudioBus?

    Samplr full screen and Koala in slide over mode. That’s a level of multi app fluidity that AU is years away from!

    I also have dedicated buttons to switch between Koala and Samplr on a hardware controller (facilitated by audiobus).

    I want to see a video!. Do you move samples back and forth between the 2?. Did i say I want a video?.

    Well .. I am very encouragable!

    I have them set up in a sort of loop, where audio from mics/line inputs and semi-modular synths hits Koala. Koala can export audio into Samplr very quickly and Samplrs audio stream is coming back into Koala by IAA on the same bus as the external inputs.

  • @OscarSouth said:

    Samplr full screen and Koala in slide over mode. That’s a level of multi app fluidity that AU is years away from!

    I see that SNOW FOX!

    Cool! Does Koala let you set backgrounds? I never even checked...

  • @AlmostAnonymous said:
    I don’t mind IAA. I usually end up dedicating an old iPad to just the app tho in a live setting and send a midi clock to it. These also work wonders for ipads with no home button:

    (One mapped to command, the other mapped to tab)

    That is pretty cool ! 😎👍

  • edited March 2021

    @BCKeys good feedback. I think the AU format still needs to improve so I hope Apple have eyes and ears into our discussions.

    I guess it is a shame that it isn’t easier for programmers to create iOS apps that are both both AUv3 and IAA because the developers who now go the IAA route are missing out on sales, I expect. There’s a number of apps that I and others (on Discord and Facebook) just never purchased simply because they are IAA. Xequence2 is a good example. The response is often that these apps look awesome but they are not AU so they are going to be difficult to fit into a DAW workflow. Atom Piano Roll 2 is similar to Xequence2 in many ways (yes, very different in others) but it is AUv3. You can see the deserved buzz that having a top quality piano roll in AU format has generated. I don’t mean to pick on Xequence2 because I read the same comments about Patterning2, the Lumbeat apps, Sampletank, etc.

    There’s actually very few IAA only apps getting released these days. I can only think of Koala, Flip Sampler and Jamm Pro recently and I guess they fit Oscar’s performance app criteria so maybe make sense? I think lobbying for improvements to the AU format is the way to go.

  • @oddSTAR said:

    @OscarSouth said:

    Samplr full screen and Koala in slide over mode. That’s a level of multi app fluidity that AU is years away from!

    I see that SNOW FOX!

    Cool! Does Koala let you set backgrounds? I never even checked...

    Yes, it allows you to do it (settings > extras)

  • @OscarSouth @espiegel123 thanks, that does put things in perspective for me

  • @AlmostAnonymous said:

    @NeonSilicon said:

    @AlmostAnonymous said:
    I don’t mind IAA. I usually end up dedicating an old iPad to just the app tho in a live setting and send a midi clock to it. These also work wonders for ipads with no home button:

    (One mapped to command, the other mapped to tab)

    Is that a key tester?

    It’s just a usb 2 key keyboard. Was about 20$ on Amazon. Something small so you could command+tab cycle through open apps on the iPads without home buttons without having to fuss with the touchscreen. Worked great for cycling through open IAAs in a live situation.

    Just brings up the app switcher for open apps without having to have a full keyboard attached.

    Ah, interesting, thanks for the info. I'm kinda into mechanical keyboards and it looked like a mini key switch tester.

  • AuV3 for me = multiple instances

  • @OscarSouth said:

    @espiegel123 said:

    @NoiseFloored said:
    Just to understand: does the fullscreen argument have to do with eliminating all distractions? I've found that maximizing a plugin in AUM/CB3/Drambo is "fullscreen enough" for me, but maybe my combination of device size (12.9") and expectations could make me not see a problem others have.

    For apps that make full use of the screen real estate on 9.7” iPads, the seemingly small amount of space they give up as “full-screen” can be (negatively impactful). On devices with larger screens this might not be an issue.

    For me it’s more about app design and flow. AU apps tend to be embedded in a GUI diving/switching workflow while full screen apps are generally designed to minimise the need for flicking between different apps — you work in one specific flow per app and changes in flow fit well conceptually with moving to a different app (which these days is a one button push experience).

    I do use lots of AU apps too, but they’re usually set up in advance and/or operated by MIDI, rarely in the foreground.

    As a developer that does AU's, my mentality is what you describe in your last sentence there. An AU's GUI is for setup and then stays out of the way. Part of this is because I don't get to dictate where my AU even sits on the user's screen or how big it is. There are tons of design constraints that a well behaved AU has that a full app does not. Just having the knowledge that you can do whatever you want with the UI and the user interaction frees creativity and thinking about what is possible with user interaction.

  • @jolico said:
    AuV3 for me = multiple instances

    Multi-document apps would now allow that with stand alone apps too. It could be hard to arrange and control, but possible.

  • @NeonSilicon said:

    @OscarSouth said:

    @espiegel123 said:

    @NoiseFloored said:
    Just to understand: does the fullscreen argument have to do with eliminating all distractions? I've found that maximizing a plugin in AUM/CB3/Drambo is "fullscreen enough" for me, but maybe my combination of device size (12.9") and expectations could make me not see a problem others have.

    For apps that make full use of the screen real estate on 9.7” iPads, the seemingly small amount of space they give up as “full-screen” can be (negatively impactful). On devices with larger screens this might not be an issue.

    For me it’s more about app design and flow. AU apps tend to be embedded in a GUI diving/switching workflow while full screen apps are generally designed to minimise the need for flicking between different apps — you work in one specific flow per app and changes in flow fit well conceptually with moving to a different app (which these days is a one button push experience).

    I do use lots of AU apps too, but they’re usually set up in advance and/or operated by MIDI, rarely in the foreground.

    As a developer that does AU's, my mentality is what you describe in your last sentence there. An AU's GUI is for setup and then stays out of the way. Part of this is because I don't get to dictate where my AU even sits on the user's screen or how big it is. There are tons of design constraints that a well behaved AU has that a full app does not. Just having the knowledge that you can do whatever you want with the UI and the user interaction frees creativity and thinking about what is possible with user interaction.

    +1,000,000

  • @oddSTAR said:

    @OscarSouth said:

    Samplr full screen and Koala in slide over mode. That’s a level of multi app fluidity that AU is years away from!

    I see that SNOW FOX!

    Cool! Does Koala let you set backgrounds? I never even checked...

    Yeah!! :)

    And yeah, you can set your own background and even make it scroll while the sync clock is running. Makes it feel very personal! Great touch.

  • @NeonSilicon said:

    @OscarSouth said:

    @espiegel123 said:

    @NoiseFloored said:
    Just to understand: does the fullscreen argument have to do with eliminating all distractions? I've found that maximizing a plugin in AUM/CB3/Drambo is "fullscreen enough" for me, but maybe my combination of device size (12.9") and expectations could make me not see a problem others have.

    For apps that make full use of the screen real estate on 9.7” iPads, the seemingly small amount of space they give up as “full-screen” can be (negatively impactful). On devices with larger screens this might not be an issue.

    For me it’s more about app design and flow. AU apps tend to be embedded in a GUI diving/switching workflow while full screen apps are generally designed to minimise the need for flicking between different apps — you work in one specific flow per app and changes in flow fit well conceptually with moving to a different app (which these days is a one button push experience).

    I do use lots of AU apps too, but they’re usually set up in advance and/or operated by MIDI, rarely in the foreground.

    As a developer that does AU's, my mentality is what you describe in your last sentence there. An AU's GUI is for setup and then stays out of the way. Part of this is because I don't get to dictate where my AU even sits on the user's screen or how big it is. There are tons of design constraints that a well behaved AU has that a full app does not. Just having the knowledge that you can do whatever you want with the UI and the user interaction frees creativity and thinking about what is possible with user interaction.

    Very interesting, enriching and insightful to read. Thanks for sharing from your perspective!

  • I really feel like we've gotten to the core of the subject matter here!

Sign In or Register to comment.