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

1…5681011…16

Comments

  • supadomsupadom

    @u0421793 said:
    If the first one was called Audiobus, the second one should retrospectively be known as Beneath Audiobus, and this third one would be called Escape from Audiobus. Then there's the forthcoming "Conquest of…"; "Battle for…". That'll be it for a few decades until the remakes.

    I rather have numbers. If Rocky, Rambo and Terminator got away with it

  • [Deleted User][Deleted User]

    In Rocky terms I'm not looking forward to AB3 as Rocky3 was a tad cheesy pie :p

  • SebastianSebastian

    We're most likely going to call it Audiobus 3. It's recognisable and it shows how far we've come since creating the first app-to-app live audio streaming platform on iOS.

  • [Deleted User][Deleted User]
    edited August 2016

    B)
    you go boys!

  • [Deleted User][Deleted User]
    edited August 2016

    @Sebastian said:

    @richardyot said:
    If there's going to be a mixer please make the metering on each lane easy to read. This is one area where the otherwise excellent AUM really falls down.

    We hear you.

    RMS meters pretty please,
    peak isn't very telling ...

    stereo to mono, too?
    stereo bass sucks ...

    and you know the difference between panning and balance ;)

  • [Deleted User][Deleted User]
    edited August 2016

    @syrupcore said:

    And a +1 for the integrated keyboard and backwards compatibility questions above. If there's a keyboard integrated, it'd be sweet if AB3(dot 1) could detect if SoundPrism is installed on the device and if so, offer it as an alternative keyboard directly within the app.

    @Sebastian said:
    Regarding SoundPrism: huh, neat idea.

    +1

  • [Deleted User][Deleted User]
    edited August 2016

    @Sebastian said:

    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.

    this includes latency compensation? B)

    and a way to globaly select the samplerate of the ab 3 session in ab? :#
    hello 96khz ...

  • wimwim

    @Fruitbat1919 said:
    In Rocky terms I'm not looking forward to AB3 as Rocky3 was a tad cheesy pie :p

    Rocky 3.1 was awesome though.

  • JohnnyGoodyearJohnnyGoodyear

    @u0421793 said:
    If the first one was called Audiobus, the second one should retrospectively be known as Beneath Audiobus, and this third one would be called Escape from Audiobus. Then there's the forthcoming "Conquest of…"; "Battle for…". That'll be it for a few decades until the remakes.

    The AudioBus Supremacy?

  • nicknick

    Audiobus 3 -- The Return of the Midi?

  • supadomsupadom

    @nick said:
    Audiobus 3 -- The Return of the Midi?

    And inevitably 'AUM Strikes Back'

  • mkell424mkell424
    edited August 2016

    @u0421793 said:
    If the first one was called Audiobus, the second one should retrospectively be known as Beneath Audiobus, and this third one would be called Escape from Audiobus. Then there's the forthcoming "Conquest of…"; "Battle for…". That'll be it for a few decades until the remakes.

    I've really enjoyed Audiobus 2: Electric Boogaloo.

  • MusicInclusiveMusicInclusive

    @supadom said:

    @nick said:
    Audiobus 3 -- The Return of the Midi?

    And inevitably 'AUM Strikes Back'

    Switching paradigms, "Audiobus - the Undiscovered Country" :wink:

  • SebastianSebastian

    While I'm taking notes regarding your feature requests here, I feel like I should point this out: the goal of Audiobus 3 is to improve stability, save time wherever possible and make MIDI Routing reliable and understandable, while adding some of the most requested features in ways that help 90% of our users get to their preferred goals faster.

  • SamuSamu

    In my 'ideal' world the AB3 integration would work as well if not better than what can be accomplished with AU-X in a DAW such as Cubasis.

    Meaning I could 'sequence' an 'AB3-Source' like I sequence an AU-X plug-in using the host and when it's time to 'freeze/record' the track with the notes the Audio from the AB3-Source app would get recorded/rendered...

    Sure there is still possible to create a separate midi and audio-track but for the sake of 'housekeeping' the above would be ideal. (After freezing the audio could simply be moved to another track if needed).

  • [Deleted User][Deleted User]
    edited August 2016

    a global audio record function (without jumping through hoops) :#

  • SamuSamu

    If there was a way to 'hijack' audio on iOS similar to what Audio Hijack does on OS X it would be totally awesome...
    https://www.rogueamoeba.com/audiohijack/

  • [Deleted User][Deleted User]

    @Sebastian said:
    While I'm taking notes regarding your feature requests here, I feel like I should point this out: the goal of Audiobus 3 is to improve stability, save time wherever possible and make MIDI Routing reliable and understandable, while adding some of the most requested features in ways that help 90% of our users get to their preferred goals faster.

    Does this mean that there will be no free toaster?

  • wimwim
    edited August 2016

    @Fruitbat1919 said:
    Does this mean that there will be no free toaster?

    I wouldn't worry. Surely that falls within 90% of users preferred goals.

  • aaronpcaaronpc

    @Sebastian said:
    While I'm taking notes regarding your feature requests here, I feel like I should point this out: the goal of Audiobus 3 is to improve stability, save time wherever possible and make MIDI Routing reliable and understandable, while adding some of the most requested features in ways that help 90% of our users get to their preferred goals faster.

    Pretty much what I envisioned. It's a coming of age story.

  • u0421793u0421793

    @Sebastian said:
    While I'm taking notes regarding your feature requests here, I feel like I should point this out: the goal of Audiobus 3 is to improve stability, save time wherever possible and make MIDI Routing reliable and understandable, while adding some of the most requested features in ways that help 90% of our users get to their preferred goals faster.

    Interesting. What methodology will you be using to quantify effective hindering and impeding of that target 10% of your users?

  • JohnnyGoodyearJohnnyGoodyear
    edited August 2016

    @Sebastian said:
    While I'm taking notes regarding your feature requests here, I feel like I should point this out: the goal of Audiobus 3 is to improve stability, save time wherever possible and make MIDI Routing reliable and understandable, while adding some of the most requested features in ways that help 90% of our users get to their preferred goals faster.

    I hear you, but it's tricky, as regards expectations, because your language above (fairly or otherwise) is more in typical keeping with an upgrade whereas as soon as the buying public thinks about a NEW product, surely far outreaching an already beloved thingie, well, there are your expectations :)

  • OscarSouthOscarSouth

    Who knew that I'd discover the meaning of life at the bottom of a feature request thread on a software developer's message board. We are in a philosophical mood tonight.

  • wimwim
    edited August 2016

    @u0421793 said:

    @Sebastian said:
    While I'm taking notes regarding your feature requests here, I feel like I should point this out: the goal of Audiobus 3 is to improve stability, save time wherever possible and make MIDI Routing reliable and understandable, while adding some of the most requested features in ways that help 90% of our users get to their preferred goals faster.

    Interesting. What methodology will you be using to quantify effective hindering and impeding of that target 10% of your users?

    Ahhh ... cut him a break. He's already going for an extra 10% over the 80-20 rule. B)

  • ExAsperis99ExAsperis99

    Well, once you unleash the hype machine, the beast is no longer controllable.
    Just, you know: WHEN?

  • lovadamusiclovadamusic

    @wim said:

    @u0421793 said:

    @Sebastian said:
    While I'm taking notes regarding your feature requests here, I feel like I should point this out: the goal of Audiobus 3 is to improve stability, save time wherever possible and make MIDI Routing reliable and understandable, while adding some of the most requested features in ways that help 90% of our users get to their preferred goals faster.

    Interesting. What methodology will you be using to quantify effective hindering and impeding of that target 10% of your users?

    Ahhh ... cut him a break. He's already going for an extra 10% over the 80/20 rule. B)

    Hmm, I took it to mean 10% of users are beyond help.

  • wimwim

    @lovadamusic said:

    @wim said:

    @u0421793 said:

    @Sebastian said:
    While I'm taking notes regarding your feature requests here, I feel like I should point this out: the goal of Audiobus 3 is to improve stability, save time wherever possible and make MIDI Routing reliable and understandable, while adding some of the most requested features in ways that help 90% of our users get to their preferred goals faster.

    Interesting. What methodology will you be using to quantify effective hindering and impeding of that target 10% of your users?

    Ahhh ... cut him a break. He's already going for an extra 10% over the 80/20 rule. B)

    Hmm, I took it to mean 10% of users are beyond help.

    No, that's the 90%.

  • wigglelightswigglelights

    @u0421793 said:

    @Sebastian said:
    While I'm taking notes regarding your feature requests here, I feel like I should point this out: the goal of Audiobus 3 is to improve stability, save time wherever possible and make MIDI Routing reliable and understandable, while adding some of the most requested features in ways that help 90% of our users get to their preferred goals faster.

    Interesting. What methodology will you be using to quantify effective hindering and impeding of that target 10% of your users?

    Really?

  • WillWill

    @lala said:
    a global audio record function (without jumping through hoops) :#

    +1. Always available on the AB bar, a button to 'just record this stuff that's happening right now'. Though perhaps that breaks the "connections broker only" philosophy of the app.

  • brambosbrambos

    @u0421793 said:

    @Sebastian said:
    While I'm taking notes regarding your feature requests here, I feel like I should point this out: the goal of Audiobus 3 is to improve stability, save time wherever possible and make MIDI Routing reliable and understandable, while adding some of the most requested features in ways that help 90% of our users get to their preferred goals faster.

    Interesting. What methodology will you be using to quantify effective hindering and impeding of that target 10% of your users?

    Very likely those 10% will also benefit a lot from the planned improvements. It's just that not all of their exceedingly esoteric wishes will be met.

    Like, wishing for a bagle machine over a toaster.

Sign In or Register to comment.