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
WOW !
Awesome news.
iPhone version and I am all set.
But look forward to using it tonight.
Bought it long ago before it had LINK in fact.
Great this is turning into a super looper. Really appreciate the custom timesig which is often omitted from ios apps in general.
Thanks for the swift reply.
I did as described above, and could hear audio when I played the AUM keyboard. I then swapped back to QL, tapped the first track button, swapped back to AUM and played a few notes. I can see yellow blocks in the active track, but have no idea if it's recorded anything. I can hear no sound playback.
Just tried this with AudioBus3, and even worse!
I got AfroLatin DM loaded into AB3, then selected QL as the output. This duly showed up in QL. I then tapped Track 1 control to start recording, and used the AB3 transport bar to start AfroLatin DM.
What I got was about a second of audio, then a loud crack, after which QL crashed. Starting up again, I can get no sound from AfroLatin DM in AB3.
Starting again, again trying to use AudioShare in the AB3 top slot, and QL in bottom slot. Result, I can't even select any file in AudioShare to start playing. Take everything out of memory, relaunch AudioShare works again.
Tried again, resulting in QL looking like it is recording, but producing no sound. Not even it's own rhythm thingy. What am I doing wrong?
This is on an iPad Pro 10.5 with latest IOS.
Zen there must be something strange going on in your setup. Again this may still be an issue in QL however Audioshare not working in an AB slot seems to be unrelated.
Please send me an email from the app itself (system settings -> about -> contact support) this will give some more info. Including a screenshot for the input and output window helps.
If Quantiloop is the cause we will get it sorted.
Yes.
>
Splendid.
Okay, I'll have another bash and send you the results. Could EASILY be user error.
Will be sending you a report in a couple of minutes. However, it may also be helpful to report here something seriously weird. It may be an AB3 issue.
Okay, so I just tried again with AfroLatin DM in AB3 top slot and QL in bottom slot. In QL this showed up fine. But very oddly, what starts playing is the .wav file from AudioShare that would not start earlier. AudioShare wasn't loaded, and yes I had cleared previous AB3 session first. But I can finally record into QL. So, recording one bar, I try dismissing AB3 from memory, which is the only way to stop the .wav file from playing, without launching AudioShare, rekaunch and clear last session, then try AfroLatin DM in top slot and QL in bottom slot. Going back to QL, this shows up, but trying to record into track two Produces no sound at all! Madness.
the manual doesn't seem to be on the website (yet) but managed to export it from within the app, looks good, now I gotta try to make use of it
.. edit: seems to be working now, my fault, sorry
Great on-going support from Stephan on this, and progress being made.
Still finding weird problems. Does anyone else have trouble recording AfroLatin DM in QL? Whenever I try, ALDM plays for a second then resets itself to 0bpm.
Also having problem with QL appearing to be recording, according to notification at top of screen, even when QL has been dismissed from memory. If I then reload it and dismiss. It again, the notice finally goes.
QL does seem to work much better with Blocs Wave, though.
Is there a way to undo an overdub without deleting the entire loop?
@lukesleepwalker said:
Undo/Redo works while playing. When stopped it deletes.
However there is a separate MIDI action undo/redo which will undo/redo when playing and stopped (and never clear)
Excellent, thanks!
i was having trouble getting a count in from an outside app. it really, really needs a record function in audiobus and audiobus remote. the threshhold method is fine but you cant tell where the timeline is. a count in would be ideal.(unless i am missing it)
besides that i jammed for about 9 hours straight well into the morning lol. great update. great external midi mapping.
Anyone else get ruismaker to work as the rhythm track? Probably user error but I can't get it to make sound.
Luke, could you double check that you have 'rhythm main out' selected in the output. We haven't tested with ruismaker but may other rhythm plugins where tested.
If it doesn't work let me know and I'll contact Bram Bos to see if we can find out what is going on
Just for the other users here. The reason it wasn't recording was a very low (20bpm link tempo). Quantiloop uses 30 bpm as the minimum, audiobus 20. We will change this in an update to 20, although I think it is very unlikely that you will record at that tempo.
Re. ALDM
We can't verify with this, but with Rock Drum Machine and Funk drummer everything works fine.
Re. notification:
This is normal IOS behaviour. It actually means that an app is using background audio and the microphone. When apps are loaded as IAA's the bar does not always show the correct app. (it will always display one from the active audio session though)
You will find that this happens in all IAA connected apps
I'd love to see a record button in AB and AB remote as well. Really enjoying Quantiloop, and would like to make more use of with my other iPad apps. Actually temped to get a foot switch just for Quantiloop, but that wouldn't be practical for most of my music making locations.
Record button. Noted, Audiobus triggers are planned for the future.
Re: Count-In
There is a count-in option for the rhythm. So you could set rhythm to: Metronome,Autostart with Count--In, Stop After Record for instance.
I can confirm that, on my iPad if no one else's Rock DM also drops itself to 20bpm in association with QL, the moment QL is dominant App.But unlike it's sister, can be brought back up to a more standard 120bpm.
On the other hand, iSpark drums works as expected, recording beautifully into QL.
Is this an incompatibility between AB3 and Rock DM?
thanks for the tip!
>
Surely, though, when QL is dismissed from memory, this notification should not remain?
There is a lot to like about QL. Lovely design, and very useful functionality...once we have our heads around the way it works, of course.
Would love to see a trigger recording when sound begins option per track, so peeps like me who have difficulty getting timing spot on could make faster progress. But maybe all I need to do is practise more.
Trigger recording is in there (in Phrase settings -> auto-record).
However IMHO if you have your hands available of a foot controller the best is to work on timing. It is easier then most people think (I’m a very bad player and can do it
).
If you are syncing to something over link or MIDI for instance, recordings will auto align.
If you are recording the First loop without a point of reference of course timing is important.
The most important is to always start on the down beat of the measure as well as STOP ON the downbeat of a measure.
(Biggest beginner mistake is to hit stop at the end of the audio which is often slightly before the beginning of the next measure)
The issue with auto record is that it only really works if your audio starts exactly at the beginning of the neasure (which is not always the case)
Yes, the main out was on, but I figured out the problem: I had selected Ruismaker as an AU so it was waiting for MIDI from the host. So I switched to IAA and it works. I guess I don't completely understand the benefit, though, because I still have to go into ruismaker transport to play the drum loop and then return to quantiloop to start the rhythm track there. Ideally I could control the drum loop transport universally; this sounds like it could be a job for AudioBus. Too bad; I like the mostly self-contained world you've conjured in this app for live use (less moving parts).
Ruismaker - Quantiloop
Most drum apps actuall start playing when the host starts playing. You will find that this is the case with the lumbeats apps iPark, DM1 etc.
I already contacted Bram and we will have a look, and get back to you.
OK I’ve just played with Ruismaker and Quantiloop and to me everything seems fine.
As AU: Ruismaker is just an engine and requires MIDI notes in which Quantiloop passes on. (I think this make sense as an input plugin)
AS IAA: Ruismaker can play a loop and is suitable as a Rhythm plugin.
So seems to me that this would be usable in the box.
Thanks, @quantiloop. It works as IAA as you describe. I just hadn't tried the transport after manually doing it the first time.
Thanks, @quantiloop. It works as IAA as you describe. I just hadn't tried the transport after manually doing it the first time.
So @quantiloop, which audio interface do you use that takes advantage of the I/Os the latest release? Anything work with iOS that can use the four separate ins and outs?
@lukesleepwalker Thats not an easy one, there are many that work with iOS.
I personally use a 12 in/14 out mixer for testing mostly.
To play I actually use a 2 in 2 out. (Guitar, vocal, and the rest are MIDI instruments as inputs).
I’d check:
IConnectAudio 4+
IRIG Pro (DUO)
Focusrite iTrack range etc
Depends a lot on what you want (portability or not, number of connections, direct lightning interface or USB through camera connector)