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!

1262729313262

Comments

  • @sisterkate OK, glad to have your input on this. So does "Harmony Pro" have a fully correct implementation of arbitrary time signatures? Because if you "approve" it, I could use it as a reference implementation for Xequence.

  • @zah, thanks for reporting the vertical movement issue. That's the first time I have seen that. Could you possibly send me the project file where that occurs? I'll PM you my email.

    And good points about splitting notes -- I shall add that to the roadmap for a mid- to short-term addition.

  • edited July 2019

    @SevenSystems said:
    @sisterkate OK, glad to have your input on this. So does "Harmony Pro" have a fully correct implementation of arbitrary time signatures? Because if you "approve" it, I could use it as a reference implementation for Xequence.

    @SevenSystems great

    Harmony Pro is correct because (just like the Notion app) it was made for classical composing and as specialist notation apps they need to follow established western musical conventions. While it's less comfortable and harder to use as a sequencer then X2, it has a comprehensive bpm/metronome page and modest price without the handwriting in/app purchase

    But DrumStudio I think is a better and closer reference as aimed at popular styles, offers all of HPro's time/sig features and uses piano roll type visual representation. It is the only affordable and easy to use drum machine I could find with custom time/sig choice and musically correct on ios. The bpm/time signature page shines with simplicity yet has full features even including accented beats for the metronome. It has the correct implementation for time sigsnatures including the the odd ones. This app focuses on it's primary purpose as a rhythm composer for drums/percussions in depth also with humanising, using ghost notes etc...
    It also has a super useful groove function unfortunately seems only for playback from the app.

    This page has helpful audio samples to hear the feel of the various time/signatures
    https://en.wikipedia.org/wiki/Time_signature.

  • @sisterkate thanks so much, that's great. Will note both of these as references for future improvement.

  • I can't seem to get the Chord Mode in Xequence 2's in built keyboards to actually play chords (or record in to the piano roll) - It just seems to play and record the route note I hit.

    Do I need to do something more than simply activate that mode on the little pop up in keyboard mode? - I can do it fine from feeding Xequence 2 with external apps such as Chordmaps or KB1 or even from AUM with Xequence Keys AUv3

    Note - Ipad OS. Ipad2018 Pro

  • @SonicNeutronic said:
    I can't seem to get the Chord Mode in Xequence 2's in built keyboards to actually play chords (or record in to the piano roll) - It just seems to play and record the route note I hit.

    Do I need to do something more than simply activate that mode on the little pop up in keyboard mode? - I can do it fine from feeding Xequence 2 with external apps such as Chordmaps or KB1 or even from AUM with Xequence Keys AUv3

    Note - Ipad OS. Ipad2018 Pro

    Sorry, this is a common misunderstanding -- "Chords" and "Triads" are just scale categories that contain scales with the respective chords' notes... i.e. all keys shown when you select "Triads" -> "Major" belong to the major chord on the current root note.

    This should probably somehow be made clearer in the interface.

    Apart from that though, actual configurable chord pads are high on the list of "wants" and will probably arrive in a future update!

  • edited July 2019

    @SevenSystems Aaaaaaa I see now. Thank you for the quick clear-up and no more wasted time for me lol... haha - Something Chordmaps2ISH built into this would be sublime lol - I cant play a single key so need every app on earth ;)

  • @SonicNeutronic said:
    @SevenSystems Aaaaaaa I see now. Thank you for the quick clear-up and no more wasted time for me lol... haha - Something Chordmaps2ISH built into this would be sublime lol - I cant play a single key so need every app on earth ;)

    This will probably be added to the FAQ so people might find this answer more quickly 🙂

    Hope that actual chord pads arrive soon! (I myself belong in the same category of keyboard playing competence 😉)

  • @SevenSystems said:

    @SonicNeutronic said:
    @SevenSystems Aaaaaaa I see now. Thank you for the quick clear-up and no more wasted time for me lol... haha - Something Chordmaps2ISH built into this would be sublime lol - I cant play a single key so need every app on earth ;)

    This will probably be added to the FAQ so people might find this answer more quickly 🙂

    Hope that actual chord pads arrive soon! (I myself belong in the same category of keyboard playing competence 😉)

    What??? You can’t transfer that clickty clack from your IBM to the ivory 🎹? 😂😂

  • @SevenSystems, thank you for the best midi DAW on iOS!
    Are you planning to add some kind of seamless switch between loops?
    For example I select one part of a song and hit play then I select another part and as for now the app pause for a moment and starts after that. But it would be great to have an option so the app will play current selection until the end and then start new one immediately after that.

  • @Eye0sStudios said:

    @SevenSystems said:

    @SonicNeutronic said:
    @SevenSystems Aaaaaaa I see now. Thank you for the quick clear-up and no more wasted time for me lol... haha - Something Chordmaps2ISH built into this would be sublime lol - I cant play a single key so need every app on earth ;)

    This will probably be added to the FAQ so people might find this answer more quickly 🙂

    Hope that actual chord pads arrive soon! (I myself belong in the same category of keyboard playing competence 😉)

    What??? You can’t transfer that clickty clack from your IBM to the ivory 🎹? 😂😂

    Oh I used to be an okay piano and keyboard player when I was younger 😉 but that didn't translate very well to a touchscreen.

    @clowm said:
    @SevenSystems, thank you for the best midi DAW on iOS!
    Are you planning to add some kind of seamless switch between loops?
    For example I select one part of a song and hit play then I select another part and as for now the app pause for a moment and starts after that. But it would be great to have an option so the app will play current selection until the end and then start new one immediately after that.

    Thanks for the praise 🙂 I have to admit that live use (which seamless loop switching essentially is meant for) is not a priority for Xequence and it's not very likely that it will be added.

    It has become easier to implement in Xequence 2, but I don't know if/when development time for it can be allocated amongst the literally dozens of other features that are waiting on the roadmap.

    Sorry to say 😳

  • @clowm said:
    @SevenSystems, thank you for the best midi DAW on iOS!
    Are you planning to add some kind of seamless switch between loops?
    For example I select one part of a song and hit play then I select another part and as for now the app pause for a moment and starts after that. But it would be great to have an option so the app will play current selection until the end and then start new one immediately after that.

    Thanks for the praise 🙂 I have to admit that live use (which seamless loop switching essentially is meant for) is not a priority for Xequence and it's not very likely that it will be added.

    It has become easier to implement in Xequence 2, but I don't know if/when development time for it can be allocated amongst the literally dozens of other features that are waiting on the roadmap.

    Sorry to say 😳

    Oh, thanks for the fast reply. That's ok. Probably I should just practice more instead of asking for more features 🙂 Also, as a developer I can volunteer to implement it on my free time if it possible.

  • edited July 2019

    @SevenSystems said:
    @sisterkate thanks so much, that's great. Will note both of these as references for future improvement.

    @SevenSystems I just realised the notation app is not called Harmony pro it is called Symphony Pro

  • @SevenSystems I am noticing that my Xequence sessions are having trouble with tempo saving. I use it mostly now with AUM and even if I save my Xequence session again and again at 82bpm.. more then often it will open at 120bpm. Any thoughts on why this is happening?

  • @Eye0sStudios said:
    @SevenSystems I am noticing that my Xequence sessions are having trouble with tempo saving. I use it mostly now with AUM and even if I save my Xequence session again and again at 82bpm.. more then often it will open at 120bpm. Any thoughts on why this is happening?

    Yes, this is unfortunately a side effect of Ableton Link -- whenever that is active, any other Link-enabled entity will be able to reset the tempo.

    I'm not sure if this can be solved in an elegant way -- many other apps also struggle with this.

    There may also be an issue in how Xequence handles this of course... do you know any other Link-enabled app that handles this better? I would then have a look.

  • @SevenSystems said:

    @Eye0sStudios said:
    @SevenSystems I am noticing that my Xequence sessions are having trouble with tempo saving. I use it mostly now with AUM and even if I save my Xequence session again and again at 82bpm.. more then often it will open at 120bpm. Any thoughts on why this is happening?

    Yes, this is unfortunately a side effect of Ableton Link -- whenever that is active, any other Link-enabled entity will be able to reset the tempo.

    I'm not sure if this can be solved in an elegant way -- many other apps also struggle with this.

    There may also be an issue in how Xequence handles this of course... do you know any other Link-enabled app that handles this better? I would then have a look.

    So even though my AUM session is at 82... and when you first open AUM it goes to 120.. but if I wait till my project in AUM is completely loaded it will show 82. Then after that when I open Xequence it still links at 120? Where is it getting that info from if my AUM session is already down at the right tempo?

    Just curious.

  • @clowm said:
    Oh, thanks for the fast reply. That's ok. Probably I should just practice more instead of asking for more features 🙂 Also, as a developer I can volunteer to implement it on my free time if it possible.

    Thanks, that is a much more difficult proposition than what you realize though, probably! :)

  • @sisterkate said:

    @SevenSystems said:
    @sisterkate thanks so much, that's great. Will note both of these as references for future improvement.

    @SevenSystems I just realised the notation app is not called Harmony pro it is called Symphony Pro

    Thanks, I've now noted DrumStudio as a reference anyway!

  • edited July 2019

    @Eye0sStudios said:

    @SevenSystems said:

    @Eye0sStudios said:
    @SevenSystems I am noticing that my Xequence sessions are having trouble with tempo saving. I use it mostly now with AUM and even if I save my Xequence session again and again at 82bpm.. more then often it will open at 120bpm. Any thoughts on why this is happening?

    Yes, this is unfortunately a side effect of Ableton Link -- whenever that is active, any other Link-enabled entity will be able to reset the tempo.

    I'm not sure if this can be solved in an elegant way -- many other apps also struggle with this.

    There may also be an issue in how Xequence handles this of course... do you know any other Link-enabled app that handles this better? I would then have a look.

    So even though my AUM session is at 82... and when you first open AUM it goes to 120.. but if I wait till my project in AUM is completely loaded it will show 82. Then after that when I open Xequence it still links at 120? Where is it getting that info from if my AUM session is already down at the right tempo?

    Just curious.

    I've just tried to reproduce the problem -- here's what I did:

    • Created a Xequence project, set it at 100 BPM and saved.
    • Created an AUM project, set it to 100 BPM and saved.
    • Closed both apps.
    • Opened AUM, opens at 120 BPM.
    • Loaded the AUM project, BPM is now at 100.
    • Opened Xequence, is immediately at 100 BPM (the Link session tempo)
    • Loaded the project, BPM stays at 100.

    I think this is correct behaviour, but maybe you did something differently than me? Here's a video:

    Sorry, Vimeo seems to be having problems... maybe the video will appear sometime (a video upload / hosting feature on this forum would be AMAZING! :))

  • @SevenSystems Any chance of adding simple increment/decrement arrows to the program change window?

    It would make things SO much easier when auditioning/changing patches. I'm thinking just a small button on top and bottom of each of the 4 value fields would be perfect.

    The current method (tapping on a field, bringing up the OS keyboard, deleting the current value, typing in the new value, closing the keyboard) is very cumbersome when, for example, trying to pick a bass sound from amongst 60 consecutive presets.

    Other than that small workflow niggle, I've really been enjoying Xequence 2 :)

  • @busker said:
    @SevenSystems Any chance of adding simple increment/decrement arrows to the program change window?

    It would make things SO much easier when auditioning/changing patches. I'm thinking just a small button on top and bottom of each of the 4 value fields would be perfect.

    The current method (tapping on a field, bringing up the OS keyboard, deleting the current value, typing in the new value, closing the keyboard) is very cumbersome when, for example, trying to pick a bass sound from amongst 60 consecutive presets.

    Other than that small workflow niggle, I've really been enjoying Xequence 2 :)

    Oh, you mean the ability to send program changes LIVE from that dialog? That's not its original intention, but it certainly sounds useful... I would have expected users to make their sound choices in the target app / on the hardware device itself, but this seems like a valid little addition.

  • @SevenSystems I do the same with your steps. At some point it goes out of whack. It might be maybe I open something else. No worries I make notes on what my projects are. But the other day not paying attention and I am man this sounds like crap..... no worries. Your still the best. 😀

  • edited July 2019

    @SevenSystems said:

    @busker said:
    @SevenSystems Any chance of adding simple increment/decrement arrows to the program change window?

    It would make things SO much easier when auditioning/changing patches. I'm thinking just a small button on top and bottom of each of the 4 value fields would be perfect.

    The current method (tapping on a field, bringing up the OS keyboard, deleting the current value, typing in the new value, closing the keyboard) is very cumbersome when, for example, trying to pick a bass sound from amongst 60 consecutive presets.

    Other than that small workflow niggle, I've really been enjoying Xequence 2 :)

    Oh, you mean the ability to send program changes LIVE from that dialog? That's not its original intention, but it certainly sounds useful... I would have expected users to make their sound choices in the target app / on the hardware device itself, but this seems like a valid little addition.

    Yes, being able to send program changes live from there would be fantastic! (In addition to the increment buttons :smile: )

    I understand what you mean about auditioning from the sound source itself, but let me give you a use case:

    I have some default project templates setup with standard instruments, so I can jump right in when inspiration strikes
    (eg. drums, bass, keys). Each track has a PC set at the start to select the corresponding default instrument.

    Once I have some parts laid down, I might want to start changing the sounds to better match the feel of the song. I could hit play in the sequencer and then switch to the sound source to change the patch, and then find something I like.

    Once I switch back to Xequence though, I'll usually want to jump around between different sections to get a feel for how they sound with the new patch, maybe change a few notes, etc.

    The problem is that after stopping the sequencer, the existing program change will reset the instrument as soon as you hit play again. So I need to either remember to delete the existing program change(s) every time, or go into the program change dialogue and edit it to reflect the instrument I selected in the sound source (which can be convoluted once you get into banks/msb/lsb). Then if I want to try other sounds, I have to do this all over again.

    Another issue with selecting patches from the sound source while looping in the sequencer is that if something sounds good and I'm satisfied with it, I'll often listen to it play for a minute or 2, and then forget that I haven't updated the program changes in Xequence before saving and closing.

    I don't think my workflow is particularly unusual, so I hope you can see how being able to more easily modify program changes within Xequence itself would resolve these issues nicely :)

  • edited July 2019

    @Eye0sStudios said:

    @SevenSystems said:

    @Eye0sStudios said:
    @SevenSystems I am noticing that my Xequence sessions are having trouble with tempo saving. I use it mostly now with AUM and even if I save my Xequence session again and again at 82bpm.. more then often it will open at 120bpm. Any thoughts on why this is happening?

    Yes, this is unfortunately a side effect of Ableton Link -- whenever that is active, any other Link-enabled entity will be able to reset the tempo.

    I'm not sure if this can be solved in an elegant way -- many other apps also struggle with this.

    There may also be an issue in how Xequence handles this of course... do you know any other Link-enabled app that handles this better? I would then have a look.

    So even though my AUM session is at 82... and when you first open AUM it goes to 120.. but if I wait till my project in AUM is completely loaded it will show 82. Then after that when I open Xequence it still links at 120? Where is it getting that info from if my AUM session is already down at the right tempo?

    Just curious.

    I was having similar issues. Ableton Link really needs a "keep master option."

    Xequence 2 kept reverting to a tempo of 127 that Patterning 2 had set in an old project even though it had long been closed and AUM was set at 103. It got too difficult to recreate and explain the issue so I live with it.

  • I was flummoxed by a strange Link timing issue on my iPad at one point. I finally discovered that it was caused by a forgotten Ableton Live session left open on my PC ... that was in the other room and had just been sitting there for weeks.

    Now I only turn on Link when I know I need it, and disable it afterward.

  • @BroCoast said:

    @Eye0sStudios said:

    @SevenSystems said:

    @Eye0sStudios said:
    @SevenSystems I am noticing that my Xequence sessions are having trouble with tempo saving. I use it mostly now with AUM and even if I save my Xequence session again and again at 82bpm.. more then often it will open at 120bpm. Any thoughts on why this is happening?

    Yes, this is unfortunately a side effect of Ableton Link -- whenever that is active, any other Link-enabled entity will be able to reset the tempo.

    I'm not sure if this can be solved in an elegant way -- many other apps also struggle with this.

    There may also be an issue in how Xequence handles this of course... do you know any other Link-enabled app that handles this better? I would then have a look.

    So even though my AUM session is at 82... and when you first open AUM it goes to 120.. but if I wait till my project in AUM is completely loaded it will show 82. Then after that when I open Xequence it still links at 120? Where is it getting that info from if my AUM session is already down at the right tempo?

    Just curious.

    I was having similar issues. Ableton Link really needs a "keep master option."

    Xequence 2 kept reverting to a tempo of 127 that Patterning 2 had set in an old project even though it had long been closed and AUM was set at 103. It got too difficult to recreate and explain the issue so I live with it.

    Man thank God. I thought I was having flashbacks to my Rave Days.

  • @Eye0sStudios said:

    @BroCoast said:

    @Eye0sStudios said:

    @SevenSystems said:

    @Eye0sStudios said:
    @SevenSystems I am noticing that my Xequence sessions are having trouble with tempo saving. I use it mostly now with AUM and even if I save my Xequence session again and again at 82bpm.. more then often it will open at 120bpm. Any thoughts on why this is happening?

    Yes, this is unfortunately a side effect of Ableton Link -- whenever that is active, any other Link-enabled entity will be able to reset the tempo.

    I'm not sure if this can be solved in an elegant way -- many other apps also struggle with this.

    There may also be an issue in how Xequence handles this of course... do you know any other Link-enabled app that handles this better? I would then have a look.

    So even though my AUM session is at 82... and when you first open AUM it goes to 120.. but if I wait till my project in AUM is completely loaded it will show 82. Then after that when I open Xequence it still links at 120? Where is it getting that info from if my AUM session is already down at the right tempo?

    Just curious.

    I was having similar issues. Ableton Link really needs a "keep master option."

    Xequence 2 kept reverting to a tempo of 127 that Patterning 2 had set in an old project even though it had long been closed and AUM was set at 103. It got too difficult to recreate and explain the issue so I live with it.

    Man thank God. I thought I was having flashbacks to my Rave Days.

    🍭

    I'm not sure why Link has been this way for so long with apps being able to jack the tempo. Under send start/stop you should be able to set app as master to ignore tempo changes.

    Lately I just keep Link off in Xequence 2 until it's loaded in an AUM session and it seems to avoid the issue.

  • edited July 2019

    @zah said:
    Change time signature during song?

    Nope but that doesn't mean you can't have a 5/8 section in a 4/4 song or whatever you might want to do.

  • @zah said:

    @BroCoast said:

    @zah said:
    Change time signature during song?

    Nope but that doesn't mean you can't have a 5/8 section in a 4/4 song or whatever you might want to do.

    I wasn't sure how to do that. If i was working in 4/4 and then wanted to introduce a 5/8 section, the whole arrange page would globally shift to 5/8

    You just have to ignore the bar lines. I guess I can make a video if it helps?

  • @busker said:
    Yes, being able to send program changes live from there would be fantastic! (In addition to the increment buttons :smile: )

    Yep, I see all your points, thanks for the insight and for describing the use case. I see the problem with the automatic program change chasing there.

    I've added this to the roadmap for investigation. Maybe being able to turn chasing of individual items (notes, controllers, program changes) would be a bonus as well.

Sign In or Register to comment.