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 two finger version would essentially replicate (and one up) the little stutter pad on the BSP and Roland Aria boxes. You could stutter any stretch at any length of the sequence.
Thanks for the ideas and bug reports! Working on an update now, bugs and crashes are top priority for now, features later.
I think you can do part of what @Samu was asking for by toggling the CC sliders on, and then pressing the "input" button on the right so it becomes "mute". This will keep MIDI going through but won't record it in the sequencer. This was originally a play mode as suggested but I didn't like toggling through so many modes. I still don't so I may put it back there and make it a popup.
I also used to have it play the currently pressed note as suggested! I ended up changing long presses to bring up the step edit, which I really liked, so I took out the play. But if I put that play mode back, you're right, it'd be nice there. Will add to the request pile
Also like the double press suggestion, I want to do that for the regular start/end mode as well.
The timing I'm looking at. I've noticed it seems to happen with certain synths and not with others. I send MIDI out a certain way, maybe some synth apps don't like the way I do it and I need to tweak it. Also possible those synth apps could be prioritizing MIDI lower and when things are active they don't see the incoming notes at the right time. Also possible iOS 9 has done some weird things with MIDI. The most likely reason is always #1, but I'm always happy to discuss at length how it could be somebody else's fault! Anyway I will keep testing and keep improving.
A couple suggestions for timing would be decrease the audio buffer latency in the synth app or AudioBus to improve responsiveness in the synth apps, and to trying increasing the latency setting in midiSTEPs to calculate and send the MIDI out earlier.
If you're having trouble with unreproducible crashes, stopping the sequencer when you delete, insert, change steps would probably help. This is of course no fun, which is why I want it to work in real time as the sequence runs, but that is likely the gnarly bits of code where timing differences in devices / OS versions or randomly doing something at the exact wrong moment exposes subtle bugs I haven't found yet.
Thanks for the feedback! Fixes coming soon.
So i bought it, because if the developer, i like these kind of people
I think it's sad when people suggest that an app isn't worth what the dev is asking for it or ask for promo codes etc. (as happened on another site I frequent) I bought both apps at full price and have absolutely no regrets at all. They are brilliant and well worth the price. Support your devs!
Afaik the problem is not your 6+ but the app store that doesn't seperate other than "iPad vs.iPhone" and therefore impossible for devs to realease something for the 6+ without including most other phone models as well.
@topic: how is (IAA)midi sync on this one?
I've been fixing things and will be submitting an update soon.
The one thing I haven't been able to reproduce is the tempo going to 0.0, any hints on features you might be using (loop vs one-shot? syncing or linking set to something other than default? receiving MIDI clock?) that could help me track that one down?
Not happening today so it could be one of those issues that only affects newly installed apps that go away when you reboot. The BPM got set to zero when the sequence stopped playing (not from me pressing stop).I tried leaving a sequence today and it didn't stop running. I have never tried the one shot or link settings yet.
I noticed in Jakob Haq's video, that the tempo was set to 0.0 BPM as well. So you might ask him if he noticed anything similar.
I will keep an eye out for this happening again but you shouldn't make it a priority unless others report the same.
One other thing I noticed. The timing can be a little bit off. More noticeable with simple slow sequences. I noticed it on a single slow three note melody, it seemed to lag a little on the one note.
Anyway, looking forward to the updates.
I've been trying to re-preoduce the tempo slowdowns without any repeatable results.
I have noticed that sometimes the tempo slows down audibly between start and stop while the set tempo remains the same. The only reason I can think of (for now) is that the 'midi-buffer' is not cleared between start and stop of the playback.
I do wish more synths would implement/include this 'style' of sequencer (thinking about Sunrizer with this SH-101 style sequencer). And well, even Steinberg could add a step-sequencer/arpeggiator-plug-in to generate midi-data for the tracks
Anyway, midiSTEPs still remains as my go-to sequencer for quickly noodling up ideas and jamming.
Other ideas would be to include a 'transpose sliders' for the 'mixer' tab that could be linked between tracks to quickly transpose multiple tracks.(ie. for example bass-line and chord/pad track).
As I won this app and midi lfos, I've been having so much fun with them. I have lots of midi apps, but this one and MidiSequencer are my firm favourites.
Very nice update come out today, version 1.0.1
I really enjoy using Midisteps! Very comfortable to make music with.
Just one little thought, if MidiLFO were built right within, this could be really fantastic and outstanding midi sequencer.
Thank you.
^ Or a 'You already own MidiLFO? Cool. Here's a perfectly placed dedicated OMAC button." With the converse in MidiLFO, natch.
Had midiSTEPs and Funkbox singing along happily last night. Not pestering; I know you already heard me about the clock stuff but I started dreaming of using a single channel in FB (or perhaps the bass line channel) to control the the step clock of midiSTEPs—just like I used to do with my 606 and 707's Trig Out -> SH-101 Clock in.
Along with the previous wheel greasing idea to jump between STEPs and LFOs, really the request here, if any, is that you be dreaming of ways of how all of your bad ass unix-style single purpose apps can be a family. Including dead simple ways for users to connect and jump between them. Yes, please continue to do a great job implementing existing standards (midi, ab, iaa...) but I hope you wont be shy about implementing your own pipes.
Hey, sorry for the delayed response, for the second consecutive release of midiSTEPs I was out of town. I need to break that pattern, it doesn't work too well.
If you find any bugs in the latest version of midiSTEPs let me know, I'm still trying to get it working rock solid before adding too much new stuff. I do finally have that 0.0 tempo bug tracked down but had already submitted the update when I found it, so it will be in the next update. If you have any crashes let me know, I got the bigger ones with this update but I'm sure there are still some left and I'll be combing through the crash logs and nailing them down.
I'm planning to get an iPad Pro when they come out so I can work on the split screen / adjustable screen size stuff. Working on that will give me a better idea of how to approach app switching and some of the other things that have been requested. I'm reading all the requests, I'm agreeing with lots of it in my head, I'm just trying to choose my shots a little more carefully this time with these apps so they keep working well into the future. With FunkBox and Little MIDI I boxed myself into some corners and I'm trying to avoid that happening again, it's an interesting time for iOS music apps and I don't yet have a great feel for where everything will end up. Hopefully playing with the Pro and working with split screen will help. Moving between apps and how to have certain features available in the app you're currently using are both things I've been thinking a lot about.
I also have one more app I want to release this year that I think you'll like. I've been working on all of these apps for a couple years now, I actually wanted to release them all LAST year which was stupidly optimistic. But I hope to get that other one out and then I can work on making them all better. I don't want you to think I'll be neglecting this app when it's released, I won't, I have plans... oh, I have plans... just trying to let some things settle, see how things pan out a little more in the post-iOS9 music app scene in general, and then I'll get things working.
Thanks! Let me know about those bugs.
@artkerns I do have a simple request for the next version.
Please make the keyboard transposable bellow C-2 (C-1 can be reached when playback-transposing the pattern). Some sound modules/synths (for example iM1 and iOS-SoundCanvas) map sounds way down so it would be nice to be able to access the whole range of available midi-notes.
So far no more hickups but the cc-panel is sometimes drawn over the note-keys instead of bellow them, will try to find a repeatable pattern so it will be easier to track down and fix.
Thans for the update!
I like this comment.
BD : [s1][r1][q][c]
CHH : [p][s2][e2][r2]
+1 for transpose beyond C2.
Is there a reason this restriction?
{,.:.,!::,.:.;.:.}{,.:.,!::,.::,::.}{,.:.,!::,.:.;.:.}{,.:.,!::,.::,::.}
I put the lower keyboard limit on the to do list, I will see how easy it is to add, hopefully it is. Things that seem simple to change can sometimes break other things when assumptions have been made in the code.
I'm not sure how I originally picked the range, but the synths I tested it with were sounding pretty sub-sonic down there, so I might have just arbitrarily cut it off based on the ones I was using. I might have also put it there because I originally let you transpose +/- 2 octaves, and wasn't sure what to do if you transposed too far down? I forget where the lowest MIDI limit is. I'll have to check the code and my assumptions.
Thanks for the CC display mention, I was able to replicate it by switching parts with different CC settings in non-record modes. I'll try to fix that too.
Got this recently and like the simplicity of it, the UI and colors (the palette reminded me of that movie "Her"), and that its 4 tracks. Funkbox and Little Midi Machine set a great standard for the midi patch bay, and this is similar in niceness for routing the midi to other apps. Love that the routing is a big button on each page, rather than buried somewhere.
Liked the options for pattern doubling macros as well, and that there is a mixer page with mutes and solos.
I had a feature request (everyone's a critic!) for Mr. Kerns, if he was interested, and there were resources for ongoing development? I realized after buying it, and using it for a while, I have a hard time conceptualizing a bar of music as a list, with rests, etc, (especially at a 16th or 32nd note resolution), and then entering it. I was imagining how easy it would be to use midisteps if there was a live record option, where the key you press is entered into the current step that is playing. Like if the grey step edit page is just following each step as they play? One using that kind of note entry could start by filling in all rests to define the loop length.
I guess 'live-recording' into midiSTEPs would not be too hard to fix?
For me I'm used to entering notes into a tracker where the rest is just a press on 'arrow down' to skip a line while playing the keyboard the way midiSTEPs work was very easy to adjust to.
Even the new Roland 'Boutique' line works pretty similarly, press/hold a step and enter a note
I'm hoping the new synth from BeepStreet will have a built in sequencer similar to midiSTEPs. For now I'm holding of getting new synths until it arrives and keep my finger off from the buy button even if the new Virsyn thing is tempting... (Already got way too many Synths but keep on coming back to a selected few, Sunrizer, Magellan, iSem and AniMoog).
Dear @Samu,
Poseidon Synth should be my selected few, so unique combinations on its own.
@Processaurus Yes I'd like to add a live record mode, it's on the (big) list. One thing you can do in the mean time with the current version if you don't like planning everything ahead, if you press and hold down an empty step (say step 16 when you only currently have 4 steps) as if you were editing it, it will pop up and let you edit it, and then fill in any missing steps with rests. So you can start by doing that with step 16, put a rest in there, then you have 16 steps of empty rests, and then can edit the particular steps where you want to put the notes in.
@artkerns
I managed 'recreate/repeat' the crashes I've been experiencing with midiSTEPs, ie. happens every time I try.
The 'crash' can be categorised as 'unexpected user behaviour'
To reproduce the crash simply have the 'record/transp/pattern' button set to either 'transp' or 'pattern' and touch a step that has nothing recorded on it and boom, back to home screen. ('record' mode doesn't crash when touching the steps (clear, note or no note) and plays/previews the step which is I presume intentional behaviour and makes playing the steps manually a breeze, nice!). This 'crash' also happens wether the pattern is playing or not.
Don't know if this is only on Air 2 iOS9.0.2 since I have no other iPads to test on...
Maybe some of you others who already have midiSTEPs can try if it crashes on your iPads?.
Does it crash for you?
The workaround for now is to always make sure 'record' is selected before touching an empty step
@artkerns Hmm...
I wonder what happened to my long post describing how to re-create the crashes i've been having with midiSTEPs, could be a forum bug...
The steps to reproduce the crash are very simple and happens every time on my Air 2 iOS9.0.2.
Happens every time wether the pattern is playing or not.
I'll make one more try to post regarding the crashes I've been having with MidiSTEPs...
(Somehow the other two are waiting for moderation?).
To reproduce the 'crashes' every time try this.
You're welcome
(Wonder if this reply gets thru or needs 'moderation'?).
The idea only applies when 'hold' is active/blinking, otherwise it would slow down the entries.
@artkerns
I managed 'recreate/repeat' the crashes I've been experiencing with midiSTEPs, ie. happens every time I try.
The 'crash' can be categorised as 'unexpected user behaviour'
To reproduce the crash simply have the 'record/transp/pattern' button set to either 'transp' or 'pattern' and touch a step that has nothing recorded on it and boom, back to home screen. ('record' mode doesn't crash when touching the steps (clear, note or no note) and plays/previews the step which is I presume intentional behaviour and makes playing the steps manually a breeze, nice!). This 'crash' also happens wether the pattern is playing or not.
Don't know if this is only on Air 2 iOS9.0.2 since I have no other iPads to test on...
Maybe some of you others who already have midiSTEPs can try if it crashes on your iPads?.
Does it crash for you?
The workaround for now is to always make sure 'record' is selected before touching an empty step
@artkerns Hmm...
I wonder what happened to my long post describing how to re-create the crashes i've been having with midiSTEPs, could be a forum bug...
The steps to reproduce the crash are very simple and happens every time on my Air 2 iOS9.0.2.
Happens every time wether the pattern is playing or not.
I'll make one more try to post regarding the crashes I've been having with MidiSTEPs...
(Somehow the other two are waiting for moderation?).
To reproduce the 'crashes' every time try this.