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
@MusicMan4Christ @Richtowns : No bother. Be sure to report any remaining problems.
Done. It’s a 5 stars for me!
But please, Link !
Thank you. Link is on the near-future road map.
To shorten the wait, you should try the new MIDI Sync mode, it works really well with most apps we've tried.
Please look into Midi thru? Might be a bug
iPhone SE only not iPad Air1 .
Only happens when Hints re-enabled.
Can you describe in more detail what's not working? What's the iOS versions on those two devices? Thanks!
Both latest.
If I go to instrument midi then go to main menu re-enable hints. Open up Midi Thru- screen locks up.
As seen on screen shot but doesn’t happen to the iPad.
@MusicMan4Christ Haha, oh dear. The text in the hint has become too large to fit, the "OK" button is cut off... however you should still be able to tap it at the verrryyyy bottom of the screen. Sorry about that.
My bad! Figured it out. Couldn’t tap on OK bottom of screen I guess the iPhone SE is too small
It a bug!
Once I tried it again I was able to barely tap the bottom and it closed the hint! Sorry for false alarm.
It's a bug anyway and I've just put it on the list. If all bugs were that easy!
As I understand it, every version release requires an update of the Rating in order to keep it viewable and in order for it to count toward the current version's ratings. It's time to update your reviews, even if you just barely did it!! It's easy--just go to the page and give the (in my case) 5 star rating. You don't have to update your review if you don't want to. It is the number of stars that matter with ratings.
Updated rating: Done!
Weird thing is no matter how many times i select 5 stars, when i go back, it doesn’t show selected.
I saw that too. It does seem to be keeping the rating though, because I saw yours and noticed that it was 5 stars.
Wow cool!
Guys friendly reminder to update your reviews or at least rate the app. This means a lot to the Developers and helps big time.
Guys what’s the proper way to route midi to and from AUM in conjunction with Xequence to prevent creating midi loop feedback?
It’s seems that I have to go enable midi and disable again on playback in AUM and Xequence.
Basically I wanna know what works best and increases your creativity workflow.
I wanna create an AB3 AUM Setup or Template as well as in Xequence so I can just switch apps when needed but keep the midi setups as intact as possible.
@MusicMan4Christ: You will mostly find a way by trying all combinations of "Send MIDI to:" and "Receive MIDI from:" in all involved apps.
There's one really strange thing about Virtual MIDI, which even many devs (including myself a few months ago) don't get because frankly, the documentation kinda sucks:
For receiving MIDI, apps can either create a virtual destination (that's the "Any" setting in Xequence's MIDI In), and other apps then connect explicitly to that virtual destination, or explicitly connect to other apps' virtual sources themselves (that's what you do when you explicitly enable specific sources in Xequence's "Sources" panel).
For sending MIDI, apps can either create a virtual source (which Xequence doesn't do) and then other apps choose to explicitly receive from that source, or they can explicitly send to other destinations (that's what Xequence's Instruments do, and the only way Xequence can send to other apps).
It's really quite messy and every developer implements / labels / calls this differently. And it's not because developers are stupid -- it's because CoreMIDI documentation is not really that great (or maybe it is, but I haven't ever found the great parts!)
So, the best thing to do is try all combinations of explicitly connecting to sources/destinations, or using the virtual endpoints, by choosing all kinds of options randomly in all involved apps, and see when you get to a point where it all works
(We tried to "simplify" this a little bit by not using a virtual source, and by labelling the virtual MIDI In destination "Any" instead of "Xequence". Other apps, say "FoobarMusic", would label this "FoobarMusic Destination", so you would be choosing something called "FoobarMusic" as the MIDI In inside FoobarMusic, and that's confusing, so we labelled it "Any"
)
EDIT: Sorry not to give a more precise answer, but it's hard to say without more details... the best practice while trying it all out is usually to start with everything "Off" and no connections / no enabled sources / destinations etc. whatsoever, and then trying to enable stuff one by one until it all works, and if something doesn't seem to do anything, disable it again.
There aren't many cases where I would output data to Xequence from an app. But if you do, you might want to set it up outside of AUM for that purpose. If not, then just be sure that Input is disabled for the channel in AUM when you do so to avoid loops.
@wim OK, I think that was more helpful than my lengthy foray into technical peculiarities
For AB3, the concept is similar, but you have to get into using the MidiFlow Adapter and MidiFlow Channels filters to set things up. Once Xequence is a true AB3 midi sender, this will be less cumbersome. I'm loving Quantum+ AB3 for instant and gratifying setup and session save experience. I love AB3 app switching, state save, and AB Remote. Can't wait for Xequence to be in that role as well.
Nah! Throw us some example code, and the relevant MIDI specifications for some light reading!
And @MusicMan4Christ if you come back with "How about a video?" I'm gonna punch you right in the nose.
Wim thanks so much for the step by step, really helps.
Say I wanna do play the Bass in iFretless Bass app itself what would be the best way to config that AB3 or AUM?
I don’t think I have the Midiflow channels filter but I did t really think I needed that.
I don't have iFretless to try it out so I'm not a good one to give you an answer.
I can't say I really advise AB3 over AUM until Xequence is AB3 midi compatible. You will probably need the MidiFlow channels filter at some point though. AB3 apps are supposed to expose separate named outputs rather than channels, but many don't. However, if an app like Quantum can output on multiple channels, you can place a MidiFlow filter between it and each destination to filter out all but the channel you want for each instrument. I say "cross that bridge when you come to it."
Oh I forgot , a video.....
Honestly, a video where someone is using it to create something on the pianoroll would be awesome for us up here on the fence. I'm still trying to work out if I should dig deeper into BM3 and perhaps some time in the future find what I'm looking for OR keep on working around idiosyncrasies in ModStep OR perhaps settle for Cubasis (or Auria for that matter) when it comes to midi handling (which isn't my idea of awesome, sadly), OR if this app actually could be the answer (once it gets Link etc).
I'm mainly talking about handling of the pianoroll, how quick/easy it is to zoom, how precise it "feels" etc. Not one video. None. Nada. Null. I would have thought one of the vloggers, of which here are quite a few these days, would have gotten to it by now (and this is not critique aimed at @SevenSystems, honestly, keep adding things as outlined here and we'll fall off our fence in the right direction sooner rather than later).
I even tried to restart the thread named something like "The Best Piano Roll on iOS" or similar (which mainly seemed to conclude ModStep was the best, at the time...then...but alas, no undo etc...) and hoping for that some people from this thread would slam dunk that discussion once and for all but alas, nothing. Silence.
@hellquist: I have a feeling something is coming very soon in the video department
For anyone that hasn’t upgraded their Xequence app, there IAP is going on sale for $5.99!! Unlimited tracks! Awesome deal!
IAPurchased!
OK, can't let all this extra effort go unrewarded. Not entirely sure I need this, but I purchased it. Thanks @SevenSystems. On first glance before bed, it is really attractive. Only question: what's the metronome solution how?
@ExAsperis99: Thank you. The metronome sends MIDI notes, so you can just use any synth you happen to have on your device to produce the sound. In Settings (the "..." menu at the top left), you can choose the MIDI destination (and channel, if necessary) for the metronome, and then that synth will play the metronome sound...
However, there's been many requests for a "zero-setup", "standard" audio metronome, and we'll try to address them as soon as we can.