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 updated with AudioBus!!!

135

Comments

  • edited August 2018

    @tja said:

    @vitocorleone123 said:
    I played around with it just to see how to get it set up, and... it's just about exactly what I found "missing" from Xequence vs. Gadget and means I think I'm ready to make that leap out of the Gadget box as I've been collecting plenty of synths and effects over the last year that collect virtual dust.

    Only 2 issues left for me to figure out (totally do-able): 1) how to do program changes to partially get around a limit of 16 midi channels, and 2) how to export each track individually -though this means solo-ing each and using AudioCopy to record each track one at a time... not as easy as Gadget which has an amazing export function.

    How many band members do you have?

    16 channels suffice for very, very much things and you may notice that you run into other problems with 16 IAA or AU Apps already.
    Then you will need to freeze to audio, which in turn frees the MIDI channel.

    For getting audio, just add AUM and save perfect loops in it.
    Or try around with Cubasis, for example.

    Just me :)

    It's a conceptual thing, I'm sure. I'm used to having unlimited tracks, so I can have multiples of several of the synths etc., split out each drum sound on it's own track, etc. I mix/master on a PC - so far. Which is why I've been exporting each track individually from Gadget.

  • wimwim
    edited August 2018

    I doubt AUM is going to add a lot of overhead.

    For 2) were you meaning exporting multiple tracks from Gadget? Or exporting multiple tracks from synths outside AUM? If the latter, it’s no problem. Just arm each AUM track for recording and press play. If from Gadget it’s more difficult. You’d need to record the incoming MIDI from Xequence into Gadget, then do a Dropbox or Ableton export.

  • @RajahP said:
    Just saying...

    Yes, Xequence is "in theory" an IAA app now, but that's just an unwanted side-effect of the Audiobus integration, and it's not of much use currently. But a "Return to host" button might be added in a future update, which would indeed make it useful.

  • @wim said:
    Pretty cool. Saved an AB3 preset then shared it via text to my iPhone. All I then needed to do was get the Xequence project file from the Xequence folder on my iPad over to the Xequence folder on my iPhone to get fully up and running.

    I suppose if iCloud synced storage was an option in Xequence this could be even more streamlined, but I’m not complaining. This is great!

    Hey wim, it should not be necessary to share the file via iCloud. The Audiobus preset itself contains the entire project, and it should open on any other device even if it doesn't have the project file. If this doesn't work, then this is a bug and I would appreciate if you could try to repeat it and PM me the details.

    (during testing, I have seen the rare occasion when an Audiobus preset did not restore the Xequence project along with it correctly. If you get that situation, could you try to just load the preset again? As I said, the project file doesn't have to be present on a device to open an Audiobus preset.)

  • wimwim
    edited August 2018

    @SevenSystems said:

    @wim said:
    Pretty cool. Saved an AB3 preset then shared it via text to my iPhone. All I then needed to do was get the Xequence project file from the Xequence folder on my iPad over to the Xequence folder on my iPhone to get fully up and running.

    I suppose if iCloud synced storage was an option in Xequence this could be even more streamlined, but I’m not complaining. This is great!

    Hey wim, it should not be necessary to share the file via iCloud. The Audiobus preset itself contains the entire project, and it should open on any other device even if it doesn't have the project file. If this doesn't work, then this is a bug and I would appreciate if you could try to repeat it and PM me the details.

    (during testing, I have seen the rare occasion when an Audiobus preset did not restore the Xequence project along with it correctly. If you get that situation, could you try to just load the preset again? As I said, the project file doesn't have to be present on a device to open an Audiobus preset.)

    Sorry, but nope. Tried half a dozen times and it opens with the last loaded project, not the midi from the preset. Even on the same device if I’ve changed project files in Xequence.

    http://preset.audiob.us/XVJOt1C8iLUbzDl

    [edit] oops. Overlooked the “PM me” part. PM’d some additional details.

  • @wim said:

    @SevenSystems said:

    @wim said:
    Pretty cool. Saved an AB3 preset then shared it via text to my iPhone. All I then needed to do was get the Xequence project file from the Xequence folder on my iPad over to the Xequence folder on my iPhone to get fully up and running.

    I suppose if iCloud synced storage was an option in Xequence this could be even more streamlined, but I’m not complaining. This is great!

    Hey wim, it should not be necessary to share the file via iCloud. The Audiobus preset itself contains the entire project, and it should open on any other device even if it doesn't have the project file. If this doesn't work, then this is a bug and I would appreciate if you could try to repeat it and PM me the details.

    (during testing, I have seen the rare occasion when an Audiobus preset did not restore the Xequence project along with it correctly. If you get that situation, could you try to just load the preset again? As I said, the project file doesn't have to be present on a device to open an Audiobus preset.)

    Sorry, but nope. Tried half a dozen times and it opens with the last loaded project, not the midi from the preset. Even on the same device if I’ve changed project files in Xequence.

    http://preset.audiob.us/XVJOt1C8iLUbzDl

    [edit] oops. Overlooked the “PM me” part. PM’d some additional details.

    Thanks for sharing, will investigate!

  • @SevenSystems very cool. It has been a very good thing watching Xequence grow. Always enjoy your input as well.

  • edited August 2018

    @SevenSystems : Hiow do I get the manual pdf?

  • @SevenSystems said:

    Yes, exporting each track as a separate MIDI file is not supported currently, but it's a nice addition I'll put on the list :)

    That would be pretty.

  • @Telstar5 said:
    @SevenSystems : Hiow do I get the manual pdf?

    From the app, hit the “...” in the top menu, then the information icon at the top right. Then follow the link to the help page and you’ll see the manual download link.

    Or ... http://www.seven.systems/xequence/downloads/XequenceQuickstartGuide.pdf

  • @SevenSystems Just thought I’d mention that so far Xequence combined with AB3 and AUM has been my favorite and most satisfying experience on iOS. Finally something stable that lets me produce great results. I hope that AEM will follow suit and get that DAW to perform this well. Awesome! Thank you.

  • @SevenSystems I cant seem to find how to change the destination of the instrument on the Iphone versions (using Iphone x), on the Ipad its as simple as just hitting the cog on the instrumental and changing the gadget, but can find the same on the iphone and no luck looking in the manual, can you help?

  • wimwim
    edited August 2018

    @Jose_Bee said:
    @SevenSystems I cant seem to find how to change the destination of the instrument on the Iphone versions (using Iphone x), on the Ipad its as simple as just hitting the cog on the instrumental and changing the gadget, but can find the same on the iphone and no luck looking in the manual, can you help?

    ??? It’s exactly the same on iPad as iPhone.

    • touch the midi plug icon in the top menu
    • Add an instrument if needed
    • Touch the gear icon at the lower right of the instrument
    • Touch “Midi Destination” to select.

    If you don’t see that then there could be something specific to the iPhone X.


  • I've found out what it was, I was zoomed out too much and the icons werent visible because it dynamically corresponds to the zoom level 8-(

  • @wim Thanks, got it! Duh, now I just saw that the developer posted a link

  • @RajahP said:
    Just saying...

    what i see it in Aum, but midi doesn’t work. weird any body else get it to work?

  • i’m fine using audiobus with xequence instead of aum, but is it possible to bus audio to other tracks in audiobus, like you can in Aumv

  • @eross, it's no problem at all to use both at once:

    • Launch Audiobus and put Xequence as a source into a MIDI lane
    • Put AUM as a source into an Audio lane
    • Put as many channels into AUM as you like, enable the "AUM Destination" for each, and assign consecutive MIDI channels
    • In Xequence, create an instrument for each instrument you created in AUM, and select "AUM" (NOT Audiobus!) as the MIDI Destination, and select the corresponding channels.
    • Boom.

    (Actually this is the way I officially recommend to use AUM with Audiobus and Xequence. I'll put that in the manual.)

  • edited August 2018


    @SevenSystems First thank you for great app. I have never been much of an Audiobus guy so forgive me if this is obvious.
    See picture. If I stop Xequence in let’s say middle of my song, no matter what I can’t get it to go back to beginning by tapping the AB transport. I have to go back into Xequence to do this. Is this normal?
    Also in a project that I saved in AB I have Gadget and Xequence, is it normal to get ghosts from Gadget? What is proper way to shut down Audiobus and not retain and ghosts?

    Thanks
    Chaz.

  • @Chaztrip said:

    @SevenSystems First thank you for great app. I have never been much of an Audiobus guy so forgive me if this is obvious.
    See picture. If I stop Xequence in let’s say middle of my song, no matter what I can’t get it to go back to beginning by tapping the AB transport. I have to go back into Xequence to do this. Is this normal?

    The "Rewind" button in Audiobus works the same as the "Stop" button inside Xequence -- the first time you tap it, it goes back to the last position where playback was started, the second time you tap it, it goes back to the beginning of the song or loop. So you would have to tap the "Rewind" button twice. Let me know if that works for you.

    Also in a project that I saved in AB I have Gadget and Xequence, is it normal to get ghosts from Gadget? What is proper way to shut down Audiobus and not retain and ghosts?

    Not entirely sure what you mean by ghosts, can you give a few more details?

  • @SevenSystems Looks like solid coding there, champ! Considering all that was involved, I would say this has been a stellar rollout. Too bad about the Reason stuff stealing a bit of the thunder.

    One quick question: Can the ruler be set to snap at anything other than bars? I'd like to use the split command to more quickly rearrange PolyHymnia results, among other things, but it's currently too limiting. Thanks.

  • @aaronpc thanks, yes you're right on the Reason thing. A bit frustrated but "it always goes like that" pessimistvoice 😉 rollout has been less apocalyptic than expected so far indeed 🙂

    About the splitting: Unfortunately, the grid in the Arranger is currently fixed at one bar. It's something I would very much like to see improved as well, and this might come in one of the next updates in preparation for a little companion app to Xequence, which would also depend on it.

  • @SevenSystems awesome welcome update, mate. I tried using polyhymnia for generating just different velocities and whatnot for existing notes (to no success). Just put Xequence on AB Input and Output, used Midiflow Randomizer as MIDI FX and getting awesome results :love:

    @SevenSystems said:
    in preparation for a little companion app to Xequence, which would also depend on it.

    Yummy :cookie:

  • @senhorlampada said:
    @SevenSystems awesome welcome update, mate. I tried using polyhymnia for generating just different velocities and whatnot for existing notes (to no success). Just put Xequence on AB Input and Output, used Midiflow Randomizer as MIDI FX and getting awesome results :love:

    Good to hear that people are exploring creative MIDI routings with Xequence without issues.

    Regarding Polyhymnia: modifying characteristics of already existing notes instead of adding new ones has been requested already and it's on the todo list...

  • @wim said:

    @ExAsperis99 said:
    I must say, I'm still totally baffled by Xequence. I was hoping that I could drop in synths and Xequence on the AB3 midi page, as in Cubasis, channels would just be populated in Xequence. I'm sure I'm doing something wrong, but that's not the case.
    Could anybody grab some screenshots of, for example, of an AB3 setup featuring two or three AUs being driven by Xequence? I have a real mental block with this otherwise beautiful piece of software.

    I think you got it backwards conceptually. Xequence is sending to the apps, not the other way around like on the Audio page.

    No, I get it, although it's not 100 percent second nature, I must admit.
    My problem with Xequence is that there's a separate page for instruments and then another page for, uh, also instruments? But with the sequencer? But there are different pastel colors that indicate...modulations?
    I've had a few stabs at it, but it's a little quirky, and I know Modstep and Cubasis well enough that I haven't been inspired to crack the Xequence nut.
    I was hoping that AB3 would just make all my connections for me. It doesn't quite.
    So I see the task facing me, and I must accept it:
    I will read the fucking manual.
    (Send help if I don't emerge by Tuesday.)

  • @SevenSystems - Is there any way that Xequence can capture the gestures (slides on keys) from Animoog? It’s recording the notes just fine...but, not the bends and modulations from the keys. Absolutely love the app and have been using it since it was first released as my main sequencer for Gadget!
    Thanks!

  • edited August 2018

    Great update!

    Looking forward to

    F
    -old
    --ers
    ---next
    AND
    -mult
    --iple
    ---mid
    ----i

  • edited August 2018

    @thatguysmitty said:
    @SevenSystems - Is there any way that Xequence can capture the gestures (slides on keys) from Animoog? It’s recording the notes just fine...but, not the bends and modulations from the keys. Absolutely love the app and have been using it since it was first released as my main sequencer for Gadget!
    Thanks!

    Animoog uses Polyphonic Aftertouch, also called PolyPressure, for transmitting the keyslides... unfortunately, that is currently not supported by Xequence, but it's something with rather high priority on the todo list!

    @ExAsperis99 said:
    My problem with Xequence is that there's a separate page for instruments and then another page for, uh, also instruments? But with the sequencer? But there are different pastel colors that indicate...modulations?

    Think of it like this:

    • Each instrument (what you set up after you tap on the "MIDI" icon) represents a sound (a MIDI connection to a synth).
    • In the arranger, each track represents one layer of your song. In the cogwheel menu of each track, you select the instrument (from the instruments page) to which that track's data belongs (should be sent to).
    • In the simplest scenario, you would simply have one arranger track for each of your instruments.
    • The big advantage of having tracks and instruments separate (in contrast to f.e. Cubasis) is that you can have SEVERAL tracks that use the SAME instrument. That means that for example, you can have ONE "strings" instrument, however, you can put the BASS notes and the TRIADS on SEPARATE tracks, and then mute, solo, manage and arrange them separately.
    • Same goes for controllers. While it is possible to put everything (notes and one or more controllers) into the same part, it is much easier to keep an overview and structure your song if you put notes and controllers on separate tracks.

    So in the end, the separation of instruments and tracks is to make complex compositions (like for example, the included demo song "Alpha") managable. However, you can always keep it as simple as you like by just having one instrument and one track per synth you want to use, and that's all :)

    Oh and the colors indicate INSTRUMENTS. Each instrument has a color, that you can freely assign. Anything that later on has to do with that instrument anywhere in the app, will have that color. All this stuff actually makes Xequence easier and more efficient to use. The manual also has great explanations for everything :)

  • @SpookyZoo said:
    Looking forward to
    -mult
    --iple
    ---mid
    ----i

    Multitrack MIDI recording will almost certainly be available in the next major update (as a very moderately priced IAP). Expect a timeframe of about 4-6 weeks!

  • edited August 2018

    Can you record multi channels (I guess they call it Omni) on one track... help?

    Edit.. sorry did not see the previous post..^

Sign In or Register to comment.