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 midi sequencer ?

1394042444552

Comments

  • Is anyone able to control Sunrizer with Xequence? I can see Sunrizer inside Xequence and set it up as an instrument, but no matter what I do I can't get Sunrizer to respond, I can't even get it to show up as a midi input option in the Sunrizer utilities section, whereas every other midi device I open shows up fine.

  • @lairdhenn said:
    Is anyone able to control Sunrizer with Xequence? I can see Sunrizer inside Xequence and set it up as an instrument, but no matter what I do I can't get Sunrizer to respond, I can't even get it to show up as a midi input option in the Sunrizer utilities section, whereas every other midi device I open shows up fine.

    Turn on "Background Audio" in Sunrizer (button at the top left).

  • @SevenSystems said:

    @lairdhenn said:
    Is anyone able to control Sunrizer with Xequence? I can see Sunrizer inside Xequence and set it up as an instrument, but no matter what I do I can't get Sunrizer to respond, I can't even get it to show up as a midi input option in the Sunrizer utilities section, whereas every other midi device I open shows up fine.

    Turn on "Background Audio" in Sunrizer (button at the top left).

    Wow I feel like an idiot, I forget that that has to be engaged each time it is opened. Wish it was a 'set and forget' menu option like most other apps. Working fine now haha, thanks.

  • @lairdhenn said:

    @SevenSystems said:

    @lairdhenn said:
    Is anyone able to control Sunrizer with Xequence? I can see Sunrizer inside Xequence and set it up as an instrument, but no matter what I do I can't get Sunrizer to respond, I can't even get it to show up as a midi input option in the Sunrizer utilities section, whereas every other midi device I open shows up fine.

    Turn on "Background Audio" in Sunrizer (button at the top left).

    Wow I feel like an idiot, I forget that that has to be engaged each time it is opened. Wish it was a 'set and forget' menu option like most other apps. Working fine now haha, thanks.

    No problem, still catches me every time too.

  • @lairdhenn said:

    @SevenSystems said:

    @lairdhenn said:
    Is anyone able to control Sunrizer with Xequence? I can see Sunrizer inside Xequence and set it up as an instrument, but no matter what I do I can't get Sunrizer to respond, I can't even get it to show up as a midi input option in the Sunrizer utilities section, whereas every other midi device I open shows up fine.

    Turn on "Background Audio" in Sunrizer (button at the top left).

    Wow I feel like an idiot, I forget that that has to be engaged each time it is opened. Wish it was a 'set and forget' menu option like most other apps. Working fine now haha, thanks.

    I think it will load no problem as an AU with state saving in AB3.

  • @ExAsperis99 said:

    @lairdhenn said:

    @SevenSystems said:

    @lairdhenn said:
    Is anyone able to control Sunrizer with Xequence? I can see Sunrizer inside Xequence and set it up as an instrument, but no matter what I do I can't get Sunrizer to respond, I can't even get it to show up as a midi input option in the Sunrizer utilities section, whereas every other midi device I open shows up fine.

    Turn on "Background Audio" in Sunrizer (button at the top left).

    Wow I feel like an idiot, I forget that that has to be engaged each time it is opened. Wish it was a 'set and forget' menu option like most other apps. Working fine now haha, thanks.

    I think it will load no problem as an AU with state saving in AB3.

    That's of course the "big boy's way" to do it! :)

  • Xequence is definitely becoming my favorite iOS midi sequencer as I become more proficient with it, so I have almost nothing but good things to say about it but I have one gripe that I would love to see changed. When I create a part and enter grid editing view it looks great, nice and open with no clutter, but when I’m editinng a part I have it looping almost every time. That diagonal line overlay is a total struggle to work against. I already know the part is looping and the loop icon in the menu bar is highlighted as a reminder as well. If there was an option to completely disable the looping overlay I would consider this a 10/10 sequencer, all other minor bugs aside.

  • edited October 2018

    @lairdhenn Nice to see you're happy with Xequence, and interesting to hear about the loop overlay being too distracting to you... I didn't hear any complaints about that yet, but an option in "..." settings to hide it while in the pianoroll editor can definitely be added in the next update.

    About "all other minor bugs", can you give a few more details on those? I'd love to crush them.

    Thanks :)

  • @SevenSystems said:

    @ExAsperis99 I can't give too many details really at this stage, sorry. All I can say is that the purists among you don't have to worry -- Xequence will stay a lean and clean MIDI-only sequencer as it is now, and be fully maintained and enhanced further. This other thing, if it ever gets finished, will be a separate app.

    It will share many of Xequence's features and of course its great workflow, but will be simplified and have a different target audience and thus probably not be very interesting for the forum, as it very likely won't have any audio connection to the outside world.

    I've said in another thread that I still think that the best possible music production flow on a small device is having everything in a single, optimized UI in one app. Maybe this hints at where I'm trying to go :)

    I want that!

    On another note... I know that code reusability is the way to go, considering that ios apps don't pay as much as desktop apps :sweat: But since xequence won't have this mixer, will you make the instrument page vertical, or grid-based or someting? :lol: :wink:

  • @SevenSystems Hello there, as a long time customer, I would have a question for you :) When I set Xequence in Audiobus and sync it midi with the whole system, as soon as I push play in audiobus, Xequence plays as well. But I don't find a way to start recording when I push play in audiobus, it works only for playing it seems. Is there a way to start recording as well when the MIDI sync occurs? Thanks.

    I can record when I press the record button anyway but I just wanted to check if there was something automatic in place as well.

  • edited October 2018

    @Norbert, I even answer questions from short-time customers! :) Audiobus has a separate "Record" button and Xequence does support it, however Audiobus only shows it for each particular app that supports recording, not for Audiobus itself. So, you won't have a record button below the Audiobus icon in the panel, but for example below / next to Xequence:

    (it makes sense because you certainly never want ALL connected apps to be recording AT ONCE!)

  • edited October 2018

    @SevenSystems said:
    @Norbert, I even answer questions from short-time customers! :) Audiobus has a separate "Record" button and Xequence does support it, however Audiobus only shows it for each particular app that supports recording, not for Audiobus itself. So, you won't have a record button below the Audiobus icon in the panel, but for example below / next to Xequence:

    (it makes sense because you certainly never want ALL connected apps to be recording AT ONCE!)

    Oh cool thanks. I hadn't seen that. I will check tonight :) I want to record my crazy plays with Gestrument Pro into Xequence so I can edit it later.

  • edited October 2018

    @SevenSystems said:
    @lairdhenn Nice to see you're happy with Xequence, and interesting to hear about the loop overlay being too distracting to you... I didn't hear any complaints about that yet, but an option in "..." settings to hide it while in the pianoroll editor can definitely be added in the next update.

    About "all other minor bugs", can you give a few more details on those? I'd love to crush them.

    Thanks :)

    Oh wow, the option to get rid of that overlay would be amazing. I'm really looking forward to that, and surprised no one else has mentioned it, maybe I'm too picky about small details...

    As for the minor bugs, in trying to recreate them it seems most of them (UI lockups) are actually my own fault as a result of using multitouch gestures to swipe back into Xequence, which I'm under the impression is kind of out of your control and why many apps recommend disabling them? For example if I'm in in any app and swipe back into Xequence's main layout the left sidebar instrument controls are completely unresponsive except for the + button, I have to tap in the grid space for them to become responsive again.

    The only other thing that I'm not sure if it is a bug or a misunderstanding on my end concerns looping with Link enabled. I like to play non-linearly and create sections I can jump around to and I haven't been able to make this work smoothly.

    The first issue is that in a scenario where Xequence is playing and I'm looping a sequence and want to disengage looping it but continue on to the next part. When I disable looping, instead of seamlessly continuing through the sequence onto the next one the progress bar jumps back to the beginning of the closest bar and waits for Link to start a new count, halting the sequence completely. The same thing happens if I want to engage looping while playing. Contrast this to say BM3 or Ableton, if their sequencers are looping a section while Link is enabled and you disengage the active loop they continue playing without interruption.
    The other issue is very similar. Again if I don't want to purely play sequences linearly and want to tap the ruler to choose which sequence to hop to next, the sequences abruptly stop and wait for a 1 count from Link to proceed to the chosen part, whereas in other sequencers (BM3 and Ableton is what I tested with again) the present part finishes the count and seamlessly jumps to the new one.

    The final thing is that the metronome is only audible during the count in and I haven't found a way (either by midi or audio on any volume setting) to make it continue being audible while recording which is the point of a metronome I've always assumed.

    I hope that isn't way too much to process, but those I think are really the only issues I've had, everything else is perfect.

  • edited October 2018

    @lairdhenn thanks for the detailed post, here's what I can say:

    As for the minor bugs, in trying to recreate them it seems most of them (UI lockups) are actually my own fault as a result of using multitouch gestures to swipe back into Xequence

    They're not your fault, but as you suspect, they're indeed a recurring gripe with iOS constantly introducing new gestures that interfere with normal app operation (just ask Audiobus @Michael about it!). It's hard to keep "catching up", but I'll add this to the investigation shortlist for a bugfix update.

    When I disable looping, instead of seamlessly continuing through the sequence onto the next one the progress bar jumps back to the beginning of the closest bar and waits for Link to start a new count
    The other issue is very similar. Again if I don't want to purely play sequences linearly and want to tap the ruler to choose which sequence to hop to next, the sequences abruptly stop and wait for a 1 count

    Yes, those two things are "by design", even if it might sound like an excuse -- Xequence's engine is really not very good at anything that involves abrupt tempo or position changes (mea culpa!). It's designed that way to make development quicker as the current design involves far less overhead than doing it "properly". Unfortunately it also has to do with the already thin economic margins when it comes to iOS music software development... ;) :bawling:

    The final thing is that the metronome is only audible during the count in and I haven't found a way (either by midi or audio on any volume setting) to make it continue being audible while recording which is the point of a metronome I've always assumed.

    You should be able to turn on the metronome by tapping on the BPM in the top toolbar, and then enabling it in the dropdown menu?

    I hope that isn't way too much to process, but those I think are really the only issues I've had, everything else is perfect.

    Thanks very much! And not too much to process.

  • @SevenSystems said:
    @Norbert, I even answer questions from short-time customers! :) Audiobus has a separate "Record" button and Xequence does support it, however Audiobus only shows it for each particular app that supports recording, not for Audiobus itself. So, you won't have a record button below the Audiobus icon in the panel, but for example below / next to Xequence:

    (it makes sense because you certainly never want ALL connected apps to be recording AT ONCE!)

    For some weird reasons, I can't manage to pilot Audiobus from Xequence. It just doesn't want to start when I press 'Play' or 'Record' in your app. When I start playing Gestrument Pro for example, it starts audiobus fine. But Xequence doesn't seem to get it working. No idea what I am doing wrong.

  • edited October 2018

    @Norbert apps hosted in Audiobus can't control the Audiobus transport. It's the other way around. You use Audiobus' transport controls, and they then start / stop Xequence. The controls are below the Audiobus icon in the panel, or to the right of the Audiobus icon inside the Audiobus app at the top. Ableton Link also has to be enabled everywhere.

  • edited October 2018

    So then it means we cannot start recording on sync? We have to hit record first then hit play in audiobus to start playing what we want to record. Thanks, that's what I thought :)

    Would be nice to have a feature to put record on hold until it starts to play though. Auria Pro does that and it's neat.

  • @Norbert, at least on iPad, you get those app icons inside the Audiobus app, at the top... there, you should find Xequence's icon and there should be a Record button next to it. When you tap that, recording and transport should start in Xequence (and transport should start in all other apps at the same time). It seems like this stuff isn't available on iPhone, only on iPad. Not sure currently, can anyone else chime in maybe?

    I've also noticed that recently, start/stop sync has become slightly buggy (stop often only works the second time you tap the Audiobus play/pause button). Xequence has been built with a beta Audiobus SDK because of some advanced MIDI stuff, it will probably all get more stable once the new Audiobus SDK is in.

  • edited October 2018

    @SevenSystems said:
    @Norbert, at least on iPad, you get those app icons inside the Audiobus app, at the top... there, you should find Xequence's icon and there should be a Record button next to it. When you tap that, recording and transport should start in Xequence (and transport should start in all other apps at the same time). It seems like this stuff isn't available on iPhone, only on iPad. Not sure currently, can anyone else chime in maybe?

    I've also noticed that recently, start/stop sync has become slightly buggy (stop often only works the second time you tap the Audiobus play/pause button). Xequence has been built with a beta Audiobus SDK because of some advanced MIDI stuff, it will probably all get more stable once the new Audiobus SDK is in.

    I know what you mean but it actually doesn't start in sync when I hit record in audiobus. At the moment, I have to press record first so xequence starts recording and then when I hit play in audiobus, gestrument pro starts playing and is recorded inside Xequence. I have tried many different MIDI setups in the different apps but to no avail. It is not a big deal as I can slide the midi notes back to the left when I am finished. So it's ok for now :)

  • edited October 2018

    @SevenSystems

    All icons are there but only in landscape mode on iPhone 7 Plus.

  • edited October 2018

    @SevenSystems can you record longer than 64 bars?

  • @[Deleted User] said:
    @SevenSystems can you record longer than 64 bars?

    Yes of course. Xequence just considers 64 bars after the last part to be the end of the song. So, just draw a very long empty part before you start recording (if you draw a 128 bars long part, recording will stop at bar 192). You can draw as long as you need, there's no overhead.

  • @SevenSystems said:

    @[Deleted User] said:
    @SevenSystems can you record longer than 64 bars?

    Yes of course. Xequence just considers 64 bars after the last part to be the end of the song. So, just draw a very long empty part before you start recording (if you draw a 128 bars long part, recording will stop at bar 192). You can draw as long as you need, there's no overhead.

    Would be easier just to have it automatically keep recording? Or increase the bar amount after the last part to like 300 bars. Can that be done?

  • @[Deleted User] said:

    @SevenSystems said:

    @[Deleted User] said:
    @SevenSystems can you record longer than 64 bars?

    Yes of course. Xequence just considers 64 bars after the last part to be the end of the song. So, just draw a very long empty part before you start recording (if you draw a 128 bars long part, recording will stop at bar 192). You can draw as long as you need, there's no overhead.

    Would be easier just to have it automatically keep recording? Or increase the bar amount after the last part to like 300 bars. Can that be done?

    It might be feasible, yeah. The whole mechanism dates back to the very beginning of Xequence and various architectural things have been improved since then so it is probably unnecessary nowadays. Will check it!

  • @ExAsperis99 said:

    @SevenSystems said:
    @wim @senhorlampada Haha, I've been wondering for a year now why nobody has ever asked that question :dizzy:

    The reason is that Xequence has been leading a secret double life for quite some time ;)

    I think I was being too coy.
    What exactly is this and when can we play with it?

    @ExAsperis99 said:

    @SevenSystems said:
    @wim @senhorlampada Haha, I've been wondering for a year now why nobody has ever asked that question :dizzy:

    The reason is that Xequence has been leading a secret double life for quite some time ;)

    I think I was being too coy.
    What exactly is this and when can we play with it?

    @ExAsperis99 said:

    @SevenSystems said:
    @wim @senhorlampada Haha, I've been wondering for a year now why nobody has ever asked that question :dizzy:

    The reason is that Xequence has been leading a secret double life for quite some time ;)

    I think I was being too coy.
    What exactly is this and when can we play with it?

    @SevenSystems said:

    @[Deleted User] said:

    @SevenSystems said:

    @[Deleted User] said:
    @SevenSystems can you record longer than 64 bars?

    Yes of course. Xequence just considers 64 bars after the last part to be the end of the song. So, just draw a very long empty part before you start recording (if you draw a 128 bars long part, recording will stop at bar 192). You can draw as long as you need, there's no overhead.

    Would be easier just to have it automatically keep recording? Or increase the bar amount after the last part to like 300 bars. Can that be done?

    It might be feasible, yeah. The whole mechanism dates back to the very beginning of Xequence and various architectural things have been improved since then so it is probably unnecessary nowadays. Will check it!

    I second this. Ableton keeps recording indefinitely. It's one of the main reason I use it as my main Daw.

  • Noob question: How can I trim half a bar from the start of a section? The playhead only moves by whole bars so I can't use the trim tool.

  • edited October 2018

    @SevenSystems said:

    @[Deleted User] said:

    @SevenSystems said:

    @[Deleted User] said:
    @SevenSystems can you record longer than 64 bars?

    Yes of course. Xequence just considers 64 bars after the last part to be the end of the song. So, just draw a very long empty part before you start recording (if you draw a 128 bars long part, recording will stop at bar 192). You can draw as long as you need, there's no overhead.

    Would be easier just to have it automatically keep recording? Or increase the bar amount after the last part to like 300 bars. Can that be done?

    It might be feasible, yeah. The whole mechanism dates back to the very beginning of Xequence and various architectural things have been improved since then so it is probably unnecessary nowadays. Will check it!

    It would be very helpful as like @gonekrazy3000 mentioned I also use Ableton because of this infinite midi recording method, important when you are jamming and don't want to lose the one good bit. I don't think infinite is totally necessary but a much longer amount of bars in recording would be beneficial.

  • @richardyot said:
    Noob question: How can I trim half a bar from the start of a section? The playhead only moves by whole bars so I can't use the trim tool.

    Thats a restriction with the app at the moment. It is on the roadmap to be implemented.

  • @Richtowns said:

    @richardyot said:
    Noob question: How can I trim half a bar from the start of a section? The playhead only moves by whole bars so I can't use the trim tool.

    Thats a restriction with the app at the moment. It is on the roadmap to be implemented.

    OK thanks for the heads-up.

    @SevenSystems IMO that's a really basic thing that I'm going to want to do all the time in the sequencer, and a glaring omission if I may say so. I don't think I can really carry on with Xequence if I'm not able to trim the regions to anything other than single bars.

  • @richardyot sorry about that limitation, I sometimes find it a bit limiting as well... currently, what you can do of course is enter the pianoroll and then delete the events that are in the first half of the first bar.

    A selectable grid for the arranger is on the roadmap and I hope to have it implemented shortly.

Sign In or Register to comment.