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!

1131416181962

Comments

  • wimwim
    edited July 2019

    @BroCoast said:
    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.

    The manual explains it better than I can. Check Instruments > Controllers and Pianoroll > Editing velocities and controllers from the table of contents.

    (Not a RTFM post. It really does do it way better. ;) )

  • @wim said:
    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

    So easy - works - thanks!

  • @wim said:

    @BroCoast said:
    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.

    The manual explains it better than I can. Check Instruments > Controllers and Pianoroll > Editing velocities and controllers from the table of contents.

    (Not a RTFM post. It really does do it way better. ;) )

    Aha got it!

    It seems I can't wing it this time. It's quite different to what I'm used to but in a way all very tucked away and organised (add the controllers you need rather than having them all visible.)

  • The user and all related content has been deleted.
  • 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.

    Yes, it's high on my list of minor annoyances to get rid of 🙂

  • @BroCoast said:

    @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.

    Happy to hear you finally dived in! 🙂

    Is there any dialog / situation where you find it particularly distracting not being able to close it by tapping elsewhere? For the little menus (like in the toolbars), it can be helpful this way because you might want to keep adjusting something in the menu while working (say, the grid).

  • @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.

    @BroCoast said:
    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.

    Sorry to hear that, I've never seen it myself. Could you possibly make a video recording of that happening with another device's camera (so that I can see all interaction including the starting of screen recording), and send that to me via email? (I'll PM you with the address).

  • @Satie said:

    @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“ ...

    @wim explained it well. Instead of Undo (which will not always be an option), you can also easily just move the separated clips back onto their original tracks (so that all clips overlap), then select them all using hold-select, and then PROCESS -> Join.

    And also yes, you can delete a controller from an instrument at any time, the recorded automation data in clips won't be erased. It will then be listed as "Unknown / Deleted Controller" in the DATA TYPE menu. (Xequence 1 used to show the slot number as well so you would know which controller slot to use when (re-)assigning a controller to it... I see that must have been lost in Xequence 2, will put that on the shortlist).

  • edited July 2019

    @BroCoast said:

    @wim said:

    @BroCoast said:
    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.

    The manual explains it better than I can. Check Instruments > Controllers and Pianoroll > Editing velocities and controllers from the table of contents.

    (Not a RTFM post. It really does do it way better. ;) )

    Aha got it!

    It seems I can't wing it this time. It's quite different to what I'm used to but in a way all very tucked away and organised (add the controllers you need rather than having them all visible.)

    Yes, that's why we did it that way -- also, a controller in Xequence has many more options than just which MIDI CC to send, like "Return", "Centered", a name etc... so it's really a good idea to have a central place for configuration.

    (it also means that you can re-assign a different CC# to the same controller data at any time)

  • @SevenSystems said:

    @BroCoast said:

    @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.

    Happy to hear you finally dived in! 🙂

    Is there any dialog / situation where you find it particularly distracting not being able to close it by tapping elsewhere? For the little menus (like in the toolbars), it can be helpful this way because you might want to keep adjusting something in the menu while working (say, the grid).

    I've become used to it now and see the reasons why, well for a lot of things really. :)

    I'm totally in love with the MIDI editing now I understand it properly, I mean you pretty much solved every gripe I had with other apps. It's so well thought out for the touch screen, no more accidentally drawn notes or struggling to select them. Just brilliant.

  • @EyeOhEss thanks, good to hear it's clicking with users :) "Ruler available in Keyboard" has been requested a few times, I have it on the list... but first, I'll start working on the other little annoyances :)

  • Does V2 slave to midi clock?

  • @EyeOhEss regarding IAA and the switcher, please see here:

  • The user and all related content has been deleted.
  • @ElectroHead said:
    Does V2 slave to midi clock?

    No, not yet but you're not the first to ask for it ;)
    You can use e.g. Genome Midi or Gadget in the meantime.

  • Sorry, but I didn’t get the scale thing.
    I copy the instrument (notes are already there), same MIDI-destination.
    I set two different scales.
    Which button do I have to choose, when the wrong-scale-warning appears, that the notes get transposed?

  • @Satie said:
    Sorry, but I didn’t get the scale thing.
    I copy the instrument (notes are already there), same MIDI-destination.
    I set two different scales.
    Which button do I have to choose, when the wrong-scale-warning appears, that the notes get transposed?

    Sorry, no automatic transposition between scales is currently available... you would have to choose "Chromatic" or "Black Keys", transpose manually, and then again choose the correct scale.

  • @SevenSystems said:

    @espiegel123 said:

    @royor said:

    @skiphunt said:

    Another thing I'm curious about... I really like Modstep for the most part. How is Xequence 2 all that much different from Modstep for most of the core functionality?

    It has UNDO.. :D

    ModStep is a pattern sequencer and requires you to compose in chunks of limited size with limited time resolution.

    Xequence is s linear sequencer with high timing resolution that doesn't force you to write in fixed length chunks.

    ...independent per-clip looping with arbitrary granularity (loop length) -- while you can still see the actual linear "outcome" on the timeline.

    Could you please explain this further?

  • @wim said:

    @GovernorSilver said:
    Can those of you who are using both Atom and Xequence 2 explain how and why you are using both together?

    I've been puzzling out Atom vs Photon as a MIDI recorder to plug into AUM but then this new beast dropped...

    I find I’m using Atom less the more I use Xequence. It’s only a little more setup, and the results are easier to turn into an arrangement later.

    Still, it’s nice to just be jamming around and turn something you like into a loop just like that with Atom. I’ll usually go that way when I know time is running short or I don’t want to be distracted by setup. I know I can always come back and record the Atom output to Xequence if I want to take it further.

    I also use Atom if I’ve started something up mostly with Rozeta or other AU Midi apps. It’s less of an interruption to drop Atom in there for anything I want to play by hand.

    But more and more I’m just starting with Xequence in Audiobus and building from there.

    After our recent discussion about Audiobus, I decided to give it another look. You convinced me to re-check it out. I'm glad I did, since now I'm using non-AU apps more, and it makes doing this much easier if you use AB3 (with AUM still the main host for other stuff). I got the fieldscaper app in the sale and it's bloody excellent - I've been having a lot of fun just messing about with that. I'm thinking of getting Tube AU to get the samples to put into Fieldscaper but am not sure if the workflow would be 'too faffy'. But it's a promising setup: get a sample from YT, mangle it in Fieldscaper until I 'discover' something interesting, then create a complementary beat and bassline, record it all into Xequence 2, then create a melody. Bish, bash, bosh, out comes something interesting. I hope!

  • Purchased in support :)
    Still hope that it will get midi-assignable session loading capability eg program change, which will add greatly to it's use case as standalone only app. Sugar bytes have set the standard, hope everyone follows their model o:)

  • @tja said:

    I cannot see any problems with Galileo.
    Did you enable Background Audio in Galileo?
    Also, Galileo has 3 input channels, so may you need 3 instruments in Xequence.
    Or map them all to one channel.

    Galileo abruptly puts itself in the background, after I open it and try to touch it. Not sure why. Does not seem to have anything to with Xequence.

    I'm on IOS 12.3.1. Will report to Yonac if the problem persists.

  • @GovernorSilver said:
    Can those of you who are using both Atom and Xequence 2 explain how and why you are using both together?

    I've been puzzling out Atom vs Photon as a MIDI recorder to plug into AUM but then this new beast dropped...

    Asked this as well and need clear as day step-by-step instructions… LOL… Thanks anyone

    In addition to standalone, would love to see this set up in Audiobus and Audibus/AUM set up

    @wim and @SevenSystems (thanks!)

  • If you open this manual image (as I often do, when wanting to zoom in on my smaller monitor), via Chrome, it is difficult to read due to the transparencies depending on the website.

  • @baconcow said:
    If you open this manual image (as I often do, when wanting to zoom in on my smaller monitor), via Chrome, it is difficult to read due to the transparencies depending on the website.

    That's a good point -- I've updated the link (when you click / tap on the architecture diagram) to point to an image with a background.

  • @SevenSystems said:

    @Satie said:
    Sorry, but I didn’t get the scale thing.
    I copy the instrument (notes are already there), same MIDI-destination.
    I set two different scales.
    Which button do I have to choose, when the wrong-scale-warning appears, that the notes get transposed?

    Sorry, no automatic transposition between scales is currently available... you would have to choose "Chromatic" or "Black Keys", transpose manually, and then again choose the correct scale.

    I was wondering about this. Easy scale transposition would be a massive boon.

  • @audio_DT said:

    @SevenSystems said:

    @Satie said:
    Sorry, but I didn’t get the scale thing.
    I copy the instrument (notes are already there), same MIDI-destination.
    I set two different scales.
    Which button do I have to choose, when the wrong-scale-warning appears, that the notes get transposed?

    Sorry, no automatic transposition between scales is currently available... you would have to choose "Chromatic" or "Black Keys", transpose manually, and then again choose the correct scale.

    I was wondering about this. Easy scale transposition would be a massive boon.

    Yes I agree completely. I think it's somewhere on the roadmap already (1 of at least 39481 things there, sometimes difficult to shuffle priorities!).

  • @skiphunt said:

    @SevenSystems said:

    @espiegel123 said:

    @royor said:

    @skiphunt said:

    Another thing I'm curious about... I really like Modstep for the most part. How is Xequence 2 all that much different from Modstep for most of the core functionality?

    It has UNDO.. :D

    ModStep is a pattern sequencer and requires you to compose in chunks of limited size with limited time resolution.

    Xequence is s linear sequencer with high timing resolution that doesn't force you to write in fixed length chunks.

    ...independent per-clip looping with arbitrary granularity (loop length) -- while you can still see the actual linear "outcome" on the timeline.

    Could you please explain this further?

    Yes, you can loop individual clips just like in a pattern sequencer, but with additional benefits like actually SEEING it linearly, and interactively. Maybe a short video explains best! (soon, I'll be a true "pro" in video making! ;))

  • @SevenSystems said:

    @audio_DT said:

    @SevenSystems said:

    @Satie said:
    Sorry, but I didn’t get the scale thing.
    I copy the instrument (notes are already there), same MIDI-destination.
    I set two different scales.
    Which button do I have to choose, when the wrong-scale-warning appears, that the notes get transposed?

    Sorry, no automatic transposition between scales is currently available... you would have to choose "Chromatic" or "Black Keys", transpose manually, and then again choose the correct scale.

    I was wondering about this. Easy scale transposition would be a massive boon.

    Yes I agree completely. I think it's somewhere on the roadmap already (1 of at least 39481 things there, sometimes difficult to shuffle priorities!).

    Fantastic. Listen, the app is great and you're very clearly a supportive developer. I'll happily wait :-)

  • It would be nice to consider use of repetive and most used actions which currently require a press+drag+release action.
    For example in the piano roll.
    A slider is very convenient for moving larger steps but not when moving a note 1 step up down left right.
    Using a slider ( press, slide, release) vs tapping a button 1 time is a huge difference for ergonomics and a button press for 1 step prevents hand strain on the long term.
    And there is enough UI space to add a dedicated button for 1 step up down left right.

    Thank you for considering!

Sign In or Register to comment.