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.

Let's talk about Audiobus 3

1246716

Comments

  • @Lacm1993 said:
    Which third party apps will support all the new features of AB3 at launch?

    We're going to announce this at a later point in time. Currently it's a bunch of MIDI controllers and the MIDI filter apps that Johannes Dörr is building.

    We've put a lot of effort into making it very easy for developers of MIDI controllers to support the new Audiobus 3 MIDI SDK. With reduced App Review times it shouldn't take too long for more apps to appear once we make the SDK public.

  • @Sebastian said:

    @MusicInclusive said:
    How long will you continue support for AB 2? (I ask because I imagine not everyone will update right away).

    We won't add any new features to Audiobus 2 anymore and we see Audiobus 3 as the direct replacement for Audiobus 2. The plan is to make Audiobus 3 a must have upgrade from day 1 for any Audiobus 2 user. It's just so much better, really.

    Understood. My question is, rather, will there be an effective end-of-life date for AB 2 - i.e. that it will stop working properly like AB 1 did after a while when AB 2 came out?

    If so, how long do you anticipate that timeframe to be?

  • @Sebastian said:
    One way we're doing this is by now automatically and instantly launching apps into the background. We can even launch most output apps into the background, like Loopy and Cubasis – something only we can do because the Audiobus SDK in these apps allows us to tell them what to host and how to behave. It's pretty neat, and it’s going to make setting up sessions and switching presets much smoother.

    I assume you'll have a way to avoid "zombie apps" that occur with IAA? When I'm opening and closing apps on the fly in a live set, IAA zombie apps are a pain.

    If they open in the background, do they close and free up resources when the app is ejected from AB?

  • Zombie apps are a pain man....

  • @Sebastian said:

    @u0421793 said:
    Will there be VU meters? Warm glowing backlit ones?

    I'm going to have to pitch this to Mike, since he's working on the mixer.

    Will the mixer have Mix Buses?

    I'm dealing with too many host-like apps in my setup right now. I've come to rely on AUM's Mix Buses to quickly decide on the fly which app I want to route to Loopy. But AUM/IAA can't have another app as its output, so I have to point my mix bus output to AB to host Loopy.

    If the AB mixer has inserts and sends, then I can get down to one host app.

  • Wow.. Looks pretty crazy great

  • edited August 2016

    @gburks said:

    @Sebastian said:

    @u0421793 said:
    Will there be VU meters? Warm glowing backlit ones?

    I'm going to have to pitch this to Mike, since he's working on the mixer.

    Will the mixer have Mix Buses?

    I'm dealing with too many host-like apps in my setup right now. I've come to rely on AUM's Mix Buses to quickly decide on the fly which app I want to route to Loopy. But AUM/IAA can't have another app as its output, so I have to point my mix bus output to AB to host Loopy.

    If the AB mixer has inserts and sends, then I can get down to one host app.

    Inserts and sends are on our to do list, but most likely not for 3.0. That being said... Technically it's not really tricky as we have full control over the audio flow in AB 3.

  • @MusicInclusive said:

    @Sebastian said:

    @MusicInclusive said:
    How long will you continue support for AB 2? (I ask because I imagine not everyone will update right away).

    We won't add any new features to Audiobus 2 anymore and we see Audiobus 3 as the direct replacement for Audiobus 2. The plan is to make Audiobus 3 a must have upgrade from day 1 for any Audiobus 2 user. It's just so much better, really.

    Understood. My question is, rather, will there be an effective end-of-life date for AB 2 - i.e. that it will stop working properly like AB 1 did after a while when AB 2 came out?

    If so, how long do you anticipate that timeframe to be?

    I don't know the end of life date for Audiobus 2. Audiobus 1 did not stop working after Audiobus 2 came out because Audiobus 2 was a free update to Audiobus 1.

  • Hoping AC Sabre supports this sooner rather than later. Haven't bought it yet, but with all its midi controls I feel like I'd want Audiobus 3 to wrangle all that.

  • Just wondering what iOS minimum we have to be on ?

  • @Nicebutfun said:
    Just wondering what iOS minimum we have to be on ?

    Currently it looks like iOS 8 but we might up that to iOS 9 since there's hardly reason why one shouldn't upgrade to 9.

  • @db909 said:
    Hoping AC Sabre supports this sooner rather than later. Haven't bought it yet, but with all its midi controls I feel like I'd want Audiobus 3 to wrangle all that.

    The developer of AC Sabre has access to the AB 3 SDK so it's really up to him. I've met him in Berlin. Pretty cool guy.

  • 2 questions:

    Will AB3 support interfaces with multiple outs and allow routing to those outputs?

    Will AB3's ram footprint be comparable to AB2?

    Thanks

  • edited August 2016

    @Sebastian said:

    @MusicInclusive said:

    @Sebastian said:

    @MusicInclusive said:
    How long will you continue support for AB 2? (I ask because I imagine not everyone will update right away).

    We won't add any new features to Audiobus 2 anymore and we see Audiobus 3 as the direct replacement for Audiobus 2. The plan is to make Audiobus 3 a must have upgrade from day 1 for any Audiobus 2 user. It's just so much better, really.

    Understood. My question is, rather, will there be an effective end-of-life date for AB 2 - i.e. that it will stop working properly like AB 1 did after a while when AB 2 came out?

    If so, how long do you anticipate that timeframe to be?

    I don't know the end of life date for Audiobus 2. Audiobus 1 did not stop working after Audiobus 2 came out because Audiobus 2 was a free update to Audiobus 1.

    Sure - but it did eventually :smile: . I support - in a limited manner - those who work in music education, some of whom do work with Audiobus in the classroom. Often they have very little budget to buy apps, so, if they need to plan ahead to purchase AB3 by a certain date it would be good to know. I say that as having actively promoted the use of AB among them, so, it would be good to know in order to prepare in that same vein of support.

    (BTW: When you say that AB 1 did not stop working after AB 2 came out, do you mean that as far as you are aware AB 1 still works? I ask because it isn't for me any more on an iPad 1. And, no, I don't realistically use that iPad with AB any more :smiley: - just fact checking so I understand what you're saying :+1: )

  • @Sebastian said:
    You can already bypass audio effects via the bypass button in the connection panel. That's probably how we're going to do it for MIDI filters as well. But I guess we could add specifica UI for it in the Audiobus app. Hmm...

    Right. Instead of adding new UI to the app, consider just making the panel available within the Audiobus app?

    Nothing is keeping Johannes (or anyone else) from building all of these things as MIDI filter apps for Audiobus 3.

    SWOON!

    Any app that works in Audiobus 2 will also work in Audiobus 3.

    Awesome. That's was confusing.

  • @Sebastian said:
    The 'this app wants to open that other app' pop up will be gone. Does that count?

    Boom!

    I just wanted to see if we could getaway with that. But you're right, we're probably going to add automatic import from AB2 to AB3 via shared app space. Happy now? :)

    Boom!

    It's okay, I was expecting that. As long as you all understand that we need to ship this at some point and that more features always mean more support and more bugs that have to be fixed, I think there's always enough room for compromise while still making it a great platform.

    Boom!

    @JohannesD said:
    Although no keyboard will be built into AB3 there will still be a dedicated keyboard app harnessing AB3's new MIDI features :)

    Boom! Care to spill the beans on the rest of the dedicated apps you're building?

  • edited August 2016

    MOST IMPORTANTLY: have you convinced Oliver Wittchow to get the minimighty nanoloop on the bus?

  • I'm guessing I am done with new apps for music creation in IOS until I get the funds to upgrade my iPad2 to something more modern. Nevertheless glad to see progress is being made on AB, which was my first introduction w/ Loopy into IOS music making.

  • Here's a question that I haven't seen asked...Is the app universal (read: does it support iPhone)? I use my iPhone exclusively for music making, and have retired my iPad 2.

    Also, with this midi implementation, will all of the apps run in sync properly (when played from a sequencer, like a piano roll, and have transport controls?

  • @Sebastian said:

    @mister_rz said:
    Will audiobus ever become an au3 itself, so I can load it into compatible hosts and automate all my synth/fx chains.

    With the current Ram limitations of AUX I don't think that is possible. But with Audiobus 3 we're going to have much more control over the audio and MIDI routing of a session than ever before, which should allow us to do pretty amazing things now (i.e. background launching for IAA hosts) and in the future.

    Can ab3 record system audio?

    I don't think that is possible on a device that has not been rooted.

    Thanks Sebastian, I can carried away imagining audiobus being a modular monster with shades of kore, looking forward to all the new stuff, especially the audio and midi routing, I am excite!

  • I am excited for AB3! Bring it on!

  • Ok....ill buy it, even though I bought AB 2 and couldn't understand how it worked and how to use it with AUM. I hope you will have a detailed manual AND video where we can learn how to make these apps work, I know many are experts here, but for me it's all very confusing......

  • @drjazz930 said:
    Ok....ill buy it, even though I bought AB 2 and couldn't understand how it worked and how to use it with AUM. I hope you will have a detailed manual AND video where we can learn how to make these apps work, I know many are experts here, but for me it's all very confusing......

    Just start a new thread describing something that you're trying to do and someone will help out.

  • @Sebastian Thanks. I can't wait! :)

  • Sounds awesome. Looking forward to it!

  • @Sebastian said:

    @db909 said:
    Hoping AC Sabre supports this sooner rather than later. Haven't bought it yet, but with all its midi controls I feel like I'd want Audiobus 3 to wrangle all that.

    The developer of AC Sabre has access to the AB 3 SDK so it's really up to him. I've met him in Berlin. Pretty cool guy.

    Just a reminder: Today is the last day to get AC Sabre for the intro price.

  • @syrupcore said:

    Boom! Care to spill the beans on the rest of the dedicated apps you're building?

    Besides the already mentioned splitter and keyboard apps, I'm working on a couple of MIDI effects that will be really fun and interesting to play with. There will also be a remapper for transforming MIDI messages. Everything is based on Midiflow, but optimized for the Audiobus workflow. Not all of those apps will be available at launch of AB3 though.

    I'm open to suggestions concerning MIDI effects, by the way. :)

  • @JohannesD said:

    @syrupcore said:

    Boom! Care to spill the beans on the rest of the dedicated apps you're building?

    Besides the already mentioned splitter and keyboard apps, I'm working on a couple of MIDI effects that will be really fun and interesting to play with. There will also be a remapper for transforming MIDI messages. Everything is based on Midiflow, but optimized for the Audiobus workflow. Not all of those apps will be available at launch of AB3 though.

    I'm open to suggestions concerning MIDI effects, by the way. :)

    Sounds awesome. Will the keyboard support a scale mode? If not at launch.... pretty please!

    An arpeggiator seems like it'd be awfully popular. Nothing crazy—dedicated apps handle that. Something with three buttons on AB sidebar that toggle through those options like the Loopy loop length:

    1. Step size (1/2, 1/4, 1/8, 1/16),
    2. arp direction (as played, up, down, random)
    3. range (0, +1 oct, +2oct).
  • In addition to splitting, will AB natively support MIDI multing/merging? Play two or more destinations from the same midi channel?

  • I know discussions around this are in dead horse territory but since we're talking about it. I'll revive it: I'd love to see filters within the AB app selection lists that match the filters on http:/:audiob.us/apps (state saving, Link support...). And, if possible, "recently used".

Sign In or Register to comment.