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!

1…2425272930…62

Comments

  • horsetrainerhorsetrainer

    @SevenSystems said:
    @Audiojunkie @Tones4Christ I can't promise a built-in audio source for it, but a few configuration options for defining a "Preview MIDI Destination" would certainly be possible, and then Xequence would just send everything that's in the MIDI file to that destination (and just use the channels from the MIDI files themselves)... it's been on the roadmap already, just can't say if / when it will be done. But it's noted :)

    I was contemplating loops when I was exploring the functions in the "drum pads' section of X2. I already touched on the subject of chord pads, and am glad to hear that's already a future consideration.

    But I never mentioned playing loops because I think complication is the bane of iOS usability.

    I think X2 is the fullest featured, easiest to use, most intuitively designed, and most useful MIDI sequencer available for iOS. Just the way it is right now. I like the ideas about additional features...BUT...

    Then I start thinking of all the DAW apps I already own, that are so packed with features that I get so lost every time I try to work in them. I spend more time trying find features than I do making music with the things.

    With X2, I can just open it up and start recording.

    So I think it's wise to weigh every consideration for implementing additional features against a paradigm for ease of use.... It's the bell curve of usability for iOS app design... One can add features to an app that will increase the usability all the way up to the apex at the top of the bell curve, But any more additions beyond that point, and the usability begins to drop off as the amount of features complicate the users ability to navigate and utilize the features of the App.

  • AudiojunkieAudiojunkie

    @horsetrainer said:

    @SevenSystems said:
    @Audiojunkie @Tones4Christ I can't promise a built-in audio source for it, but a few configuration options for defining a "Preview MIDI Destination" would certainly be possible, and then Xequence would just send everything that's in the MIDI file to that destination (and just use the channels from the MIDI files themselves)... it's been on the roadmap already, just can't say if / when it will be done. But it's noted :)

    I was contemplating loops when I was exploring the functions in the "drum pads' section of X2. I already touched on the subject of chord pads, and am glad to hear that's already a future consideration.

    But I never mentioned playing loops because I think complication is the bane of iOS usability.

    I think X2 is the fullest featured, easiest to use, most intuitively designed, and most useful MIDI sequencer available for iOS. Just the way it is right now. I like the ideas about additional features...BUT...

    Then I start thinking of all the DAW apps I already own, that are so packed with features that I get so lost every time I try to work in them. I spend more time trying find features than I do making music with the things.

    With X2, I can just open it up and start recording.

    So I think it's wise to weigh every consideration for implementing additional features against a paradigm for ease of use.... It's the bell curve of usability for iOS app design... One can add features to an app that will increase the usability all the way up to the apex at the top of the bell curve, But any more additions beyond that point, and the usability begins to drop off as the amount of features complicate the users ability to navigate and utilize the features of the App.

    There is truth to what you say. However, name one app--any app, that does this feature request well. None of the DAWs do.

  • RajahPRajahP
    edited July 2019

    @rs2000 said:

    @RajahP said:
    Seems like Gadget does a nice midi import these days... just saying.. 😎

    "Nice" depends on what you need.
    Importing a linear track will end up in equal-sized patterns which is often not what you want.
    Some preparation of your MIDI file in Xequence 2 might be necessary.

    Actually, it’s exactly what ‘we’ requested earlier in the thread.. It is useful for getting midi-loops into Maschine etc. on desktop.. And Gadget’s Ableton Export is a blessing..

  • rs2000rs2000

    @RajahP said:

    @rs2000 said:

    @RajahP said:
    Seems like Gadget does a nice midi import these days... just saying.. 😎

    "Nice" depends on what you need.
    Importing a linear track will end up in equal-sized patterns which is often not what you want.
    Some preparation of your MIDI file in Xequence 2 might be necessary.

    Actually, it’s exactly what ‘we’ requested earlier in the thread.. It is useful for getting midi-loops into Maschine etc. on desktop.. And Gadget’s Ableton Export is a blessing..

    I like it the way it is. Not everybody does tho :#

  • Antkn33Antkn33
    edited July 2019

    Thanks

    @SevenSystems said:

    @Antkn33 said:
    I would really like the ability to insert a clip anywhere in the timeline. For example if I want the intro the be four bars longer it seems now they I have to move all the later sections to create four more bars. It would be great to be able to put the Play head at the position I want and be able to insert four bars( or whatever the case is ).

    Yes, thanks for the reminder -- an "Insert Time" feature is something that wouldn't be terribly hard to add and is indeed very useful. Of course, if the point where you want to insert time goes through existing clips, these would need to be automatically split there as well.

    Similarly, a complementary "Delete time" function would then be logic(al) as well.

  • RajahPRajahP

    @rs2000 said:

    @RajahP said:

    @rs2000 said:

    @RajahP said:
    Seems like Gadget does a nice midi import these days... just saying.. 😎

    "Nice" depends on what you need.
    Importing a linear track will end up in equal-sized patterns which is often not what you want.
    Some preparation of your MIDI file in Xequence 2 might be necessary.

    Actually, it’s exactly what ‘we’ requested earlier in the thread.. It is useful for getting midi-loops into Maschine etc. on desktop.. And Gadget’s Ableton Export is a blessing..

    I like it the way it is. Not everybody does tho :#

    Well, there is a solution.. and it’s pretty nice importing a project into Gadget and using its instruments..
    And yes, I like/love this app too.. 😬

  • wimwim

    @Audiojunkie said:

    @horsetrainer said:

    @SevenSystems said:
    @Audiojunkie @Tones4Christ I can't promise a built-in audio source for it, but a few configuration options for defining a "Preview MIDI Destination" would certainly be possible, and then Xequence would just send everything that's in the MIDI file to that destination (and just use the channels from the MIDI files themselves)... it's been on the roadmap already, just can't say if / when it will be done. But it's noted :)

    I was contemplating loops when I was exploring the functions in the "drum pads' section of X2. I already touched on the subject of chord pads, and am glad to hear that's already a future consideration.

    But I never mentioned playing loops because I think complication is the bane of iOS usability.

    I think X2 is the fullest featured, easiest to use, most intuitively designed, and most useful MIDI sequencer available for iOS. Just the way it is right now. I like the ideas about additional features...BUT...

    Then I start thinking of all the DAW apps I already own, that are so packed with features that I get so lost every time I try to work in them. I spend more time trying find features than I do making music with the things.

    With X2, I can just open it up and start recording.

    So I think it's wise to weigh every consideration for implementing additional features against a paradigm for ease of use.... It's the bell curve of usability for iOS app design... One can add features to an app that will increase the usability all the way up to the apex at the top of the bell curve, But any more additions beyond that point, and the usability begins to drop off as the amount of features complicate the users ability to navigate and utilize the features of the App.

    There is truth to what you say. However, name one app--any app, that does this feature request well. None of the DAWs do.

    The most likely candidate for this IMO is AudioShare. It’s the best music librarian on iOS, and it already has the ability to “preview” midi files, but it doesn’t output anything listenable really. All @j_liljedahl would need to do would be to add a GM soundfont and the ability to select the instrument from it for playback preview. Or, even just provide a quick pop up asking if the preview should be played on drums or piano.

  • wimwim

    @audio_DT said:

    @SevenSystems said:
    @audio_DT No, it's not that automatic :) It just means that if Xequence during recording receives a controller number that is not yet set up on the current instrument, it will add it to the instrument.

    Thanks. I'm not concerned because it's easy enough to do manually - but I must confess that I still don't understand what you mean by 'It just means that if Xequence during recording receives a controller number that is not yet set up on the current instrument, it will add it to the instrument.' What is added to what, and where? Sorry, you must be getting frustrated by me now! It's no biggie, anyway, because, as I say, setting CCs up is easy enough - it's just my misunderstanding that is doing my head in.

    I think I see the confusion here. The key word here is “receives”. When you change something in AUM that doesn’t necessarily mean Xequence is receiving it. In order for Xequence to receive something, it has to be sent out of AUM to Xequence.

    So, for instance if you have a Rozeta LFO in AUM and you route it’s output to Xequence, that will be added. But if you move a control on an app and want that to be added in Xequence, two things have to be true. First, the app needs to have MIDI out (most don’t), and second, that output needs to be routed to Xequence.

    I hope that kind of makes sense. MIDI isn’t a two way connection, unless an app supports it and it’s set up that way. So, setting up an app to be controlled by Xequence is a one-way street. The two aren’t linked two ways.

    How this could work is if you routed a controller to both the app and Xequence. For instance, if I set up my NanoKEY Studio to send both to Xequence and to an app, the controller’s cc messages will be received by Xequence, added, and recorded, while at the same time the controller will be affecting the app.

    Since I can’t readily make a picture that would illustrate this easily, maybe picturing midi cabling would help. Midi cables are one-way. You connect the Out from one device to the In from another. Now the first device can send to the second. But the second can’t send to the first because there’s no cable sending from the second device’s Out port to the first device’s In port. You just don’t get two-way communication over a single cable.

    Virtual midi is the same way. Except that many apps, and most FX, don’t even have an out port. It’s like a hardware device with an IN only jack.

    I hope that helps. If I had a little more ambition I’d try to illustrate it. ;)

  • Tones4ChristTones4Christ

    Guys I was able to have Sweet Midi Player send midi files to X2 but when imported X2 groups the entire midi file into a single track. These midi files have Bass, leads and Drums which were used for arranger keyboards all are GM standard though.

  • horsetrainerhorsetrainer
    edited July 2019

    @Audiojunkie said:

    @horsetrainer said:

    @SevenSystems said:
    @Audiojunkie @Tones4Christ I can't promise a built-in audio source for it, but a few configuration options for defining a "Preview MIDI Destination" would certainly be possible, and then Xequence would just send everything that's in the MIDI file to that destination (and just use the channels from the MIDI files themselves)... it's been on the roadmap already, just can't say if / when it will be done. But it's noted :)

    I was contemplating loops when I was exploring the functions in the "drum pads' section of X2. I already touched on the subject of chord pads, and am glad to hear that's already a future consideration.

    But I never mentioned playing loops because I think complication is the bane of iOS usability.

    I think X2 is the fullest featured, easiest to use, most intuitively designed, and most useful MIDI sequencer available for iOS. Just the way it is right now. I like the ideas about additional features...BUT...

    Then I start thinking of all the DAW apps I already own, that are so packed with features that I get so lost every time I try to work in them. I spend more time trying find features than I do making music with the things.

    With X2, I can just open it up and start recording.

    So I think it's wise to weigh every consideration for implementing additional features against a paradigm for ease of use.... It's the bell curve of usability for iOS app design... One can add features to an app that will increase the usability all the way up to the apex at the top of the bell curve, But any more additions beyond that point, and the usability begins to drop off as the amount of features complicate the users ability to navigate and utilize the features of the App.

    There is truth to what you say. However, name one app--any app, that does this feature request well. None of the DAWs do.

    I don't know of any iOS App with a pattern feature that didn't make me frustrated when I tried to get it to do the things that I wanted to use it for.

    Hypothetically, lets say we (we in general) could design a pattern playing feature into X2... What would we want it to do?

    These are my thoughts about that.

    It would be a MIDI only pattern feature.
    I'd want it to have a grid of pads that I can use to trigger patterns while I have X2 recording selected pattern output into a track.

    The Pattern "section" would use the same "sequencer engine" that X2 uses for its tracks.
    Each Pattern "Pad" would be linked to it's own "track" in a part of the App Called "The pattern track section".
    The pattern section, and the Sequencer section, would both share the same tempo setting in the main transport.

    Each pad could be selected for either recording into, or editing.
    Each pad would have an adjustable length from (something like) 1 to 8 bars.

    Each Pad could be recorded into by selecting it to highlight it, then using the general transport controls to record notes into the pattern. Or by selecting the Pad to bring up a "track view" for that pad, where all of the general X2 Sequencer recording and editing features would be available for that pattern in the "track view" of the pattern.

    The "track view" for a pattern would have the track transport controls and all other adjustable parameters located at the top half of the window. The lower half would have a piano keyboard layout, switchable with a chord pad layout.

    All patterns would be savable as either individual midi files, or as a collection of patterns assigned to any particular pad layout.

    In the main X2 window, Play Patterns can be selected, and this will bring up a grid of pre-programed pads on the lower half of the screen. The patterns can either be recorded live into X2 tracks, or alternatively and pattern containing pad can be dragged and dropped directly into any track of the X2 Sequencer.

    Additionally. With "Pattern drag and drop enabled" any section of track in the X2 Sequencer can first be split into a whole number of measures, and then dragged and dropped into any available empty pattern pads on the lower half go the screen.

    That's all I can think of for now. I have to go do stuff.

    But you know what I'm thinking. @SevenSystems

    Could you turn X2 into The.. "X2- MIDI Pattern Sequencer".. as a separate application?

    I wish I knew more about what already exists for iOS in the way of Pattern composition tools.
    Garage band has a feature, but I find it frustrating to use. I have Groovebox, but is audio only as far as I can tell, no MIDI.

    Is there any Pattern App out there that provides an intuitive, composition orientated user interface, with MIDI editing features comparable to those of X2?

  • wimwim
    edited July 2019

    @horsetrainer said:
    Is there any Pattern App out there that provides an intuitive, composition orientated user interface, with MIDI editing features comparable to those of X2?

    Sounds like kinda like Stagelight to me.

    Midi Out on it is broken at this point, but otherwise it comes close to what I understand from a quick read of your post.

  • SevenSystemsSevenSystems

    @wim said:
    So, for instance if you have a Rozeta LFO in AUM and you route it’s output to Xequence, that will be added. But if you move a control on an app and want that to be added in Xequence, two things have to be true. First, the app needs to have MIDI out (most don’t), and second, that output needs to be routed to Xequence.

    And third, Xequence needs to be recording! I wonder if it would make sense to extend this so that new controllers are always recognized and offered to be added. Kind of an "always-on MIDI learn". Have to think about it.

  • SevenSystemsSevenSystems

    @Tones4Christ said:
    Guys I was able to have Sweet Midi Player send midi files to X2 but when imported X2 groups the entire midi file into a single track. These midi files have Bass, leads and Drums which were used for arranger keyboards all are GM standard though.

    Then that file probably only had a single track. It may have the instruments on separate channels, but that doesn't matter when importing to Xequence -- it will only separate by TRACKS, NOT channels. It's something that will possible be made configurable in a future version.

  • SevenSystemsSevenSystems
    edited July 2019

    @horsetrainer, a project almost exactly like what you describe was started about a year ago, but other stuff has taken priority and I also felt a bit lost because I'm not a "live" person at all so I didn't really know what I was doing, semantically.

    (the pads are freely sizable, adjustable etc., clips from Xequence can be sent to the looper app with a tap... maybe I'll pursue this further at some point when the Earth's rotation slows even further and my days finally got 48 hours ;))

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • Tones4ChristTones4Christ

    Yeah you’re right they all have different midi channels. I checked when I selected different channels in X2 and the midi player played a different instrument.

    Would really love the option to select that as one imports the midi file just like it asks if you want different tracks for the controllers. Please that would be so awesome! And the only other app that can do this is Cubasis.

    Thanks for considering it❤️❤️❤️🙏👍🏼🎹😇

  • Tones4ChristTones4Christ

    https://www.dropbox.com/s/twwjuyjg9873t6k/16BtRockBld70..mid?dl=0

    Here’s the midi file I was trying to extract into X2:

  • SevenSystemsSevenSystems

    @Tones4Christ said:
    https://www.dropbox.com/s/twwjuyjg9873t6k/16BtRockBld70..mid?dl=0

    Here’s the midi file I was trying to extract into X2:

    Thanks, will have a look why it gives problems!

  • horsetrainerhorsetrainer
    edited July 2019

    @wim said:

    @horsetrainer said:
    Is there any Pattern App out there that provides an intuitive, composition orientated user interface, with MIDI editing features comparable to those of X2?

    Sounds like kinda like Stagelight to me.

    Midi Out on it is broken at this point, but otherwise it comes close to what I understand from a quick read of your post.

    Thanks for directing me to look at that.
    I can see that it has interesting pattern capacities, but it does not seem to be anything close to what I'd call easy to use with an intuitive user interface. Especially when I long tapped on a pattern and found a MIDI export option... When clicked on brought up what appeared to look like a proprietary iOS file system manager window, that apparently let me navigate into the deepest nether regions of the iOS operating system (places I think should best be left inaccessible).

    But since I could not recall any saved midi files, I'm guessing the ability to save files is probably part of the full feature in-app purchase.

    I think this further validates my earlier point about over-complexity being the bane of App usability.

    I'm much rather have a number of individual very well designed easy to understand Apps devoted to doing one singular function very well. Than one complicated App that attempts to pack so many feature into one space that remembering how to access those features dominates the mind so much that it messes up the "karma" of creating music.

    @SevenSystems... I think you already deserve some type of developer equivalent of a grammy award for your production of X2. I think if people ask you to do more... it's only because they like what you already did.

    Maybe you could have yourself cloned. That capability is more likely to exist long before the earth rotation slows to 48 hour days.... The sun will probably have gone supernova by then anyhow. ;)

  • SevenSystemsSevenSystems

    @horsetrainer said:
    @SevenSystems... I think you already deserve some type of developer equivalent of a grammy award for your production of X2. I think if people ask you to do more... it's only because they like what you already did.

    Yes, thanks a lot and trust me, I don't take feature requests as an offense 😉 as long as users don't take the impossibility of adding them all as one, either.

    Maybe you could have yourself cloned.

    Unfortunately, even the closest realistic and already possible equivalent for doing so has been extremely unsuccessful for me so far, so I have to disappoint you, it's highly unlikely anything like that will happen 😂

  • Tones4ChristTones4Christ

    Yeah I agree! I think if it’s easier to just include the option to extract the incoming midi file by tracks per midi channels that would rock. No need to code the midi player thing imho as there are other apps that already do this such as Sweet Midi Player. But thanks so much for considering it.👍🏼😌

    @SevenSystems said:

    @horsetrainer said:
    @SevenSystems... I think you already deserve some type of developer equivalent of a grammy award for your production of X2. I think if people ask you to do more... it's only because they like what you already did.

    Yes, thanks a lot and trust me, I don't take feature requests as an offense 😉 as long as users don't take the impossibility of adding them all as one, either.

    Maybe you could have yourself cloned.

    Unfortunately, even the closest realistic and already possible equivalent for doing so has been extremely unsuccessful for me so far, so I have to disappoint you, it's highly unlikely anything like that will happen 😂

  • slicetwoslicetwo
    edited July 2019

    Has anyone gotten Elastic Drums working with Xequence? I have them linked via Ableton link and a channel in Xequence routed to ED with the proper template, but I'm getting no sound.

    Same thing with patterning. Though I got that working eventually, I don't remember how.

  • rs2000rs2000

    @slicetwo said:
    Has anyone gotten Elastic Drums working with Xequence? I have them linked via Ableton link and a channel in Xequence routed to ED with the proper template, but I'm getting no sound.

    Same thing with patterning. Though I got that working eventually, I don't remember how.

    ED background audio enabled?

  • wimwim

    It’s working for me with ED in AudioBus, using AudioBus Midi. I had to change the drum map though. I could also have midi learned the pads I guess.

  • audio_DTaudio_DT

    @wim said:

    @audio_DT said:

    @SevenSystems said:
    @audio_DT No, it's not that automatic :) It just means that if Xequence during recording receives a controller number that is not yet set up on the current instrument, it will add it to the instrument.

    Thanks. I'm not concerned because it's easy enough to do manually - but I must confess that I still don't understand what you mean by 'It just means that if Xequence during recording receives a controller number that is not yet set up on the current instrument, it will add it to the instrument.' What is added to what, and where? Sorry, you must be getting frustrated by me now! It's no biggie, anyway, because, as I say, setting CCs up is easy enough - it's just my misunderstanding that is doing my head in.

    I think I see the confusion here. The key word here is “receives”. When you change something in AUM that doesn’t necessarily mean Xequence is receiving it. In order for Xequence to receive something, it has to be sent out of AUM to Xequence.

    So, for instance if you have a Rozeta LFO in AUM and you route it’s output to Xequence, that will be added. But if you move a control on an app and want that to be added in Xequence, two things have to be true. First, the app needs to have MIDI out (most don’t), and second, that output needs to be routed to Xequence.

    I hope that kind of makes sense. MIDI isn’t a two way connection, unless an app supports it and it’s set up that way. So, setting up an app to be controlled by Xequence is a one-way street. The two aren’t linked two ways.

    How this could work is if you routed a controller to both the app and Xequence. For instance, if I set up my NanoKEY Studio to send both to Xequence and to an app, the controller’s cc messages will be received by Xequence, added, and recorded, while at the same time the controller will be affecting the app.

    Since I can’t readily make a picture that would illustrate this easily, maybe picturing midi cabling would help. Midi cables are one-way. You connect the Out from one device to the In from another. Now the first device can send to the second. But the second can’t send to the first because there’s no cable sending from the second device’s Out port to the first device’s In port. You just don’t get two-way communication over a single cable.

    Virtual midi is the same way. Except that many apps, and most FX, don’t even have an out port. It’s like a hardware device with an IN only jack.

    I hope that helps. If I had a little more ambition I’d try to illustrate it. ;)

    Thanks @wim, that’s very helpful, and much appreciated. I think I’m grasping the concept more now, so thanks for the assistance. You should be a paid operative on here! Cheers.

  • slicetwoslicetwo
    edited July 2019

    @rs2000 said:

    @slicetwo said:
    Has anyone gotten Elastic Drums working with Xequence? I have them linked via Ableton link and a channel in Xequence routed to ED with the proper template, but I'm getting no sound.

    Same thing with patterning. Though I got that working eventually, I don't remember how.

    ED background audio enabled?

    Turns out I had to do MIDI LEARN for all the notes. Wonky.

  • SevenSystemsSevenSystems

    @zah said:
    @SevenSystems or anyone

    User error probably, but I have an issue with disappearing midi notes:

    Lay down a drum pattern - ie. kik snare hihats
    Decide later the drums need more midi events
    Record ie. hand claps. Duplicating that drum clip plays back only the handclaps

    Open up in editor - only the handclaps are visible, but all midi notes are heard

    You've probably recorded the second clip over the first so that they overlap.

    Can you try this? :)

  • SevenSystemsSevenSystems
    edited July 2019

    @zah: By opening that clip before recording.

  • SevenSystemsSevenSystems

    @zah said:

    @SevenSystems said:
    @zah: By opening that clip before recording.

    That's an extra 2 steps to get into the piano roll and get back to arranging. :(

    Why not an option to record into a clip in sequencer?
    This should be the default. And if not, an option somewhere to make it your default.

    You can just leave the pianoroll editor open, there's no need to close it between recordings.

    If you do need to stay in the arranger, it is easy to merge newly recorded clips with existing ones by just selecting the overlapping clips by tapping and holding and then using PROCESS -> Join.

  • SevenSystemsSevenSystems

    @zah said:

    @SevenSystems said:

    @zah said:

    @SevenSystems said:
    @zah: By opening that clip before recording.

    That's an extra 2 steps to get into the piano roll and get back to arranging. :(

    Why not an option to record into a clip in sequencer?
    This should be the default. And if not, an option somewhere to make it your default.

    You can just leave the pianoroll editor open, there's no need to close it between recordings.

    If you do need to stay in the arranger, it is easy to merge newly recorded clips with existing ones by just selecting the overlapping clips by tapping and holding and then using PROCESS -> Join.

    @SevenSystems Joining does not merge the clips into one.

    Example 1
    I record some midi events . I then record more midi events. I now have an overlapping clip. I select/Process/Join them, but Xequence says to select two clips.

    OK, maybe there's a bug there -- could you make a short video that shows the process, so that I can check if there's anything that you're doing differently?

    For reference, here's an example of what I do:

    Example 2
    I create a sub-track and record new midi events. I now have two vertical clips with separate midi notes that I wish to join. I select both, press Process and Join. I still have two clips.

    Yes, the clips have to be overlapping on the same tracks in order to be merged. You would have to move all clips that you would like to join / merge onto the same track.

Sign In or Register to comment.