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
@Crabman it's working here fine apart from some wonkiness when it isn't. I know, helpful.
Not working for me in Cubasis or Auria .If I load SPA from the Audiobus screen it comes up with the IAA controls but they don't work and the tempo is stuck at zero and I can't get any controls to work.It worked fine until this upgrade.I tried deleting and restarting everything but on go.I emailed the Dev who is very responsive so hopefully it will get fixed soon. IPad Air 1 ,IOS 7.12.
Hi JohnnyGoodyear,what IPad and IOS are you using? The strange thing for me is that it was working when I first got the upgrade and then it just stopped responding.Any ideas would be be appreciated.Thanks
@Jomazz Air1/8latest I am getting some stuttering, then all's well, then a stop, then some stuttering. Pretty random. Def. needs a fix.
Yes, StepPolyArp 2.5 very buggy ! that is what I feel now. Can anyone play it with Cubasis 1.9 midi recording?
Yes works fine here. Been Using it as an IAA Instrument in Cubasis 1.9 triggering the internal sounds. Works rock solid no glitches at all. Even Rendering is fine.
Experimented with midi thru to other Instruments. There seemed to be an an issue but i can work that out by directly Routing the midi with step poly arp itself so I used the IAA Instrument to Trigger Thor IAA (over AB2) without any Problems.
This update got my attention because the fact that StepPolyArp forces you to think numerically in semitones (instead of in notes, which is how basically every other MIDI sequencer works) was really impeding my use of the app. I absolutely LOVE a lot of things about the interface, the note editor, randomization, etc., so I wanted this to be my primary MIDI app. But setting things up 0, +1, +3, etc. might be clear to someone better with theory than I am, but it was never clear if "0" referenced the root note triggered on the keyboard, or something else. I will definitely revisit the app to see if this helps me.
Fixed note adds so much with so little! Super nice update.
"Numerically in semitones" is great when you want to send different chords to the same pattern... Think roman numeral chord notation-! Set all of the row transpositions to zero and start sending chords over midi, you'll be blown away at how flexible this system is
I still hesitate to buy it but it would be really great as an IAA Midi plugin in Cubasis or Auria (like somebody already mentioned).Nonetheless,a friend of mine which has the same setup (Air 2 with 8.1.3) did a quick test as IAA in Cubasis and routed midi to micrologue but it didn't work (micrologue did not respond).Although i can't exclude he made a mistake (but routing in cubasis is stupidly easy,no?).Unfortunately he went to bed now,leaving an old appoholic in the dark for tonight
@Kaikoo I do apologize, I made it out to be easier than it is, because I too ran into some midi issues with Cubasis. I fixed it by deleting the track an trying again, and for whatever reason it worked.
Yes, working with midi in iOS is a pain, seemingly with whatever setup you've got going.
One thing, IAA is not necessary for midi. So you don't need to load StepPolyArp into Cubasis to use it's midi. My setup was: load Nave into Cubasis with IAA, then route StepPolyArp's midi into Nave's Cubasis track. Like I say, didn't work at first, deleted the track then tried again and it worked.
I know it's not necessary but more much comfotable to open end edit it from"within"the host.Not to mention that the IAA sync is supposed to be way more reliable and no need to setup anything (Effectrix works always like breeze this way for example).And on top of that,SPA will be saved with the project (although this has it's own flaws,i know).If i use it just parallel with Midi sync...it will be a hit ot miss if the sync is usable on my device.Often enough it turned out that the same setup,that works for one,didn't worked for others...unfortunately.
For me it's really only interesting if it works as IAA.But if the developer has an open ear to his customer maybe i'll purchase it anyway and see how it runs.
This worked nice prior to the update but is useless in it's current state. Looking forward to a fix.
Guess what? I do not know how I mess around 3rd synth with SPA and cubasis. I do know after some tests, StepPolyArp 2.5 can not functioning with 3rd Synth ( without cubasis 1.9 ) , even after restart the Ipad. So it supposed to work fine without Cubasis to play easily, but SPA ends up dead with no movement of any sort of stubbornness. So strange experience. I had to delete SPA again to re-download form store. Ha, Never have this kind of experience on Ipad.
@Kaikoo Don't lose heart, but hope all the same for a fix release soon...
I got an email from the Dev and he is aware of the problems.He said a fix has been submitted to Apple but it could take nine days for approval.Hopefully he got all the bugs.
Guess I better postpone the world tour....
Thank you to notify!
Thanks,my bucks are safe for another 9 days then.
I don't understand though why he didn't used an expedited review now.That's what they are for if you break your lil peace of software and you don't want your customer waiting for that looong review time.
I came just that close to not updating right away but I could not resist and have learned my lesson hopefully to wait for reports prior to updating. This app has been so rock steady for me though I erroneously believed I would be alright! More than happy to wait for such an important piece of kit though. I can definately say I will miss it!
Anyone who is having problems should email the Dev because it seems that there are different problems depending on if you're on IOS 7. or IOS 8.He may not be aware of all the different bugs.I will ask him to check this forum .
I bought it now to help iron out the IAA issues.I also can't get it to work properly.It always quits working after a few seconds of playing.I tested it with cubasis (only cubasis internal sounds).Also,the IAA sync is not tight.Notes playing (well,IF they play...) a little delayed.I already sent a mail to the dev.I'm using Air 2 with 8.1.3
Hi (from StepPolyArp developper), there is an issue on some setup when connecting StepPolyArp to Audiobus, the tempo goes to 0 and Audiobus is detected as a sequencer host, what that should not. A fix (2.5.1) is already waiting for validation to Apple, sorry, this is a random bug that not appeared during tests.
Please for bugs report, or features, use the contact support page:
http://laurentcolson.com/contact.php
Laurent
Hi Laurent,thanks for stopping by.Do also find out more (or better:fixed) about the IAA issues?
As i've already written here (and in a support mail ;-),IAA was the main reason i bought it now.
Some app sitting in Cubasis right away, Some are not. StepPolyArp is not! You can tell from the first time play. Please, fix the IAA full support.
Not just IAA! I just open StepPolyArp. You know what' hpaaen? It is not moving anything when you touch the piano roll. Totally dead.
Yes this happened to me after I was playing around with it in Audiobus, it also froze and crashed my ipad several times (one of the few times my ipad had a blue screen of death).
I've got it working again, I'm not quite sure how... maybe it was loading my saved preset before the crash which had stored some audiobus data. I tried loading a factory preset upon starting the app. This seems to have fixed it for me and is now working as normal outside of audiobus at least.
Try deleting the app and reinstalling it
I tried everything possible now,multiple times reinstalled,restarted etc and there is just one possible configuration where it more or less worked as IAA in cubasis.Besides this i always get midi feedback loops and the cpu climbs to 100% (=cubasis freezes).But the timing is too shaky and a little delayed.I gave it up for now.BUT i just tried SPA the"oldschool"way (open the app but not in cubasis) via midi sync and i have to say this is one (if not THE) of the most tight syncs i've ever had on iOS.Just a little midi delay in cubasis (arround 10ms) and it works like a charm.I already felt in love with SPA
The only downside:running cubasis in a loop causes a small timing"jump"in SPA whenever the loop starts from the beginning again.And then it's not in sync anymore.Only solution so far:setting a long loop so i have a few minutes to tweak SPA before i have to switch back and restart the sequencer.If i'm happy with my arp i just record the notes then (works also flawless here).There is obviously room for improvements but the rock solid clock was worth the purchase alone 
Wow, I feel fortunate that I held off on the update, but, I have to encourage people to buy this app. It's completely fantastic, and well worth the money. Don't take my word for it, search the forums, this is a tried-and-true winter.