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
@SecretBaseDesign I hate to do this to you, but you made some promises about an early "2015" updated version of MIDImorphosis (Version 2) for iOS, When you delivered the OSX version I was expecting the iPad version to be the next cab off the rank. Truly I am staggered by the amount, variety and quality of the fantastic Apps you are delivering this year, but the one I am patiently waiting for currently appears to be way down your list of importance and that is fair enough as you are entitled to do as you see fit, but if you could just indicate a ballpark idea of when you will have the time or inclination to produce MIDImorphosis 2 for iOS I will be a happy man. I hope this post does not read as rude to you as I would not like to appear any way other than a big fan of your work
@SecretBaseDesign It would be great if you could increase/decrease the velocity sensitivity like in Impaktor. The other problem with Voxkit seems to be latency. What I was actually trying to do was pretty much exactly what @gburks wrote: a bass drum pedal so just 1 trigger with a fixed MIDI note. Except that I was thinking of adding a second pedal (board with piezo) for another sound like HH or cowbell, which I would try to get to physically produce a sound different enough to the first so Voxkit could easily distinguish between the 2 triggers. So I'm wondering if it might be helpful to be able to restrict the number of triggers to the amount actually being used (so in this case from 4 to 2). Or even 1 when only 1 trigger is used. Wouldn't that reduce the processing and resulting latency significantly? Another idea was if I could use a stereo interface and then select separate input channels for the 2 triggers that should still mean no guessing which note is being played because everything coming in on channel 1 is note 1 and everything on channel 2 is note 2, right? So having that and a good way to adjust input sensitivity would probably do the trick for me. I don't really need Impaktor to do this if something else does it. But the reason for choosing Impaktor now is the better responsiveness compared to Voxkit. And Impaktor is awesome...
@banjofran -- totally fair; I'm behind schedule on the MIDImorphosis update. As they say, the best laid plans of mice and men.... I didn't have Music IO on the radar at all until I got pinged by Dan and Nic (MIDI Designer and MIDI Bridge developers); once we embarked on that, lots of other things got pushed to the side. A huge amount of time has gone into Music IO, and there's more that we plan to do.
On the horizon right now -- Music IO 1.40 should be out the door in a couple of weeks, and then there's a new and different app that uses the reworked core pitch detection of OS X MIDImorphosis on the boards. My expectation is that the market for the new app is much larger than the guitar pitch-to-MIDI market, so that's going to take precedence. After that's done, I should be able to get to MM 2.0 for iOS.
WRT Voxkit latency -- it should be fairly low, for a process that does analysis of the incoming signal. The audio normal comes in 256-sample buffers, or about 5.6ms. The FFT gets run on that, and then I trigger the closest spectrum match from the columns that are enabled. Because I'm using MIDI, the audio isn't replaced-in-place (like an effect); the MIDI message gets handed off, and it's the next audio frame, or possibly the one after that, where sound starts to be produced. Latency was in the 12ms to 15ms range, if I recall my experiments correctly (it's been a while). This is faster than most hardware-based guitar pitch-to-MIDI processors, and about half the latency of a Bluetooth MIDI message, but for drums, the timing is really critical. Hardware drum pads can be 5ms or less (which is lower than even a single typical audio frame). One of the challenges with tracking velocity accurately is that the real "volume" of an incoming sound may not be reflected in the first fraction of a second of the strike, depending on what you're hitting.
Processing time for the FFT isn't significant, nor is the matching -- the limiting factor is the audio frame size, and the sequential nature of sending MIDI. Impaktor is closer to an effects app, and replaces incoming audio with samples or synthesized tones -- and as far as I can tell, it's not really looking at the "tone" of the incoming audio, and just using volume level to control the synthesis. Very cool app -- but doing something quite different from Voxkit.
@Matt_Fletcher_2000. How's the sensitivity of the pads? Can you get different velocities easily?
Yes the pads are quite sensitive to velocity when played with sticks.
^ Super pretty please consider this for Impaktor 2! And/or the ability to point 4 discreet audio inputs at it ala Alesis DM-4/5. You know you've created a little bit of magic when there are youtube videos out there by people who've purchased multiple iPods solely for the purpose of drumming with multiple instances of Impaktor!
On that note, and we all love universal apps, if Impactor 2 were instead not universal, we could ostensibly run two instances provided we could choose separate trigger inputs. If not via discreet audio input selection, AB effects slot support would allow us to use AB for the routing and Impaktor could carry on not caring.
And on that note (sorry!), AB effects slot support would mean that we could play an audio rhythm into something like Loopy or a DAW and send that to Impaktor which would allow us to tweak the synth while it responds to the original audio signal. AB effects slot support could obviously open up a lot of musical possibilities with the app but one interesting one for me that we can't really do now is: 1) record the raw dry audio and the Impaktor output simultaneously to two tracks, 2) end recording and route the recorded dry audio back to Impaktor, 3) change the base notes in Impaktor, 4) rejoice at the perfectly in-sync polyphonic tonal output. You can, of course, record two passes with Impaktor 1 but those passes being perfectly in sync is pretty much impossible.
Don't mean to welcome you back to the forum with a bunch of greedy requests! Just thoughts. Love your app(s). Good luck with whatever you're doing.
Cool. Thanks. I'm tempted then.
Impaktor in the effects slot would already be a huge improvement. Then I could run one instance on iPhone and another on iPad and connect 2 triggers to the iConnectAudio. The way it is now Impaktor only sees input 1 and so trigger 1 triggers on both devices.
I just realized it can't do background audio. That kinda sucks...
Just a quick request to say that I would prefer it not be done this way. This forces all users to buy both versions if they have iPad and iPhone. (and want a full screen version on iPad)
If you keep the universal version and then also release an iPhone only version, (which can be used on the iPad) then all users will be happy.
See Loopy and Loopy HD for a good example of what I mean.
After reading your first paragraph I thought, "He's right but it could be done like Loopy/LoopyHD." Then I read the second and third paragraphs.
This discussion has prompted me to get Impaktor...and I am having a great time with it. I have had a longstanding love affair with Sunrizer, but now will be sharing my heart with another wonderful BeepStreeter.
Thanks.
Kill her?
Impaktor: I'm trying to get Impaktor to work with an external audio interface (behringer UCA222) and a Roland drum pad as the "mi."
It works AMAZINGLY well, except for the fact that it seems that when I try to loop, the audio of another track is acting as a trigger for the selected track!
Do you know of any secret that will allow me to use the external audio interface to get the drum pad to work, but not have playback audio re trigger Impaktor?