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!

1151618202162

Comments

  • @SevenSystems said:

    @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! ;))

    That doesn't remotely touch on the benefits of a clip-launching sequencer like Modstep or Ableton's Session view, and to tout it as somehow an improvement is a little disingenuous. Xequence is excellent at what it does. It doesn't do clip launching.

  • @Steaders said:

    @wim said:

    @Steaders said:
    Midi Thru was it wim!!
    Thanks SO Much!

    I couldn’t get your second preset to work though. Probably me. 😢

    If you would like to provide further details we can probably work it out. Perhaps setting up from the screenshot instructions rather than with the preset is better.

    It’s ok. I don’t think I need to get the second preset working as your original method is working well.

    Cool. I’m glad it’s working well enough. I did add some to my earlier post in case it’s of use to others.

  • @ExAsperis99 said:

    @SevenSystems said:

    @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! ;))

    That doesn't remotely touch on the benefits of a clip-launching sequencer like Modstep or Ableton's Session view, and to tout it as somehow an improvement is a little disingenuous. Xequence is excellent at what it does. It doesn't do clip launching.

    I think because @SevenSystems doesn't use pattern sequencers, the difference in the organizational principles isn't immediately apparent--and the importance of being able to select/trigger different patterns at a touch.

    This is not a criticism of Xequence. It is great at what it does and within its context, the 'clips' are a nice way of organizing within a linear sequence. There is no need for it to be something other than what it is (any more than ModStep should turn itself into a linear sequencer). So, I am not lobbying for Xequence to be turned into a pattern sequencer. I am just mentioning this I think people that haven't used pattern sequencers much don't get their appeal and what makes them worthwhile to the people that love them. Similarly, people for whom sequencer means "pattern sequencer" often don't get why people that need/like linear sequencers like them.

  • @ExAsperis99 said:

    That doesn't remotely touch on the benefits of a clip-launching sequencer like Modstep or Ableton's Session view, and to tout it as somehow an improvement is a little disingenuous. Xequence is excellent at what it does. It doesn't do clip launching.

    Yeah it's not an improvement but it is really useful it's own right, I've been testing it out earlier.
    It's actually pretty close to the Ableton arrangement clip looping. Ideally you want both.

    Not saying I wouldn't like to have a session view in there too, but it's nicely thought through as a linear sequencer. I'm digging the workflow after the initial source selection head scratching :)

  • edited July 2019

    @ExAsperis99 said:

    @SevenSystems said:

    @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! ;))

    That doesn't remotely touch on the benefits of a clip-launching sequencer like Modstep or Ableton's Session view, and to tout it as somehow an improvement is a little disingenuous. Xequence is excellent at what it does. It doesn't do clip launching.

    Would be great if one can just export those clips/loops ‘individually’.. something like what Gadget does for use in Ableton (Maschine, etc.)
    Or, I should ask if it can?

  • @RajahP said:

    @ExAsperis99 said:

    @SevenSystems said:

    @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! ;))

    That doesn't remotely touch on the benefits of a clip-launching sequencer like Modstep or Ableton's Session view, and to tout it as somehow an improvement is a little disingenuous. Xequence is excellent at what it does. It doesn't do clip launching.

    Would be great if one can just export those clips/loops ‘individually’.. something like what Gadget does for use in Ableton (Maschine, etc.)
    Or, I should ask if it can?

    Individual clip export to midi file would be a nice little addition.

  • @SevenSystems said:

    @GovernorSilver said:

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

    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!)

    wim had a good response, which I copied for future reference. Atom for him is convenient to have inside of AUM for quick capture of MIDI events while jamming. Then he exports MIDI from Atom to Xequence for further MIDI editing. Photon could probably do the same job... except it doesn't run in iPhone!

    While Xequence can obviously control synth apps by sending MIDI out to the synths, I am unclear as to whether it can capture incoming MIDI in real time. I think this is why wim and others are using the likes of Atom in AUM.

    I'm still a bit unclear on why Audiobus is being used, but the manual says it's good for "fast switching between apps, for central transport control, and storing and recalling the entire project from a single location." This is from the Example Setups section: http://seven.systems/xequence2/en/manual/

    Yes, Xequence has sophisticated support for recording MIDI from external (hardware or virtual) sources, including fully automatic multitrack recording (there's no need for manually creating or assigning tracks), automatically separated by sources and MIDI channels.

    Interesting! Ok, will experiment with using Xequence to record MIDI generated by Rozetta Particles, Autony, etc. and see if I like the workflow enough to skip having an intermediary MIDI recorder.

  • @espiegel123 said:

    @GovernorSilver said:

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

    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!)

    wim had a good response, which I copied for future reference. Atom for him is convenient to have inside of AUM for quick capture of MIDI events while jamming. Then he exports MIDI from Atom to Xequence for further MIDI editing. Photon could probably do the same job... except it doesn't run in iPhone!

    While Xequence can obviously control synth apps by sending MIDI out to the synths, I am unclear as to whether it can capture incoming MIDI in real time. I think this is why wim and others are using the likes of Atom in AUM.

    I'm still a bit unclear on why Audiobus is being used, but the manual says it's good for "fast switching between apps, for central transport control, and storing and recalling the entire project from a single location." This is from the Example Setups section: http://seven.systems/xequence2/en/manual/

    Audiobus has a floating palette that lets you switch with one tap to any other app loaded in your session and offers transport controls for all the apps loaded in your session. So, if you are in Animoog for instance, you can click Xequence's record button so that you can record your Animoog performance without switching back and forth from Xequence to Animoog to get the transport started and stopped.

    Also, if you have IAA apps that support Audiobus state-saving, their settings can be saved in your session. AUM supports AB state-saving. So, you don't even need to save a separate AUM sesssion. The AUM setup will get stored in your AB preset if AUM is in the AB preset.

    I have IAA apps but hardly use IAA, and with Apple's planned deprecation of IAA, I'll probably never use it again.

    Good points though about the transport controls and not having to switch between apps to use them. Maybe now is the time to finally get Audiobus 3. I've only used the original, and all but stopped using it after I got AUM.

  • edited July 2019

    @GovernorSilver said:

    Interesting! Ok, will experiment with using Xequence to record MIDI generated by Rozetta Particles, Autony, etc. and see if I like the workflow enough to skip having an intermediary MIDI recorder.

    Yes, it works fine! I just set up a Xequence 2 + Audiobus + AUM configuration as described in the manual, loaded a Rozeta Bassline in AUM and by routing it to "Xequence Destination" in the AUM midi routing pane I was able to record Bassline's output into a Xequence clip by selecting "Network Session 1" as MIDI source for the parent track. Everything was perfectly in synch.

    The only issue I'm having now is that if the loop mode is enabled on the clip, Xequence seems to overdub the clip if I don't stop recording right at the end of the clip and the few notes which are possibly (I say "possibly" because I could not see two different overdubbed and overlapping clips) overdubbed sound much louder. Easy workaround is to disable loop mode before recording, and cut the resulting clip according to needs.

    EDIT: also, when I record Bassline into Xequence, the synth associated to the track's instrument doesn't play the note while recording? Is that the correct behaviour? Once the clip is recorded and I push play, then the notes are played as expected.
    EDIT2: OK, I just needed to enable MIDI Thru for Xequence to play the notes being recorded on the linked instrument.

  • edited July 2019

    @ExAsperis99 said:

    @SevenSystems said:

    @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! ;))

    That doesn't remotely touch on the benefits of a clip-launching sequencer like Modstep or Ableton's Session view, and to tout it as somehow an improvement is a little disingenuous. Xequence is excellent at what it does. It doesn't do clip launching.

    I haven't dived into MIDI control of X2 yet but I have a feeling I could replicate a lot of Session view. It would just take a bit of clever mapping/work.

  • @silent1: yes, currently, when you record with the song loop enabled, then each new pass of the loop will ADD notes to the already existing ones (merges them into the same clip), there's currently no automatic creation of track lanes or multiple clips for each loop. However, this is high on the list that I want to see in the app, and it should be added shortly. I plan to make this an option, and when it's enabled, Xequence will create a new subtrack for each loop pass, and mute the previous subtrack automatically, so you can then listen to and select your best take(s) just by muting/unmuting.

    Also note that currently, MIDI Thru does not respect Multitrack Recording settings, i.e. it always routes ALL enabled MIDI inputs to the SELECTED track. I agree it would be nice to have MIDI Thru consider the Multitrack settings, too -- have to investigate how to best solve this.

    @RajahP @wim, not sure if this is what you mean, but you CAN convert a loop to individual clips by selecting the first clip and then PROCESS -> "Convert loops to clips". After doing that, you can select one of those clips and export it (be sure to enable "Only selected clips").

  • @ExAsperis99 said:

    @SevenSystems said:

    @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! ;))

    That doesn't remotely touch on the benefits of a clip-launching sequencer like Modstep or Ableton's Session view, and to tout it as somehow an improvement is a little disingenuous. Xequence is excellent at what it does. It doesn't do clip launching.

    Yep, seems like it. I will simply stop talking about and answering any questions relating to this topic. I think the "war" between linear and pattern sequencers is somehow like dogs and cats. Two completely different and heavily opposite kinds of persons / systems. :)

  • @SevenSystems said:
    @RajahP @wim, not sure if this is what you mean, but you CAN convert a loop to individual clips by selecting the first clip and then PROCESS -> "Convert loops to clips". After doing that, you can select one of those clips and export it (be sure to enable "Only selected clips").

    Oh. Cool. I never noticed the "Only selected clips" option!

  • wimwim
    edited July 2019

    @SevenSystems said:
    Yep, seems like it. I will simply stop talking about and answering any questions relating to this topic. I think the "war" between linear and pattern sequencers is somehow like dogs and cats. Two completely different and heavily opposite kinds of persons / systems. :)

    Ableton Live argues indisputably against that last sentence. Stagelight and GarageBand too, (though less authoritatively), from an iOS perspective.

    but I totally get it why one would not want to wade into those waters. ;)

  • Yeah, not a war at all. Both methods are complimentary for optimum results :)

    Ableton gets it right because both are equally important and can feed into each other.
    In this case AUM or another host can act as the clip launcher non-linear part whilst Xequence can be the linear sequencer to compliment this workflow :)

  • @silent1 said:

    @GovernorSilver said:

    Interesting! Ok, will experiment with using Xequence to record MIDI generated by Rozetta Particles, Autony, etc. and see if I like the workflow enough to skip having an intermediary MIDI recorder.

    Yes, it works fine! I just set up a Xequence 2 + Audiobus + AUM configuration as described in the manual, loaded a Rozeta Bassline in AUM and by routing it to "Xequence Destination" in the AUM midi routing pane I was able to record Bassline's output into a Xequence clip by selecting "Network Session 1" as MIDI source for the parent track. Everything was perfectly in synch.

    Cool! I tried something similar.

    1. Load Rozeta Particles into AUM
    2. Tap Multitrack Recording button in Xequence
    3. Tap Arranger button to get back to Arranger in Xequence
    4. Tap Record

    Sure enough, Xequence automatically created a new Track/clip with a recording of Particles' MIDI output, using a dummy Instrument.

    Next step is to figure out how to get Xequence to play the clip so that a synth receives the clip MIDI. Might take me a couple of days. :D

  • edited July 2019

    Well, my original question comparing Xequence to Modstep had more to do with a brand new Xequence 2 user trying to figure out what Xequence’s core competencies are by comparing it to Modstep that I know much better.

    I do like both for different reasons. And, I also like that Xequence 2 is completely useable even on a small iPhone SE screen.

  • @SevenSystems said:
    @silent1: yes, currently, when you record with the song loop enabled, then each new pass of the loop will ADD notes to the already existing ones (merges them into the same clip), there's currently no automatic creation of track lanes or multiple clips for each loop. However, this is high on the list that I want to see in the app, and it should be added shortly. I plan to make this an option, and when it's enabled, Xequence will create a new subtrack for each loop pass, and mute the previous subtrack automatically, so you can then listen to and select your best take(s) just by muting/unmuting.

    This would/will be - simply - a great workflow enhancement. Look forward to it.

  • Guys once I have recorded the midi coming from AB3; I got four midi tracks recorded, Bass, Pads, Drums and Lead keyboard. Now, I never created out put midi settings in X2 to play back the midi tracks, is it possible to select the track with the recorded midi data and just select its midi output back to AB3?

  • @zah said:
    I am interested in the piano roll part of this app as well, but nowhere in the manual under PIANOROLL do I see anything about midi note features.

    Can you split notes? Legato? Gap between notes? Overlaps? Are gaps adjustable? Can you divide a whole note into 16ths for example? Can I paint notes by dragging my finger? Can I overlay another clip on working clip to see both clips midi notes while tweaking midi on main clip? How (if possible) is any of this done? The manual doesn’t goes into any detail here at all.

    I’d like to work on midi clips away from desktop and export into DAW.

    I'm only a day in so far but for me it's by far the best piano roll editor I have used on iOS. It can do all of those things no problem.

    It has the touch recognition of Garageband (very easy to select notes.)

    Legato is really cool on this, you just select the notes you want legato and apply it. A lot of shortcut features.

  • edited July 2019
    The user and all related content has been deleted.
  • The user and all related content has been deleted.
  • @Tones4Christ said:
    Guys once I have recorded the midi coming from AB3; I got four midi tracks recorded, Bass, Pads, Drums and Lead keyboard. Now, I never created out put midi settings in X2 to play back the midi tracks, is it possible to select the track with the recorded midi data and just select its midi output back to AB3?

    Tap the midi plug icon at the top of the page, then the three dots at the bottom right of the instrument. Select AudioBus (not AudioBus 3) and a channel. Then load Xequence Midi Out 1 (or whatever channel you set) in the input of a lane on the AudioBus MIDI page, the app you want to play in the output.

    If the app you want to play isn’t able to be added on the midi page, load it on the Audio page, and change the Xequence output to go directly to the app.

    The Using Xequence + AudioBus + AUM example in the manual is helpful.

  • edited July 2019

    @SevenSystems said:

    @RajahP @wim, not sure if this is what you mean, but you CAN convert a loop to individual clips by selecting the first clip and then PROCESS -> "Convert loops to clips". After doing that, you can select one of those clips and export it (be sure to enable "Only selected clips").

    Seem to have a solution.. Split the tracks into clips, move clips to its own tracks and export..

  • @SevenSystems or @wim or anyone. I’m trying to get Xequence setup to send and receive midi from my laptop. I’m using rtpMIDI on laptop and set it up. I can control FL synths just fine. But I can’t figure out how to have Xequence record the midi from laptop? Do I need to go usb and use something like midimux? I’m really not getting any latency playing from Xequence but really want to get midi back from FL.

    Thanks.

  • edited July 2019

    @Eye0sStudios said:
    @SevenSystems or @wim or anyone. I’m trying to get Xequence setup to send and receive midi from my laptop. I’m using rtpMIDI on laptop and set it up. I can control FL synths just fine. But I can’t figure out how to have Xequence record the midi from laptop? Do I need to go usb and use something like midimux? I’m really not getting any latency playing from Xequence but really want to get midi back from FL.

    Thanks.

    I have no experience with rtpMIDI myself, but as long as it can either 1) send its MIDI to a virtual MIDI destination ("Xequence Destination", enabled in Xequence Settings -> MIDI / Recording -> MIDI Input -> Sources), or 2) has a virtual MIDI Source, that you would enable in the aforementioned dialog, then it should work.

  • Will try that Wim thanks so much!

    I was having issues cause I wasn’t sure if iBassist works as a sound module cause I didn’t want it to auto generate progressions based on the incoming midi from X2. Whereas Funk drummer I know has a sound module mode; except it wouldn’t trigger on for some odd reason. It just kept on auto generating drums. I’m really happy that I was able to record all four tracks in real-time in a single pass and that’s what I was really looking for. Lightweight and simple. Now I need to figure out the playback of my midi tracks. I’ll look in the manual.

    @wim said:

    @Tones4Christ said:
    Guys once I have recorded the midi coming from AB3; I got four midi tracks recorded, Bass, Pads, Drums and Lead keyboard. Now, I never created out put midi settings in X2 to play back the midi tracks, is it possible to select the track with the recorded midi data and just select its midi output back to AB3?

    Tap the midi plug icon at the top of the page, then the three dots at the bottom right of the instrument. Select AudioBus (not AudioBus 3) and a channel. Then load Xequence Midi Out 1 (or whatever channel you set) in the input of a lane on the AudioBus MIDI page, the app you want to play in the output.

    If the app you want to play isn’t able to be added on the midi page, load it on the Audio page, and change the Xequence output to go directly to the app.

    The Using Xequence + AudioBus + AUM example in the manual is helpful.

  • I had to disable auto track management as it was creating too many midi tracks. I found that for my needs to do multitrack ina single pass where I have AB3 hosting iBassist, Navichord, Funk Drummer and various synths for background pass and leads, I found that setting up my own midi tracks works best. I’m not sure if this is due to me using the AB3 beta but it might be. Either way I was able to record the midi output of iBassist, Pads, Leads, Funk Drummer and the Bass note from Navichord all in a single pass into X2! That was so smooth to see all the midi tracks light up with midi data!

  • Same, auto track management was getting annoying, hehe, though I can see the value.

  • @Tones4Christ @nondes very interesting to see your feedback from practical use. I was entirely sure that automatic track management was better and the only option anyone would ever want, until several beta testers were really annoyed and screamed me into bringing manual management back as an option 🙂 seems they were right!

Sign In or Register to comment.