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
Ahh, OK, so there is some ground to cover regarding other hosts.
Well, you can always just enable MIDI In on “Xequence Destination” in X2, then send the midi out to “Xequence Destination” from NS2. The trick is there’s no global start that will work for both (NS2 doesn’t have Link Start/Stop). So, you need to start them separately, then trim the recorded midi and move it into the right position in X2.
If you load both X2 and NS2 into Audiobus 3 then you can use it to start them both at the same time. But by then might be just as well off learning to use Rozeta and X2 in Audiobus.
Hey @SevenSystems
Still very happy with all my X2 (and X1) work... Getting more and more my „go-to-sequencer“...possibly it is already
I am on 13.4 on all my iPads and can not click the Transport-buttons with the mouse.
Can we investigate? Is that already known? I think it worked before the 13.4 update.
Kind regards!
Edit: Well, exactly it is not only the Transport-Buttons. It’s all UI elements.
Thanks, nice to hear
Oh, that's worrying. I'm not seeing this behavior on my iPad Pro 9.7" 2017 with iPadOS 13.4.
Do you have any kind of accessibility / zoom setting or similar enabled?
Does literally no single button respond? Does zooming / panning in the Arranger work? Do buttons at least light up slightly when you touch them?
Anyone else seeing this?
Thanks!
@SevenSystems
Sending you a PM right now.
For everyone using a mouse: I've just uploaded an update to Apple that introduces preliminary mouse support (everything should work except zooming / pinching in editors, which still requires multi-touch (two fingers)). More complete mouse support (possibly including a zoom slider and/or scroll bars) is being considered for a future update.
And thanks @MrBlaschke for your feedback and help with sorting this.
Update should be available in the coming days if Apple staff is still working and doesn't find any problems.
Stay safe and healthy (including mentally, which might be the bigger challenge right now!) everyone in these unprecedented times.
@SevenSystems Amazing! Thanks so much - you are very welcome 🙏
@SevenSystems Thanks for this new feature, stay safe (and all of us) too !
@SevenSystems Any chance to have Xequence sequence remote from one iPad to another or can it do this and I’m an idiot?
Could you provide a few more details on what you're meaning to achieve -- if you want to create a MIDI connection between two Xequences on different devices, that can be done via Bluetooth MIDI already. But maybe I've misunderstood.
So I am a visual guy.... and sometimes it would be nice to have Xequence on one iPad sequencing AUM on the other. That way I could see all that is going on. I know I am weird...
Oh yeah, I see... that is completely possible.
See settings in AUM (iPad in this case):
...and on your Xequence device (iPhone in this case):
You might not get the best timing though, and significant latency.
This sounds like a great solution, possibly even better than au integration, went to try it on my old iPad buts it’s stuck on iOS 9, is it OS or hardware limitations that prevent compatibility there?
Both. Bluetooth MIDI LE is needed, and some older hardware and iOS versions don't support it.
Actually I would be interested in any feedback if this is feasible in an actual production situation. I doubt that the timing will be very tight, it probably also depends on technical details in AUM. (The Bluetooth MIDI packets that Xequence sends when the sequencer is running should contain timestamps and these should actually arrive over Bluetooth in AUM, but I'm not entirely sure. If that's the case and AUM uses them, then it would still have sample-accurate timing over Bluetooth (despite the latency).
Ah fair enough, ta
I’ve just read somewhere someone pleading for a IIA button to come back and forth AUM but I just can’t find where. Well this would be a great idea until we get the AU version.
It’s in the Samplr thread.. I did.. should have posted it here..
Oh, it’s all right, @RajahP Nice addition in Samplr too. Very practical.
It actually works quite well!
I wouldn't use it for production because with a high number of MIDI notes, the latency will naturally increase but with a few polyphonic tracks, the BT serial protocol is a fairly low-latency deal. I'm quite happy with it.
Audio over BT is much worse for two reasons:
1. It needs more bandwidth and additional buffers
2. It relies on audio compression because linear PCM would eat uo too much bandwidth and as a consequence, too much power from the BT viewpoint.
As for MIDI timestamps, I'm almost 100% sure that they are removed when they leave the CoreMIDI stack to go over BlueTooth.
With hardware MIDI, packets just have to be sent, received and processed as fast as possible, which has great influence on related thread prioritization in your app.
Timestamps only help if packets can be sent in advance which isn't supported by the MIDI protocol as used in hardware today.
Important: Please don't update to 2.2.10 (the current version in the App Store) and wait for 2.2.11!
2.2.10 contains an important bug that can cause the "Play" button to crash. Sorry for the inconvenience!
(if the Apple gods allow, 2.2.11 should be available very shortly!)
👍
Update: Apple has approved 2.2.11 after 5 minutes, that is amazing. All good, please update to 2.2.11 as soon as you see it in the App Store (do not update if it still says 2.2.10!).
Thank you Apple!
@tja yep. I had removed it from sale as soon as I knew about the crash, to prevent more destruction!
It should reappear soon though.
Thanks for the heads-up! The App Store seems to have been confused for an hour or so, even completely missing the app description. Sorted now!
And sorry for the inconvenience caused! (a good reminder for "Even bugfix updates need to be tested for bugs"!)
Maybe I've missed them but does xequence have LFOs? If not, any plans to add them?
Also, riffer has an option to choose how many root notes you use when generating a pattern. Can Polyhymnia do this?
Hi -- Xequence does not have LFOs per se, but you can quite easily "fake" them (with lots of control) by drawing your desired LFO curve in a clip, and then setting that clip to loop and then using MIDI timestretching / cropping / etc. to shape your "LFO" to your liking. (I can make a short video if you're interested).
PolyHymnia will always generate notes in the scale of the track's instrument -- there is no explicit way to set a root note, but you can adjust the pitch range up or down or tweak the algorithm to fit your needs.
Hope that helps.
Yeah, it does. Thanks
I've been drawing them in already. Just thought it might speed things up a bit with dedicated LFOs. But you've given me some interesting ideas there
I really like Polyhymnia btw, and xequence Inn general, but that root note option really helps to make more musical - less random - phrases. I'm not complaining though the chord option blows riffer out of the water. This app really is awesome
Once again, thanks 👍