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.

Could AB3 be an AU host?

What do you think, would this be a possibility at all?

Comments

  • I can''t see any reason why AB3 could not be an AU Host but the question is really why? To compete with DAWs?

    Since most of the apps AB manages data to and from are already hosts of some kind it would be 'host to host host' which to me seems less than optimal way of doing things.

    Considering that apps that implement AB also get IAA-Generator 'for free' and since 'hosts' are improving I seem my self being less and less dependant on AB. I am tempted by Kymaticas upcoming AUM which to me feels like an AB replacement for live-work and 'noodling'.

  • edited February 2016

    Yep, eventually it can be. Although we don't see much appeal in focusing on the current way AU are implemented. iOS music apps are great because they allow developers to access the whole screen and use most of the device's capabilities without much restriction regarding Ram.

    What really baffles me is how Audio Unit Extensions are treated as the next big thing when it's clear that there's almost no incentive for developers to add that functionality to their apps because they cannot be monetised (which part of the reason that there's almost no uptake in the technology). And once they're in use they take even more of a backseat position because the DAW's chrome eats up most of the screen real estate. Wasteful, in my opinion.

    I'm not even going to start talking about the lacking documentation for OS X or limitations to the UI. iOS music is much more than a few synths with lots of knobs.

    iOS has too many great MIDI controller apps that aren't utilized properly because CoreMIDI routing is almost as big of a minefield as CoreMIDI Sync is. Now that Link is here and we have access to a global play button via the Audiobus SDK we can tackle that part. If you enjoy DAW-like workflows that focus on mastering there are great apps for that already, like Cubasis and Auria Pro.

    We believe the Connection Panel, Audiobus Remote and fewer ways to misconfigure MIDI and Audio routing with less taps and fewer hiccups is key.

  • I was mainly thinking this would be great for live performance situations. So instead of trying to use a real daw we could have AB as the host with the advantage of being able to use multiple instances of our beloved apps. Especially for effects it would be incredibly handy to be able to have the same delay or reverb or whatever on different instruments. I think it would be great!

  • edited February 2016

    There's a ram limitation on Audio unit extensions which means if your most beloved apps are sample based you're not going to gain much from the theoretical multi-instance capabilities. If they can be ported at all - even if the developer has the technical prowess to pull Audio Unit V3 stuff off.

    And then there's a problem with the screen size suggestions that the GarageBand team has come up with and which seems to be the usual guideline for Audio unit extensions - if your app has an innovative input paradigm like say... Fugue Machine or Patterning there's very little chance they're going to be able to fit into that.

    And then on top of that this restriction interferes with any host's design, because then implementing Split View will be very tricky. I can't help but feel that these are massive design restrictions and some of them are shortsighted in the face of iOS 9's new visual multitasking features (which are great).

  • If more developers would make their iOS apps multi-timbral it would solve my problem to want to have several instances.
    There are a few like ThumbJam which let me do it!
    If i could use up to 8 parts of an app i would be happy. It would also make it possible to make proper settings to use such apps with a midi controller like a linnstrument, seaboard and of course ThumbJam etc.

Sign In or Register to comment.