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
@Fitz - I'm going to add a latch mode - which will allow steps to send midi note on but no note off message - this will be used for drones. The idea being that you run a sub-sequence (basically a snapshot) in latch mode to create your drones, then use midiSequencer in normal mode to play the non-drone devices.
note sustain is would be outside of steps really... when you get the rack version you can create a slower tempo track to extend the notes over the top of other (faster) sequences - this will probably give you what you are after.
Latch mode sounds good. Thanks
@midiSequencer
CC MIDI BUG?
I’ve been using both the Lemur and the midiSequencer apps to send midi CC messages to control rrarrow. It works fine for Lemur but only the first CC sent in midiSequencer works. I use the same setup to control BitWiz with both apps and both work. I hope this is helpful to you in implementing a more robust midi implementation.
It would be nice to have the option of sending CC only to some apps, both notes and CC to others, some notes only, and combinations thereof.
AUDIOBUS BUG
When using midiSequencer in Audiobus with an app in the effect slot, it ends up muting the sound output unless I create a second Audiobus signal chain and add midiSequencer there. There is no problem when I use midiSequencer outside of Audiobus although it is very convenient to control apps with the popup menu inside Audiobus.
I really like the app and the IAP too, plus the manual. There's a lot of functionality in the app.
@Paulinko let me try and understand what you are reporting then?
1) Bug : rrarrow is only receiving midi CC1 not CC2, 3 or 4? So you think MS might not be sending more than 1 CC at a time. Ok, I've checked the code(variations of 4 sent, cycle button(on/off), CC only send), & debugged the output, and it works as expected. Will try a test on midi later as I don't have rrarrow.
You are setting different CC's in Options Panel?
2) sending cc only per device. Yes like that, will modify the Devices output to allow you to set per output.
3) Some more details would be nice on the mute problem - what app were you using in the effects slot? Audio is midiSequence is 0 volume, but it works with the effects I've tried.
Glad you like midiSequencer. v1.7 will be out very soon with some bug fixes of 1.6 (main one being the < > shift sequence buttons don't work).
@midiSequencer
The video shows what I've been experiencing. The lack of sound output could be related to apps with audio feedback as Bias has the same behavior and birdStepper doesn't.
The first CC in the list in midiSequencer is received correctly by rrarrow, the others are not and rrarrow works fine with Lemur so it's an interaction between midiSequencer and rrarrow.
UPDATE
midiSequencer Audiobus Mute Bug:
rrarrow, deregulator, Bias, AmpliTube, Attractor, Flying Haggis, Turnado, WOW
Okay with midiSequencer:
birdStepper, Effectrix, AUFX:Dub, Crystalline, Final Touch, JamUp Pro
@paulinko - thanks for posting. It's going to be difficult for me to work this out without having the apps - so I might have to buy them!
coreMidi is coreMidi - rarrarow not getting midi CC's whilst others getting 4 can only be a problem with rrarrow. How you are sending may also have an effect - are you sending it from midiSequencer virtual midi - or direct to rrarrow? I will try it out however....
The mute audio problem might be midiSequencer audio setting - after all it doesn't do audio, so will check the settings...
I notice rrarrow was updated on 6th june - is it that version you tried? I've also contacted the developer to ask if his app supports 4 midi controllers.
@Paulinko - alex the dev of rrarrow is going to try this tomorrow (we exchanged apps).
@midiSequencer Thanks! If it's any help, if I connect with rrarrow directly I get nothing. If I do midiSequencer out I get only the first CC. If I do network midi using the Apollo app send Lemur output to Apollo out to Session 1 into core media on the iPad running rrarrow, everything works. If I do output from Lemur to rrarrow, nothing. If I do Lemur to MidiBridge with MidiBridge connected to itself and the network sessions connected to themselves it works too.
@Paulinko - hopefully alex will come up with something. He did a quick tryout using cubasis and noticed a problem.
@Paulinko hello and thanks for the report. Will check that issue with rrarrow and hope to fix it in the next update.
Regards, Alex
@njazz thanks! Great app.
@midiSequencer The update of Audiobus seems to have added a new twist to the muting of apps with feedback when midiSequencer is in the same signal chain. If rrarrow, deregulator, or Strange Attractor is in the input slot, you get sound but if any of them is in the effects slot, you get no sound. Therefore the issue may revolve around how these apps react to the sound midiSequencer is putting out? Perhaps they interpret zero volume as a condition where feedback protection has been initiated and therefore mute the sound?
yes I noticed that when I tried after the AB update.... No sound at all.
midiSequencer only outputs audio when in the background (to keep it from being suspended - so it plays a wav file at 0 volume every 10 seconds).
Are you saying you have no issue if midiSequencer is not in the input stack?
I can have midiSequencer in the input stack so long as the feedback app (e.g. rrarrow or Bias) isn't in the effect stack. If the feedback app is in the input or output stack and midiSequencer is in the input stack, there is sound. If midiSequencer is in the input stack and a feedback app is in the effect stack there is no sound.
Hi. Would someone tell me what IAP offers? Thanks a lot!
The IAP offers the ability to add additional notes to the single (or maybe ornamented) steps of the sequencer. Up to 127 notes additional notes can be added using a 2 octave (transposable) keyboard.
Choose from some preset chords or just tap keys to add additional notes. Chords (with additional notes) can be inverted up & down the keyboard.
The keyboard can show you notes foreign to the current sequence scale.
Each note (including that of the step) can be modified for velocity & length relative to the step note.
Where steps are ornamented, the chord will play normally with the step note only being ornamented (e.g. Baroque mordents in the middle of a chord say).
V1.7 due out soon will include the ability to save a copy of a chord and paste it on another step.
Thanks, and sorry for asking the same here and fb.
No problem. I've a short audio demo of what midiSequencer chords & ornaments sound like on the ipad using just one patch of sunrizer