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.

[ ONE IMPORTANT QUESTION ABOUT IAA ]

2»

Comments

  • @j_liljedahl & @WaveMachineLabs Really thanks guys, specially Jonatan, now I know all I want to know :-)

  • Thanks @ Rim. That was very helpful. This is one thing I don't understand, I purposely disabled background audio in Megellan and everything still works. I can switch from host to Megellan and still get sound playing the host keyboard. I'm also able to record.

  • edited October 2013

    @mgmg4871: When an app has a "background audio" toggle, it usually only takes effect if there are no other conditions saying it should keep playing in background. Examples of such conditions are: Currently connected to Audiobus or an IAA host. This is exactly as it should be, it would be confusing if users needed to remember to switch on "background audio" to get it working with Audiobus, for example.

    Personally, I think the best way is to not even have a "background audio" toggle, but simply figure out if an app should play in background or not. Sometimes it's easier, for example AudioShare simply continues in background if any of the following conditions are true:

    • Currently playing a file
    • Currently recording
    • Connected to Audiobus
    • Currently running IAA nodes (next version!)

    A synth app could add:

    • Currently playing a sequencer or arpeggiator in HOLD mode
    • Connected through virtual midi
  • @Jonatan, thanks for clearing that up for me.

  • And actually, I think there are cases where an app couldn't know if it should play in background or not. For example, if a synth is controlled from a hardware MIDI interface. They usually auto-connect to such interfaces to avoid needing the user enter some midi setup menu and connect manually, and in that case it could be confusing if one had to manually disconnect from all midi interfaces to stop the app from running in background.

Sign In or Register to comment.