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.

Xequence 2.3 is now available (with full MPE support)

13»

Comments

  • @Gdub said:
    I have Xequence in an audio lane as someone above mentioned, so all good
    I guess it is possible to trigger loopy pro loops via Xequence?
    Any tips , advice,
    could I just use one lane to trigger loops at certain points along the time line of Xequence?

    I don't have loopy pro (my device is ios12 maximum)
    But yep... you can trigger it
    I already did this with other apps that deal with loops/samples

    Regarding Loopy Pro, you gotta check here:
    https://loopypro.com/manual/#control-settings

    The section of the manual you need

  • @SevenSystems

    That would be great Xequence as an au plugin!

    I thought it would be easier to create some more virtual midi out devices.
    Had a look into that and midiFire can create upto 64 virtual midi devices.
    So all my wishes are granted allready.

    Thanks again for the great software

  • @Alfred said:
    I thought it would be easier to create some more virtual midi out devices.

    Yes, it wouldn't be that hard to do technically, but:

    • the manual, website and many screenshots in both would have to be updated too
    • the better routing option in general is to select the other app as a destination on the instruments screen instead of listening to "Xequence Source" in the target app. That's because due to a technical oddity in Virtual MIDI, the exact MIDI timestamps from Xequence can only be passed to the destination plugin in the first scenario, not when using "Xequence Source". So, it would actually be better if AUM offered multiple "AUM Destination"s.

    Thanks again for the great software

    You're welcome, thanks for the feedback!

  • edited August 2022
    The user and all related content has been deleted.
  • edited July 2022

    @senhorlampada said:
    I'm gonna end up buying the AUv3 Pads and Keys to show my love for your work :wink:
    Good to use whenever on an AU workflow

    I’ve had them for awhile and they are both very useful, they did have them in a bundle so look for that too.

    Update - Bundle is still available.

  • @ReflectiveHaze said:
    Thanks for the great update! Love the Xequence + AUM workflow. So many good MIDI recording, selecting and editing tools in Xequence and now love the level indicators on Velocity and CCs! Bought the expansion pack to try MPE recording and editing :)

    Glad you're happy with the update 😊 If you bought the Enhanced Pack, also check out the ability to save and load instruments -- can be very handy for building a library of MIDI configurations for apps...

  • edited August 2022
    The user and all related content has been deleted.
  • A little request: There's currently a single known bug in Xequence 2.3.2: There seems to be some specific set of rare circumstances when switching to the Drums layout on the Keyboard screen causes a crash (seeing this in the crash logs).

    Is anyone here seeing this? If so it would be great if you could share the project and some details when this happens -- having a bug with crash potential in the app doesn't feel great no matter how rare.

  • edited August 2022
    The user and all related content has been deleted.
  • @ReflectiveHaze said:
    I hadn’t come across this bug, but tried to make it happen and think I found repeatable steps to cause a crash:
    1. Start a new project
    2. Go to the instrument page
    3. Touch the “+ Instrument” button
    4. Tap done in the new instrument screen
    5. Go to the keyboard page
    6. Change the keyboard to drum pads

    Hope this helps you find it!

    Hah, amazing! Thanks, baffled how this could've been overlooked. Fix is on the way!

  • Yep
    Same for me
    Latest iOS on iPad and iPhone
    Look forward to the update!!

  • @Gdub said:
    Yep
    Same for me
    Latest iOS on iPad and iPhone
    Look forward to the update!!

    Update has been submitted to Apple for review.

    In the meantime, you can duplicate an existing instrument ("+" button on an instrument) instead of using the "+ New Instrument" button to avoid the issue.

  • wimwim
    edited July 2022

    @SevenSystems said:
    Hah, amazing! Thanks, baffled how this could've been overlooked...

    Good help is soo hard to find these days! ;)

  • edited July 2022

    @wim said:

    @SevenSystems said:
    Hah, amazing! Thanks, baffled how this could've been overlooked...

    Good help is soo hard to find these days! ;)

    Haha! That's not what I meant -- I actually introduced the bug AFTER the beta! (it has to do with the file format optimizations... basically stripping redundant information from files but then failing to restore it...)

    I should've said "Baffled how this Seven Systems eejit could've overlooked it" 🍺

  • @SevenSystems the new update has come through and AB preset saving is now working like a charm, thanks 😊

  • @MisplacedDevelopment said:
    @SevenSystems the new update has come through and AB preset saving is now working like a charm, thanks 😊

    Don't praise the day before the evening! (German idiom) ... though I sure hope it's fixed now! 😎

  • Congrats! Any thoughts on how doable it would be to make the keyboard (and the AU Keys] Function as MPE controllers?

  • @Gavinski said:
    Congrats! Any thoughts on how doable it would be to make the keyboard (and the AU Keys] Function as MPE controllers?

    Thanks!

    Yes, turning Xequence's keyboard (and hopefully, Xequence AU | Keys) into an MPE controller is firmly planned for an update soon.

  • @SevenSystems said:

    @Gavinski said:
    Congrats! Any thoughts on how doable it would be to make the keyboard (and the AU Keys] Function as MPE controllers?

    Thanks!

    Yes, turning Xequence's keyboard (and hopefully, Xequence AU | Keys) into an MPE controller is firmly planned for an update soon.

    That would be great!

  • Eagerly await AUv3 so I can ditch Atom2, LK for this

  • @SevenSystems would you consider bringing the hold modes to the pads also?

  • @pruddo said:
    @SevenSystems would you consider bringing the hold modes to the pads also?

    Yeah, I did notice myself that they would make sense there too, I'll see if I can squeeze them in there sometime!

  • I don't see how to purchase the Enhanced Pack?

  • @gkillmaster said:
    I don't see how to purchase the Enhanced Pack?

    Hey. It should be on the settings screen, in the "i" tab?

  • @SevenSystems said:

    @gkillmaster said:
    I don't see how to purchase the Enhanced Pack?

    Hey. It should be on the settings screen, in the "i" tab?

    Omg, I was looking at Xequence 1. So sorry and thanks for the tip!

  • Just to clarify, PolyHymnia is part of the base app and the MPE capabilities are in the Enhanced Pack?

  • @gkillmaster said:
    Just to clarify, PolyHymnia is part of the base app and the MPE capabilities are in the Enhanced Pack?

    Yes exactly. Here's an overview of the differences:

    https://seven.systems/xequence2/en/enhanced/

Sign In or Register to comment.