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
@SevenSystems do you plan to add a ‘return to host’ button on Xequence? I find it incredibly frustrating to have to double click my home button on iPad and manually choose AUM every time I edit Xequence.
As far as I can tell it isn’t a difficult feature to add?
deleted, forgot humour is a bad idea.
If it is simple to give it Microphone access, you can get the little taskbar at the top of the app with the mic icon. If you tap this icon, it usually switches back to the host, even without a dedicated in-app ‘return to host’ button.
Just a thought.
i have a problem with xequence. i bought a iconnectivity mio 10 to bring my midi devices into network.
I have Problems with some hardware synths connected via wireless midi.
when i create 2 tracks, only one is played and the other has delay. When i use reaper or for example nanostudio 2 i can play as much midi channles over wireless as i want.
When i am using a USB cable, it is working correctly with xequence. Tried several things, no chance.
That’s a good idea 💡, I will try that and see what happens. However I can’t see why a button on Xequence can’t be added like the one on say synthscaper. Just be a lot more user friendly IMO.
Wireless MIDI (and audio, of course!) is best to be avoided in my experience... however, maybe we can get to the source of the problem (I don't have this particular interface so it would be hard for me to test) --
Is this delay constant, or is there jitter in the timing? If it is constant, you could try to pull the corresponding tracks back by tapping the cogwheel and then pulling "Delay" to the left (if the delay is less than 200 ms).
It would also be interesting to see if adjusting [ MIDI / Recording ] -> [MIDI OUTPUT] -> [MIDI Pre-Buffer ms:] to a lower value (say, 100) improves the timing? If so, then it is a bug in either the interface or one of the connected synths.
[Harassment ON] MPE recording ! [Harassment OFF]
[CoolnessHat ON] First point currently on the roadmap!
[CoolnessHat OFF]
i have tried to lower the latency... that didnt fix the issue.
as mentioned before, with nanostudio it works without problems over wireless midi. All devices at same time. But i dont like nanostudio2... too unflexible.
@colonelgeil sorry, hard to diagnose without actually using the hardware... I might try to borrow such an interface and see what I can find.
I just noticed that when using Xequence with AB3 (I am using latest AB3 beta) that Xequence's play icon in the AB3 palette doesn't change to pause if I start playback by clicking the play button in Xequence's menu bar. I think it also doesn't toggle if I start playback by pressing Xequence's play icon in the palette but am not certain.
This on iPad running 11.4.1
@espiegel123 thanks for the report, will try to reproduce and investigate shortly!
I'm looking for input. I keep reading comments from ModStep fans so I looked at some YouTube videos and I didn't see anything compelling that I couldn't do in Xequence. Are there ideas implemented in ModStep worth having as the MIDI driver for AUM harnesses of Apps.
I'm not a huge fan of the approach in Xequence used to assign Apps to tracks... too many clicks rather than a list of supported devices. I think this is a result of using pure MIDI for the interconnect rather than AB, IAA or AU to create a connection.
When Xequence connects to an App using MIDI is that Virtual MIDI, IAA MIDI or some other MIDI programmer's spec. If this should be a distinct thread I can start one but I'd prefer NOT to buy ModStep and actually want someone to tell me that's a good idea with some facts.
Well, ModStep has scenes, much like Ableton, BM3 or Stagelight. In fact, it only has scenes, it doesn't have a traditional timeline. It is also a very competent midi sequencer, but I would advice anyone who would like to start using it to host their instruments outside of ModStep (in AUM/AB/ApeMatrix etc). ModStep has a boatload of its own quirks. Someone will quickly respond that there is no undo. Also the metronome is rather annoying. Seeing past that it has some really cool features as well.
Having said all of that, I use Xequence these days.
Modstep is a pattern sequencer along the lines of Gadget bug richer. If you think in 1-16 bars at a time, pattern sequencers can be nice.
For me that approach can be helpful working up ideas. But for me it doesn't work as full composition tool whereas Xequence doesn't have those limitations. I personally find Xeq's Instrument/track paradigm really handy. But everyone has their own preference.
Thanks. When I discovered the way Gadget worked I pretty much stopped using it and haven't looked back. So, I'll pass on thinking ModStep might bring me something I'd prefer. I like an unlimited timeline since I tend to avoid thinking in Loops are building blocks. If I even find a program that support 256 bar "scenes" maybe I'd consider it but 16 bars just makes me have to figure out ways to break out of the limitations.
@McDtracy note that you can still have "Gadget-like" auto-looping parts if you want by selecting any part(s) and then choosing "Loop on" from the Magic Wand menu... some users overlook it so I just thought I'd mention it just in case
I made a video what happens when I play two tracks over wireless midi:
https://drive.google.com/file/d/1x99vjEBu025wQNjHqVBJ4xWfUjE9Sa57/view?usp=drivesdk
Again, with nanostudio 2 no problem. Playing only one midi track it is also ok.
Thanks for that. Does changing the MIDI Pre-Roll setting in Xequence have any effect whatsoever? i.e. is it worse if you set it to 1000 and better if you set it to 100?
EDIT: Oh, and is that a Yamaha SY-85 at the bottom?
EDIT 2: could you send me the Xequence project file too? Email address in PM!
Hello,
It’s a korg m1
Latency has no effect. I think midi messages are colliding or something. I sent you the audiobus project. I hope it includes everything.
Is there a way to edit the controller number or add additional controllers?
I wish I was as good at the app as the dev is a handling customer service.....LOL
Classy talented dude
In the Instrument setup, you can set the preferred cc's for each instrument. I think there is a limit to the number of different ccs you can use that can be lifted with an inexpensive IAP.
Ah, of course. Cheers! I was looking for it in the piano roll CC section.
Good stuff!
@espiegel123 first! Thanks
@SpookyZoo what espiegel123 said 
Oh and thanks @RUST( i )K
I bought it and spent the last bit just trying to get Midi to send from it in one AUM node to another AUM node with Synthmaster in it and make a noise.
Read the QuickStart guide and have clicked on the cog wheel in xequence but still don’t get how you set a simple MIDI setup from it to another synth in AUM? Also, have clicked on MIDI sources in Aum to enable it, but it doesn’t list in there so I’ve tried various settings to no avail.
Could someone screenshot the settings for that simple send from to, or explain so I don’t start thinking I’m cross-eyed, looking at the iPad upside down on the hard holiday nog?
Have you set it as AUM Destination in Xequence?
Although it may seem that routing the MIDI via the Xequence node in AUM is the way to go, Xequence targets should be routed in the Xequence app.
Let us know how you get on.
Also make sure your Xequence track is set to the correct Xequence instrument, so the Midi is sent to the intended destination.