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 is now available!

1121315171862

Comments

  • I was able to use the Files App, in iOS 13 beta (did not try on iOS 12) to uncompress then load the Gadget project file (no renaming). I then moved it into the "Gadget" folder in the "On My iPad" area (might have been a sub-folder within "Gadget", I will have to check later). It then showed up under "Open" on Gadget 2. Having only Kamata (which I don't think is used), it seemed to work with all tracks except the "Voice" one. Does anyone know which IAP that is? I wonder if there is another Gadget that could be used as a suitable alternative for the demonstration?

  • @espiegel123 said:

    @Steaders said:
    Couple of other questions.
    I can’t load apps inside Xequence right (like Aum)? I have to open them outside of Xequence before Xequence sees them?
    Other than state/preset saving, Why would I use Audiobus with Xequence?
    I am unable to sync start stop fugue Machine and Xequence. Is this where Audiobus comes in?
    Sorry if the answers are obvious.

    IMO, state-saving is huge plus the remote transport and app-switching available from the floating palette. That palette is handy even when state saving not needed.

    It absolutely is. I’m still figuring out Audiobus so it’s helpful to understand when to use it and when to not. Thanks!

  • edited July 2019

    @baconcow said:
    I was able to use the Files App, in iOS 13 beta (did not try on iOS 12) to uncompress then load the Gadget project file (no renaming). I then moved it into the "Gadget" folder in the "On My iPad" area (might have been a sub-folder within "Gadget", I will have to check later). It then showed up under "Open" on Gadget 2. Having only Kamata (which I don't think is used), it seemed to work with all tracks except the "Voice" one. Does anyone know which IAP that is? I wonder if there is another Gadget that could be used as a suitable alternative for the demonstration?

    Yeah unfortunately, Gadget doesn't detect nor inform the user about which IAPs are missing for a project in any way... the vocal track is however Abu Dhabi... but most of the drum tracks are made using Recife, which is another IAP.

    You can hear how "Alpha" should sound here:

    ...and Beta:

    Oh and yeah, I guess it might be easier to share a Gadget project file with iOS 13 because it supports unzipping. I'll try to devise a more efficient way once iOS 13 has become more mainstream, and update the "Downloads" page.

  • edited July 2019

    @BroCoast said:
    Hi, can someone quickly explain to me why I might want this? I mean no disrespect, just that I never grabbed V1 because I didn't really understand what it was good for either.

    I can't speak for anyone but myself. My purpose for using X2 is because it's the best App I've found so far for composing music the way that's most creative for me.

    I like to do long jams where I do a lot of improv and experimentation. Lot's of what I work out is completely serendipitous. I'll find a melody or some really complex arpeggios or cord progressions. Sometimes a very complex song will just suddenly enter my mind and it just comes out.

    I've been playing this way for years, and I often wish I had recordings of what I did, because after I'm done, it's gone forever.

    Because X2 uses MIDI, the files sizes are very small.

    Xequence stops recording 64 bars after the last existing part in the arranger. So I draw in very long blank track into X2 to keep it from auto-stopping.

    Then I can zone-out and jam while recording the whole thing into a tiny MIDI file.

    Later, I can go back and edit out the good parts into their own clips. Save the clips onto a new track, then save the new track with all the "good stuff" as a sort of archive of musical ideas that I can later use to build songs out of.

    I can do MIDI time stretching with X2 (most iOS DAW's can't do that), and time stretching lets me adjust the MIDI clips I plan on using together in a new project, so they can all have the same tempo.

    Because I'm working in MIDI and not audio, I can use my midi data to play other instruments other than the one I originally composed on.

    This app is a huge breakthrough for me, because I don't have to learn to play the stuff that "just happens" when I jam. Once it's MIDI, I can archive it and save it to an external drive when the new iPadOS comes around.

    If I need to tweak the MIDI to adjust certain parts, X2 has all the tools to do it.

    This is my purpose for this App.

  • @horsetrainer said:

    @BroCoast said:
    Hi, can someone quickly explain to me why I might want this? I mean no disrespect, just that I never grabbed V1 because I didn't really understand what it was good for either.

    I can't speak for anyone but myself. My purpose for using X2 is because it's the best App I've found so far for composing music the way that's most creative for me.

    I like to do long jams where I do a lot of improv and experimentation. Lot's of what I work out is completely serendipitous. I'll find a melody or some really complex arpeggios or cord progressions. Sometimes a very complex song will just suddenly enter my mind and it just comes out.

    I've been playing this way for years, and I often wish I had recordings of what I did, because after I'm done, it's gone forever.

    Because X2 uses MIDI, the files sizes are very small.

    Xequence stops recording 64 bars after the last existing part in the arranger. So I draw in very long blank track into X2 to keep it from auto-stopping.

    Then I can zone-out and jam while recording the whole thing in to a tiny MIDI file.

    Later, I can go back and edit out the good parts into their own clips. Save the clips onto a new track, then save the new track with all the "good stuff" as a sort of archive of musical ideas that I can later use to build songs out of.

    I can do MIDI time stretching with X2 (most iOS DAW's can't do that), and time stretching lets me adjust the MIDI clips I plan on using together in a new project, so they can all have the same tempo.

    Because I'm working in MIDI and not audio, I can use my midi data to play other instruments other than the one I originally composed on.

    This app is a huge breakthrough for me, because I don't have to learn to play the stuff that "just happens" when I jam. Once it's MIDI, I can archive it and save it to an external drive when the new iPadOS comes around.

    If I need to tweak the MIDI to adjust certain parts, X2 have all the tools to do it.

    This is my purpose for this App.

    Excellent! Exactly what I wanted to hear. Thanks for an incredibly concise summary.

  • @horsetrainer said:
    Xequence stops recording 64 bars after the last existing part in the arranger. So I draw in very long blank track into X2 to keep it from auto-stopping.

    I think rather than drawing in a long track, you can just drop a short clip way out in the timeline. Might be a little less work.

  • @wim said:

    @horsetrainer said:
    Xequence stops recording 64 bars after the last existing part in the arranger. So I draw in very long blank track into X2 to keep it from auto-stopping.

    I think rather than drawing in a long track, you can just drop a short clip way out in the timeline. Might be a little less work.

    Is there anything you don’t know wim? 😉👍🏻

  • @wim said:

    @horsetrainer said:
    Xequence stops recording 64 bars after the last existing part in the arranger. So I draw in very long blank track into X2 to keep it from auto-stopping.

    I think rather than drawing in a long track, you can just drop a short clip way out in the timeline. Might be a little less work.

    Ok, thanks for the help with that. :)

  • @SevenSystems : it would be great if recording didn't auto-terminate or at least used something not tied to what is already in the file. For example terminating after 32 measures without input or something.

  • @Steaders said:

    @wim said:

    @horsetrainer said:
    Xequence stops recording 64 bars after the last existing part in the arranger. So I draw in very long blank track into X2 to keep it from auto-stopping.

    I think rather than drawing in a long track, you can just drop a short clip way out in the timeline. Might be a little less work.

    Is there anything you don’t know wim? 😉👍🏻

    :lol:

    I often wonder this too when reading these forums.

    Great job on this @SevenSystems

    I'm still getting used to not being able to tap anywhere on the screen to close dialog/boxes but this is very slick.

  • This looks incredible.
    Great work.

  • wimwim
    edited July 2019

    @Steaders said:

    @wim said:

    @horsetrainer said:
    Xequence stops recording 64 bars after the last existing part in the arranger. So I draw in very long blank track into X2 to keep it from auto-stopping.

    I think rather than drawing in a long track, you can just drop a short clip way out in the timeline. Might be a little less work.

    Is there anything you don’t know wim? 😉👍🏻

    Well, for starters, how to play for more than 64 bars without getting sick of hearing myself. 😂

    I’d even settle for more than 4 bars.

  • @SevenSystems said:
    @Steaders, here's the video, I hope (but I guess you already figured it out) :

    @Steaders said:
    Couple of other questions.
    I can’t load apps inside Xequence right (like Aum)? I have to open them outside of Xequence before Xequence sees them?
    Other than state/preset saving, Why would I use Audiobus with Xequence?
    I am unable to sync start stop fugue Machine and Xequence. Is this where Audiobus comes in?
    Sorry if the answers are obvious.

    No, Xequence itself is a pure MIDI sequencer, but the beauty of using a separate app for hosting is that both apps can do at what they do best each.

    Regarding Audiobus, there's lots of other advantages. Being able to use MIDI processors in any spot in the routing, seeing the MIDI routing visually, switching between any two apps with a single tap, remote-controlling Xequence's or any other app's transport without switching apps, etc. etc...

    Regarding Fugue Machine, unfortunately it doesn't support start/stop sync via Ableton Link. It may support start/stop sync via Audiobus though (which Xequence also supports), though I'm not entirely sure. Maybe someone else?

    Syncing another sequencer is best done over MIDI clock because with LINK, you never know when both start and that can be annoying especially during editing when you hit Play and Stop often.

    Does Fugue Machine support receiving MIDI Clock?
    This would be perfect because Xequence 2 sends MIDI Clock and Start/Stop commands over MIDI, then Fugue Machine would follow X2 exactly.

    Sometimes, the "receive MIDI Clock" capability is hidden inside Audiobus support so it's always worth a try linking both with Audiobus.

  • edited July 2019

    @rs2000 said:
    Syncing another sequencer is best done over MIDI clock because with LINK, you never know when both start and that can be annoying especially during editing when you hit Play and Stop often.

    This has a pretty bad Link implementation. Apps with good Link implementation (see Patterning 2) do not have those transport issues you describe.

    Xequence 2 actually does something I've never experienced with any Link enabled app which makes it not worth having Link switched on at all.

  • @BroCoast said:

    @rs2000 said:
    Syncing another sequencer is best done over MIDI clock because with LINK, you never know when both start and that can be annoying especially during editing when you hit Play and Stop often.

    This has a pretty bad Link implementation. Apps with good Link implementation (see Patterning 2) do not have those transport issues you describe.

    Xequence 2 actually does something I've never experienced with any Link enabled app which makes it not worth having Link switched on at all.

    That's interesting. I'm sure @SevenSystems would want to fix it if anything is broken.
    Which two apps are you LINKing successfully with instant Start/Stop without delay?

  • @rs2000 said:

    @BroCoast said:

    @rs2000 said:
    Syncing another sequencer is best done over MIDI clock because with LINK, you never know when both start and that can be annoying especially during editing when you hit Play and Stop often.

    This has a pretty bad Link implementation. Apps with good Link implementation (see Patterning 2) do not have those transport issues you describe.

    Xequence 2 actually does something I've never experienced with any Link enabled app which makes it not worth having Link switched on at all.

    That's interesting. I'm sure @SevenSystems would want to fix it if anything is broken.
    Which two apps are you LINKing successfully with instant Start/Stop without delay?

    AUM & patterning will always start successfully with instant start/stop without delay.

    But I just tested this a bit and Xequence 2 will also work properly in this way after one initial start/stop. So it does work fine also just not on first try.

    Link V3 is very good. When apps implement it correctly there is no longer the problem of start delay.

  • edited July 2019

    @BroCoast said:

    @rs2000 said:

    @BroCoast said:

    @rs2000 said:
    Syncing another sequencer is best done over MIDI clock because with LINK, you never know when both start and that can be annoying especially during editing when you hit Play and Stop often.

    This has a pretty bad Link implementation. Apps with good Link implementation (see Patterning 2) do not have those transport issues you describe.

    Xequence 2 actually does something I've never experienced with any Link enabled app which makes it not worth having Link switched on at all.

    That's interesting. I'm sure @SevenSystems would want to fix it if anything is broken.
    Which two apps are you LINKing successfully with instant Start/Stop without delay?

    AUM & patterning will always start successfully with instant start/stop without delay.

    But I just tested this a bit and Xequence 2 will also work properly in this way after one initial start/stop. So it does work fine also just not on first try.

    Link V3 is very good. When apps implement it correctly there is no longer the problem of start delay.

    Thanks, that's useful input.
    In LINK v3, a LINK member can force all other members to a certain beat position which is necessary for instant start. It's described as to "better avoid" in the SDK docs so I'm not surprised that not every app developer has implemented it.

  • I can confirm one bug though. Screen recording with Xequence 2 open will crash it every single time.

    I tried to record an AUM session with Xequence 2, Patterning 2 and Animoog. As soon as I try to screen record it crashes Xequence 2, I tried this 3 times.

  • The user and all related content has been deleted.
  • @espiegel123 said:
    @SevenSystems : it would be great if recording didn't auto-terminate or at least used something not tied to what is already in the file. For example terminating after 32 measures without input or something.

    I hadn’t realised this, so I just tried it out with Xequence 1 (still on the fence about version 2). I just played keys for 64 bars and it stopped recording. This is very strange behaviour. I can’t really understand why it does this, as it’s a real improv killer.

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

    Resolved.

  • @purpan2 said:

    @espiegel123 said:
    @SevenSystems : it would be great if recording didn't auto-terminate or at least used something not tied to what is already in the file. For example terminating after 32 measures without input or something.

    I hadn’t realised this, so I just tried it out with Xequence 1 (still on the fence about version 2). I just played keys for 64 bars and it stopped recording. This is very strange behaviour. I can’t really understand why it does this, as it’s a real improv killer.

    @SevenSystems explained it to me once, though I won’t try to summarize. It kinda made sense to me at the time. :#

    It doesn’t seem like that big a deal if you know you’re going to be noodling for a long while just to drop a clip in there way out on the timeline. One can always save a project to use as a template, then open that and do a save-as when starting out.

    But that’s just me.

  • Is it possible to separate only one CC going out of Xequence?
    So there are many CC-information on one part, but I want to do MIDI-learn on the receiving tool. Can one CC be set on solo?

  • You can split the ccs onto their own track lanes, then solo the one you want. Just highlight a clip with automation and then go to the manic wand menu to select Controllers to own tracks. When done you can use undo to put them back together if you want.

  • @Satie said:
    Is it possible to separate only one CC going out of Xequence?
    So there are many CC-information on one part, but I want to do MIDI-learn on the receiving tool. Can one CC be set on solo?

    I've never seen this feature in a DAW but it's an interesting idea.
    Have you tried to just remove the respective CC entry on the MIDI Instrument page?
    I have not tried it but AFAIR the controller data will not be erased, then later you could add a CC value again? Worth a try, no?

  • Another simple way to accomplish the midi learn is simply to configure a slider for it in the Xequence keyboard for the app, then simply move the controller rather than playing back the track.

    But if for some reason having the track playing is necessary, then the other way I described will work too.

  • @rs2000 said:
    I've never seen this feature in a DAW but it's an interesting idea.

    You have now! ;)

  • Dumb question but how do I select a CC# to draw in information for? I can do pitch, velocity or notes.

    Also regarding Link. I have it working flawlessly now, not sure what I did but it always starts perfectly from AUM transport.

  • @rs2000 said:

    @Satie said:
    Is it possible to separate only one CC going out of Xequence?
    So there are many CC-information on one part, but I want to do MIDI-learn on the receiving tool. Can one CC be set on solo?

    I've never seen this feature in a DAW but it's an interesting idea.
    Have you tried to just remove the respective CC entry on the MIDI Instrument page?
    I have not tried it but AFAIR the controller data will not be erased, then later you could add a CC value again? Worth a try, no?

    I‘m sure, I have seen this feature in at least one tool, can’t find it right now - maybe „Different Drummer“ or „Aphelian“ ...

Sign In or Register to comment.