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
The kick is a strange one. It seems to do the same “aliasing “ type sound that DM1 does (definitely sample based) when tuned in any way. Also doesn’t respond to velocity in external sequencer when other sounds do ...
No, because you stayed within the app. It will keep time and you won’t notice the delay playing live with it. If you were to use it as an AUv3 and send midi to it or use the internal sequencer along with other sequenced instruments you would have a greater chance of noticing the delay.
Yeah...kickdrum sounds "interesting"> @Zerozerozero said:
I’m not sure I understand you, it might just be me being thick. If it is, I apologise, I don’t mean to be confrontational but in this video I use the AR-909 in AUM and in a few different Cubasis 3 projects. Now, to be fair - having seen other people’s tests of the App and then having done my own (after making my video) I’ve found exactly the same as some of you guys. Run it alongside Ruismaker in AUM and the latency is noticeable. The AUM project at the beginning of my video doesn’t show it up though - it might if it were a different kind of arrangement, I’m not sure. In Cubasis 3 though - I haven’t measured the latency in any other way than to listen to the music and it sounds in time to my ears. Interesting thing - everything I’ve frozen from the AR-909 is bang on the money and everything ends up frozen before I mix anyway.
If I can answer a couple of other things in this same post - I would like to make sure I’ve expressed myself as I intended. I wanted to say that it’s important for people to be honest but that it doesn’t have to be done in a shitty way. I’m not calling people out for being truthful or asking them to stop being so. If I can back that up by saying, nobody has been more outspoken about Steinberg with regards to Cubasis 3 than I have, and I’ve said how I feel about it on my channel, to Lars, in the Steinberg forum and this one and Facebook etc.. I’ve also been brutally honest about my distaste for Positive Grids sales tactics. Steinberg responded with honours - by asking me to be a beta tester. I’m helping them improve Cubasis 3 and proud of that. Positive Grid just ignore me. I’m not the kind of YouTuber who won’t say anything bad about an app or company because I don’t want to jeopardise getting free stuff. But I would always say it as nicely as can be.
If a developer sends me an app or if I buy an app just cos I want it I’ll use it, I’ll make music with it, I’ll teach people how to use it, I’ll do anything to help anyone with iOS music absolutely whenever I can whether they’re a patron or watch my channel or not but - I’m not a guy who measures milliseconds. I’ll throw it into the mix and if it sounds good to me, it flies. I’m here to make music and to help others do so.
Yes, the aliasing “ringing” when tuned is the only part I really don’t care for. It’s not as noticeable in AUM as in GarageBand.
The kick is not sampled. And the earth is not flat. Just sayin’.
Lol I’m not getting involved in no kick sample conspiracy! If Matt says no samples them it’s no samples. 👌
I suspect it's more of an issue with Apple's MusicPlayer / MusicSequence, or how they're being used. I've no idea if that's what they're actually using under the hood, but I've seen some AK stuff that does, so my intuition leans more in that direction
By the time you're into all that low-level DSP stuff, there should be no trace whatsoever of even Objective-C code, let along Swift
I think it's an unfortunate consequence of the AK team having grasped the nettle and being very up-front about doing audio stuff with Swift (and good on'em for doing so!), whenever something goes wrong, the reaction in user-land is oh... it's because they're using Swift. I think often, the more likely explanation is simply that this stuff is hard to get right, and there's virtually no documentation telling us (the developers) how to do it right
A lot of the time you're learning from your mistakes, and some developers are further down that road than others...
😂🤔
Hopefully the dev can take all this criticism as a back handed compliment. If we didn’t care, we wouldn’t moan. Obviously an appetite/market for an aggressive, tweakable drum machine. Hope they keep at it. Midi learn is a big one 🤞
It also has twice the lag of the other instruments.
I wouldnt have cared if the interface and sounds weren’t so perfect.
May I ask a question here (sorry if that has been handled here before)?
Trying to use AR-909 in Cubasis, it loads and plays fine, but I can't get anything recorded, neither the sound nor the midi. I assume that I'm doing something wrong. Any ideas?
It doesn't have midi out. You can use cubasis piano roll or any other midi editor to sequence it.
Yup. Although I'm pretty sure midi out is coming soon.
Thanks a lot guys for the information!👍
I don't know what's up with the GUI of this app especially when used as AUv3 in AUM on an iPhone (iPhone 8) and switching between landscape and portrait mode. Sometimes wrong knobs are moved (ie. I touch one knob but another knobs value is changed) and some knobs don't react to taps at all...
...could be that the app gets 'confused' when the screen is rotated or the UI viewport is resized or something like that!?
(It's not the only app that gets confused by screen rotation and viewport resize).
Cheers!
Yup, have this also. It happens in lots of other apps too. Thinking it was more of an AUM/iOS 14 issue....?
Here it’s the BD that has the timing problem, hats seem to go well. About the “all synthesized” thing: I guess they refer to the parts that where synthesized on the TR-909. It would be very weird/not logical to synthesize the cymbals and hats.
@analog_matt , Re: timing issues.
An update today, with ableton link. So I checked the AU in AUM and Link makes no difference, as au’s take their timing And buffer settings info from the host, so I had a fiddle around..
My project tempo is at 136bpm and AR909 audio is noticeably behind the metronome.
I dropped the tempo in AUM to 20bpm, and AR909 is noticeably ahead of the metronome.
Sliding up the bpms, AR909 is exactly in time with the metronome, at 64bpm.
The amount of timing weirdness seems to be tempo dependant.
Good work!
😂
Hopefully not 909 bpm, because that would break the tempo barrier and crack the screen from the sonic boom.
Update dropped for me today (UK). Timing issues exactly as before: 25ms for the BD, 12ms for all the other instruments. At least (even worse?) this happens independent of BPM settings.
I think I’m done with this app.
When I saw “improves timing even more...” in the app’s update description my heart sank a little.
They still know it’s not right.
Oof, I guess I’ll always have my samples from mars 909 at least
Yeah me too, I did the test aaaand.. Oh well. Not that an oscilloscope is entirely necessary to hear the flam coming from the late kick, but for scientific reasons I guess. I personally think the previous build was somewhat usable, at least everything was together.
The only workaround I can think of now, the BD must be hard panned to one side, everything thing else hard panned to the other with a 12ms delay, then mixed back to centre. I'm tired.
Is the 909 ready to play well with other drum apps?
They must be trying hard to fix it as there have been a couple of updates to improve timing now. I do feel for the developers. It’s such a shame this wasn’t caught in beta because the app release should have been delayed until it can play in time IMO.
Yup I get this with most AU's inside AUM on the phone (that or the controls are unresponsive on the right side of the screen) . Tilting the phone to portrait mode and back to landscape with the AU plugin opened fixes it, but you gotta do it every single time you open up an AU window ( @j_liljedahl ).
The delay for the BD is about 25ms, for the other instruments it’s 12ms. You’d need to record two drum tracks (at least) and then use delay compensation in your DAW.
Worth it? It sounds damn good but I’d rather create a few sample sets and work with that.
No, not yet ☹️
Out of curiosity does the impulse setting (bd transient in parameters) effect this test (low setting being worse)?
To my ears it’s not sounding too bad now running next to another drum machine (FunkBox)...