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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Comments
@chandroji yes, there is currently no Bluetooth dialog in Xequence itself. It's just a system dialog and the same in any app though, so you can just use any other app that has such a dialog (AUM, MidiFire, etc.) to set it up, it will then persist.
Thanks for the quick reply! So I had to get into settings etc, that was not very intuitive. Seems to work now! Thanks!
@nick yeah, maybe defaulting new MIDI sources to "Enabled" would be a good idea actually!
I have a weird behavior with gestrument pro. Everytime I try to record a midi track into Xequence, it records twice every single note. Has anyone run into this issue before? Thanks.
Edit: Ok I found the problem. In the MIDI recording tab, I had chosen more than 1 midi in sources.
Yes, it sounds to me like you have had both "Xequence Destination" and "Gestrument Pro" enabled, and have had Gestrument Pro send to "Xequence Destination" as well, which would explain the double notes.
yeah, that‘s how most apps handle it hence the expectation that it should just work ...
I really do appreciate it!
There's a new update coming in the next days that addresses that issue. Sometimes it's good to listen to users!
impressive customer service 🙂
@SevenSystems thanks so much for the option to hide the hatched loop overlay. The fact that no one complained about it but me and it was implemented less than a week after I brought it up is just crazy. You rule.
Only because it took only half an hour and an update was due anyway
The best way to thank me is to leave a review if you haven't already (preferably not a one-star like the "Terrible App, Terrible Developer (tm)" guy (who also frequents this forum) 
Thanks!)
@SevenSystems will you add the ‘back to host’ button in the app? I really feel this is an important feature which I believe isn’t hard to implement? It is sort of standard in IAA apps in my personal experience with them.
@SevenSystems that x-ray toggle is an excellent update.
I will take a look at it, but can't promise anything, as Xequence does not even officially support IAA... It's just a side effect of it supporting Audiobus.
(the officially supported way to quickly switch between Xequence and other apps is through Audiobus)
Sometimes it's the easy stuff
hope it's radioactive enough 😄
Thanks for the update @SevenSystems . Another 5 star rating coming your way.
Can't wait !!
I would appreciate this feature as most of the time I only use AUM, the fact that I have to click the iPad home button to get out of AUM and then again when moving from xequence back to AUM Is very time consuming and since the ‘back to host button’ is not a difficult option to add I do think it will greatly improve your app’s efficiency when people only use AUM.
One way (AUM - > Xequence) can be handled by having Xequence loaded up in AUM. Then just tap the icon.
If Xequence can get this going the other way it would be cool.
AUM & Xequence is my current combo.
If it's simply a matter of calling a "ReturnToHost()" function when tapping a button, then I will add it. I seem to remember I briefly Googled the other day, but couldn't find it
Actually you are correct, from AUM to xequence is possible. The other way implemented would be very cool.
Hi,
I enjoy Xeqeuence a lot. Till now, I have mostly used it as a little sketchpad to quickly capture ideas and motifs that I develop later in a DAW. But this week, I've started to explore using it for more extensive development and composition and have run into a couple of gotchas -- and have a couple of feature requests.
-- Issue copying / pasting tracks with controllers from one project to another.
The main gotcha that I've run into is related to importing a MIDI file that has controllers and copying tracks from the imported MIDI file into another Xequence project. When I do that, I have run into an issue that Xequence translates the actual CC numbers when pasting the tracks (using the destination files setup). I can see why that might sometimes be useful, but in the several files that I was working with, it had a fair amount of hassle. I hadn't explicitly set up any controllers in the destination project and did not know what the controller numbers were in the original. It required a fair amount of flipping back and forth between the imported MIDI file and the Xequence project.
If you need a recipe for reproducing the issue, please let me know.
What I'd really love to see when pasting in a track that has controllers that don't match controllers defined for the instrument, is for Xequence to use the source files original controller numbers or (less ideal) put up a dialog asking if you want to use the original controller numbers or translated controllers.
Thanks for a great app.
@espiegel123 thanks for the detailed post and suggestions.
Yes, Xequence assigns internal "slot numbers" to the controllers (1 to 12) which are independent of the actual CC number, and as you've right lt pointed out, that's by design... but I agree that having a mechanism to carry over the actual controller setup from the instrument which was used for parts on the clipboard when pasting into a different project would be very handy. Very good suggestion, will add this to the roadmap.
And BTW, very happy to finally see people use Xequence for larger projects. It's funny because that's precisely what the app has been designed for (see "Alpha"!) as most iOS sequencers are mostly designed around "noodling", but so far most Xequence projects I've seen involved a single track and around 3 parts
About Join and Split: yeah that can be added to the guide... I thought it was intuitive enough as it works just like in most other DAWs I've used, is there something in particular that you considered difficult to find there?
I also found the join and split difficult to understand and unintuitive.
How would you suggest they can be improved?
yes exactly, that's all it is. I hear adding the AUM logo can cause a few issues when programming it but some devs just don't add the logo which is fine.
About my initial confusion figuring out how to split parts. Sorry if this is overlong. But maybe it will prove useful--as I am probably not the only one that didn't find it obvious (although I am embarrassed that I didn't figure it out more quickly--it is straightforward once you know that the time marker is used to split parts).
I think the initial source of confusion on my part was that I was expecting (and I am not sure why) that I would be able to define parts from selected notes in the piano roll editor or that I could separate a part by selecting a time region in the arranger.
I guess I was thinking, "I need to define a part from a selection" as opposed to "I can split an existing part where the play cursor is" which is how it works. And while that is a perfectly reasonable way for it to work, it didn't occur to me and nothing in the docs mentioned splitting and joining -- which then made me wonder if it was even possible.
Also contributing to my confusion was that from some other (desktop) apps, I am used to being able to make a selection in a region and have some command available to turn the selection into a region/part.
And when I looked at the QuickStart, I didn't see any mention of splitting and joining parts. Once you realize the correct paradigm (select a part and you can split it at the playhead), it is straightforward.
Related suggestions:
p.s. As an fyi, to help get a sense of context, I have a lot of DAW experience and have worked professionally with music software for a long time.
I have run into a quirk of parts that I am hoping you might think about looking into. If you split a part, notes that overlap the split point get suppressed/cut-off when playing the parts.
This has come up in a couple of different types of situations.
Situation 1 is where a part has a pickup note that spans the split point. I often use pickup notes. It isn't a problem if the pickup has a short duration and ends before the split point, but if you have a pickup that starts on the eighth note that precedes the part boundary and the note is supposed to be held for a while, there are two side-effects: if you play the whole piece, the note terminates at the part boundary rather than being held for its full value. If you loop the second part, the note doesn't sound. I'd suggest that if you are looping such a part that the note should be 'chased'.
Situation 2 is essentially the same but arises when one has a note that plays on a synth with a slow attack and has nudged the note a little ahead of the beat to take account of the long attack.
I understand that this is a somewhat tricky situation to know what the app should do in the case of looping a selection/part, but in my opinion whel playing straight through, the note shouldn't be cut off.
Another thing that took me a stupidly long time to figure out was that you create empty parts by turning on the pencil mode and just tapping somewhere. It might be worth a mention in the QuickStart -- as I had seen a reference to drawing a small empty part but wasn't sure how to do it. I was using 'Empty Part' from the clipboard menu and then shortening it.
@espiegel123 all very good suggestions and observations, thanks again.
The part about splits going through existing notes is already on my plate. In a future version, a popup will appear in that case, asking you whether to split the notes, shorten them, or leave them as is.
And then, the question "what to do with notes that extend beyond the part end" is a little more difficult to solve... as you pointed out, it cuts them at the end right now. It used to play them through, but that meant that for example you weren't able to shorten a part with a long strings chord to cut it off, you actually had to edit it.
I guess the best thing to do might be to again ask the user when such a situation occurs what to do with cut off notes. However I also don't want to riddle the app with too many distractions.
But good to bring it up, wonder what others think.