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.

I do use AudioBus, all the time

Reposting this in a positive thread, hoping that fellow and fellowette AB enthusiasts will add thier support.

AudioBus changed so much for me. Discovering what it could do was a revelation. The glue I hadn't even realised I was looking for. I've been a fan ever since, and still believe that any music app not on the bus is, by definition, pedestrian. Rarely do I buy a music app that fails to provide AB compatibility, and when I do show faith, it just becomes frustrating, waiting for the developer to catch up, Moodscaper and Skram being prime examples.

I feel certain that AB3 will be everything we are anticipating, and a little bit more. Apple should be paying the AB team for all they've done to boost IOS music making. But being the greedy sods that Apple are, it's likely up to us to do what we can to promote and support AudioBus. Because if it wasn't there, IOS music making would be so much poorer, like an orchestra without a concert hall.

«1

Comments

  • Audiobus continues to be the lynchpin of all my musical endeavours on iOS. Thanks AB team!

  • Yay for reframing. Yay for AB3 and many more years of happy busing.

  • You guys like to listen sweet subjective thing, even don't want a bit of noise injection?

    How can we have a better days in this human world?

    Me? No worry, I will be off. Planet Apes.

  • I love AB too, although lately I haven't got the time to push virtual buttons & twist virtual knobs on my iPad.
    I've tried also a different workflow with AUM which is also awesome, but somehow the Audiobus Control panel is awesome. Especially since many of my loved apps have Link and they start in time.

    Not to mention AB remote which can run side by side on the iPad screen. Genious!

    Now all we need is wireless recording :)
    I know it's hard but not impossible. I'd love to use my iPad as my instrument and the iPhone as a daw... or buy a second hand ipad air 1 just to use it as a daw.

  • Audiobus is one of those examples where the outside is deceptively simple but what goes on inside is absolutely epic. As a dev, every time I run into some platform-complexity and I realise how much more of that type of stuff Audiobus has to cope with in an elegant and robust way my mind just boggles. Deep respect for what those guys are pulling off.

  • AUM is great, but I still use Audiobus for the reasons already stated here. AB is just the first thing I think of to quickly glue stuff together. The next version sounds like even more to look forward to.

    Beyond the app itself, the AB team is essentially the leadership for iOS music-making. Then, I believe this forum is the center of the iOS music social network. Use whatever apps you like, but some people should look beyond their self-absorbed little cloud to see the bigger picture.

  • Is there any info about the next version? @Sebastian ?

  • I love Audiobus. Without it, professional level music on iOS simply wouldn't exist.

  • @alecsbuga said:
    Is there any info about the next version? @Sebastian ?

    Info is coming in the next weeks. Launch is some time after that. We're currently nailing down the SDK, then implementing the UI (extensive Mockups are done).

    One of the main big features is going to be Midi (but a reliable implementation that avoids double notes and confusing routing in multiple places). We're closely working together with Johannes Dörr for that, the guy who makes MidiFlow. He's going to release a bunch of apps that are designed to showcase/facilitate Audiobus 3's features.

    There's going to be a new category of apps: Midi Filters.

    That should be enough for now, I hope.

  • AB support is planned for moodscaper and is currently in the top 5 requested features. Stay positive! :)

  • @moodscaper said:
    AB support is planned for moodscaper and is currently in the top 5 requested features. Stay positive! :)

    I'm positive about it. Moodscaper is great. AB support, whenever it happens, will make it greater.

  • @moodscaper said:
    AB support is planned for moodscaper and is currently in the top 5 requested features. Stay positive! :)

    Yay. :)

  • I'm also wondering if it's possible to 'sneak in' more of AudioBus interface into a hosts 'AU-View', i.e. integrate a 'lane' from AudioBus into an AU-View inside a host?

    I have to be honest but for me being able to avoid 'app swapping' is the biggest gain with AUs as it makes it easier to keep everything in focus. My typical workflow is to make a few scenes in Gadget, export them to DropBox as individual tracks and import them to Cubasis and transfer samples from Cubasis to Gadget via DropBox when needed since there is no 'Open In...' support and I'd rather avoid using AudioCopy. Too bad DropBox requires constant internet access to be useable.

    When the recording features in AudioShare got support for IAA-Inserts I noticed a drastic drop in my usage of AudioBus as the main feature was to chain apps and effects and record the results into AudioShare.

  • edited July 2016

    @Sebastian - please could you tell us what the relationship is (if any) between AB3 and TAAE2 as I'm extremely interested in both these things especially as you've mentioned MIDI here... ;) Look forward to hearing more about AB3! Edit - and happy to wait for more info as and when you see fit to share it - sure you guys are mega-busy as per :)

  • @moodscaper said:
    @Sebastian - please could you tell us what the relationship is (if any) between AB3 and TAAE2 as I'm extremely interested in both these things especially as you've mentioned MIDI here... ;)

    TAAE2 will be compatible with Audiobus, but that's pretty much it.
    Mike mainly made TAAE2 because he's using that for Loopy Masterpiece Edition (which will be compatible with Audiobus as well).

    There's no underlying dependency there and TAAE2 does not handle any MIDI stuff.

    What we're doing with MIDI in Audiobus 3 is that we're building it on CoreMIDI, but in a way that makes it immune to typical issues like double notes or confusing midi routing that has to be done in multiple places. Audiobus 3 will handle MIDI setup for apps that support it. We're going to make it very easy for MIDI controller apps to integrate the Audiobus 3 SDK and then be used in the Audiobus ecosystem alongside other apps.

    It's basically the same input->filter->output paradigm we're already using in Audiobus 2, but for MIDI. And all of the routing will be done in Audiobus 3, so there's no hunting for special MIDI configuration screens in all of the apps that are used.

  • @Sebastian said:

    @moodscaper said:
    @Sebastian - please could you tell us what the relationship is (if any) between AB3 and TAAE2 as I'm extremely interested in both these things especially as you've mentioned MIDI here... ;)

    TAAE2 will be compatible with Audiobus, but that's pretty much it.
    Mike mainly made TAAE2 because he's using that for Loopy Masterpiece Edition (which will be compatible with Audiobus as well).

    There's no underlying dependency there and TAAE2 does not handle any MIDI stuff.

    What we're doing with MIDI in Audiobus 3 is that we're building it on CoreMIDI, but in a way that makes it immune to typical issues like double notes or confusing midi routing that has to be done in multiple places. Audiobus 3 will handle MIDI setup for apps that support it. We're going to make it very easy for MIDI controller apps to integrate the Audiobus 3 SDK and then be used in the Audiobus ecosystem alongside other apps.

    It's basically the same input->filter->output paradigm we're already using in Audiobus 2, but for MIDI. And all of the routing will be done in Audiobus 3, so there's no hunting for special MIDI configuration screens in all of the apps that are used.

    This is big. Thanks!

  • @anickt said:

    @Sebastian said:

    @moodscaper said:
    @Sebastian - please could you tell us what the relationship is (if any) between AB3 and TAAE2 as I'm extremely interested in both these things especially as you've mentioned MIDI here... ;)

    TAAE2 will be compatible with Audiobus, but that's pretty much it.
    Mike mainly made TAAE2 because he's using that for Loopy Masterpiece Edition (which will be compatible with Audiobus as well).

    There's no underlying dependency there and TAAE2 does not handle any MIDI stuff.

    What we're doing with MIDI in Audiobus 3 is that we're building it on CoreMIDI, but in a way that makes it immune to typical issues like double notes or confusing midi routing that has to be done in multiple places. Audiobus 3 will handle MIDI setup for apps that support it. We're going to make it very easy for MIDI controller apps to integrate the Audiobus 3 SDK and then be used in the Audiobus ecosystem alongside other apps.

    It's basically the same input->filter->output paradigm we're already using in Audiobus 2, but for MIDI. And all of the routing will be done in Audiobus 3, so there's no hunting for special MIDI configuration screens in all of the apps that are used.

    This is big. Thanks!

    Yes, we think so, too.

  • @Sebastian - many thanks for the clarification - this all sounds rather fantastic!

  • @moodscaper said:
    AB support is planned for moodscaper and is currently in the top 5 requested features. Stay positive! :)

    >

    I am positive. It's a great app, with bags of potential. Also, I understand you're a sole developer, and can't do everything at once. I just happen to think that AB support is more use to more people than other features in waiting. :)

  • I do use AB - these days more likely with Audioshare.

    Looking forward to AB 3 :smiley: rocking! :+1:

    (See, made that positive too :wink: )

  • @moodscaper said:
    @Sebastian - many thanks for the clarification - this all sounds rather fantastic!

    Sweet. If you'd like to get access to the beta just send me a direct message and I'll send you the information you need.

  • Great news in this thread. Two of my favourite apps coming closer to MIDI. Making music on iOS is going to become even more pleasurable

  • Yes finally! I hate messing around with midi routings in different apps.

  • I've barely scratched the surface with Audiobus 2, and the remote..... This little bit of info is blowing my mind right up!

  • I would not be an app addict without it.
    Thanks a lot, AudioBus!

  • @Sebastian said:

    @alecsbuga said:
    Is there any info about the next version? @Sebastian ?

    Info is coming in the next weeks. Launch is some time after that. We're currently nailing down the SDK, then implementing the UI (extensive Mockups are done).

    One of the main big features is going to be Midi (but a reliable implementation that avoids double notes and confusing routing in multiple places). We're closely working together with Johannes Dörr for that, the guy who makes MidiFlow. He's going to release a bunch of apps that are designed to showcase/facilitate Audiobus 3's features.

    There's going to be a new category of apps: Midi Filters.

    That should be enough for now, I hope.

    Oh, that's nice.

  • I currently use AB + AUM as my core live setup. I have tried to only use one or the other, but run into too many blockers:

    AUM by itself, zombie IAA apps, no state saving, no routing the output of a channel into another app (for example, can't route an app's output into Loopy), no AudioBus panel in other apps, no AB remote.

    AB by itself, no mixer, sends, no AU.

    The two together... Overly complex setup, two hosts, noticeable latency even at buffer of 128 on live guitar and drum triggering.

    I think the AB-only setup is very close. I hope at some point a basic mixer gets added.

  • I have loved AB since day one, with the addition of MIDI support, I will be even more in love, if that's possible!!!

  • Same here. The Bus has been instrumental and I really can't wait for the next AB3

    @Nkersov said:
    Reposting this in a positive thread, hoping that fellow and fellowette AB enthusiasts will add thier support.

    AudioBus changed so much for me. Discovering what it could do was a revelation. The glue I hadn't even realised I was looking for. I've been a fan ever since, and still believe that any music app not on the bus is, by definition, pedestrian. Rarely do I buy a music app that fails to provide AB compatibility, and when I do show faith, it just becomes frustrating, waiting for the developer to catch up, Moodscaper and Skram being prime examples.

    I feel certain that AB3 will be everything we are anticipating, and a little bit more. Apple should be paying the AB team for all they've done to boost IOS music making. But being the greedy sods that Apple are, it's likely up to us to do what we can to promote and support AudioBus. Because if it wasn't there, IOS music making would be so much poorer, like an orchestra without a concert hall.

Sign In or Register to comment.