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
@Nicebutfun said:
Yeah same is happening to me, they are pushing a fix for it soon. A joke that this slipped through beta testing though, too many people dick riding retronyms and Akai and not actually making beats.
It seems this glitch only happens when you move the slices for custom chops, not when you use the autochop.
Makes me wonder what everyone on this thread is doing with the app that so few people have complained about this! Is everyone just loading this app, hitting a few pads and screaming awesome? Just like the beta testers I suppose.. Lol
Jesus, the arrogance. How is 'hitting a few pads and screaming awesome' a terrible workflow worthy of such scorn? Do people HAVE to chop samples in order to meet your approval? Can't people make decent tunes using the stock samples? (Answer: Of course.)
I agree that the beta testers should have discovered the bug (and who knows, maybe they did but the release date was already set and it was too late to delay...), but this level of faux-superiority really pisses me off and it's annoying that it's gradually starting to creep its way into the Audiobus forum.
I read about the bug a few days ago ( in this very thread and twitter) and am patiently awaiting the bug fix update....i think the beta testers may be on par with the attention payed to this whole thread by @Nicebutfun & @Busker lol
@Michael_R_Grant said:
Yeah I know it was a asshole comment but c'mon this is an mpc... Mpc and chopping are intrinsic to the workflow. Sorry I upset you but it's just how I feel. I never mentioned anything about stock samples anyway? You can experience the bug with the stock samples...
Anyway I have nothing against how people use this app, it just suprises me that the MAIN feature of this mpc app is not even being used by most users. No wonder retronyms are so slack, they can ride the wave of congratulations from people that want a drum trigger machine.
Did you see that they actually responded to requests for midi out with "sure, but why would you want midi out?" That is ridiculous and there is no way in hell they don't understand the need for midi out on an mpc (midi production centre!). The mpc has long been considered a centrepiece in studios for midi control. It's all a big joke at this point, I guess I should blame myself for expecting a mpc from a mpc app
Sorry if I upset you
@DaveMagoo said:
I was one of the ones that mentioned this bug a few days ago
Fair point
It was this part of your post that threw me....
"Makes me wonder what everyone on this thread is doing with the app that so few people have complained about this!"
I do hope the update is out in days and not weeks though !
Thanks for the mixed comments. I had read about it some where, couldn't remember if it was on this forum or another. I am not here to hate or really moan, just wanted to know if others had the same experience that i regretfully suffered. Thankyou on the update that it is a bug and lets all hold hands and hope the update is a matter of days an not weeks, or longer GOD forbid......
I just expected ipmc pro to beable to deal with samples and chopping, from the start.
Perhaps if i had known this i may have held off buying, so until fixed this will sit in the pile with many other apps till the update
But once fixed, I will be very happy to spend many hours on this
P.S. thanks to everyone on the forum, i can garentee lots of apps have improved due to the comments here.
3 cheers to audiobus-----keep up the ground breaking work, ( might of been better for everyone if apple had just employed the bus boys from the beginning )
P.S.S. heard today that iphone 6 apparently will have 2GHz processor !!!!!
@Marco said:
Doing the midi learn in Tabletop frequently crashes the app and when you are successful in getting it to learn the pads, it doesn't save them to the session. The midi learn function is broken.
The midi learn works just fine in iMPC.
You will also have to transfer any of your sounds into the Tabletop version of iMPC Pro if you want to use them in Tabletop. You can't copy programs into the Tabletop version of iMPC Pro and will have to recreate them inside of Tabletop iMPC Pro.
We truly are the beta testers of this app. My composition sounds different every time I kill the app and then reload it. The word 'stable' in not what comes to mind first.
I just had 2 crashes......within minutes of each other.....not good.....how do you send crash logs with this thing?
What iPads are you running? On my mini retina I have not had a single crash...haven't since 3 updates past. I have some tracks that fill every inch of screen.
In Tabletop, do you mean IMPC crash??
Please give us the ability to tap anywhere out of the the current menu to exit it, as opposed to having to tap the menu select tab again which is a little counter intuitive (for me at least).
I keep tapping outside the drop down menu and then remember I have to close the menu by tapping the top:(
@KlaautuNinja on iPad Air all latest software versions...it's the Ram I think.....she a hungry lady alright...maybe cos I'm on safari on and off
Yeah close everything. And close any IAA apps after use. I tend to use the IAA recorder as if takes up less room onscreen and you can close the app afterwards.
In impc ,audiocopy2 leaves a huge gap at the end of the wav file and smaller when used inside Tabletop. (And it's been for over a year bug)...This means that the exported wav will never be synced for looping. Is that fixed on impc pro?
Is somewhere a list of all known bugs?
@DanWalton: From what i've read the Pro seems to have problems with external soundcards as well,are you already aware of this problem?And does the Pro support multiple outputs?
Can somebody please explain how to use the 16 level thing in a song. How to play a tuned sound, which means is there a way to do this from the timeline? How to access it besides from the "Main" menu?
p.s.
did a record from the Main, which results in the timeline in midi notes playing the tuned files, but you cannot see which is which tune, because all in the same line.
@helmutmaria said:
you can tune the notes in the timeline but it's easier just to record them in live with the short time I have used it...
@Korakios said:
>
>
No, the same problem is in the Pro.
@DaveMagoo, thanks for the tip. A Cubase user since the Atari times has a very midi orientated view ;-) Have to get used to the extended possibilities.
Somebody else with the problem that the choosen inter app fx in the mixer sometimes is saved with the song and sometimes not?
@Aphex said:
Really! I haven't even completed (impc pro crashed) an export but I really find it incredible that this bug has carried over from impc1
I'm going to start putting together a list of bugs, maybe we can get confirmation on fixes from retronyms. I just saw a post on mpcforums that listed a whole bunch of bugs too.
Hate to say it but I think big fixes will be put on the back burner for now, as retronyms still has it's fourth summer of awesome app to release.
They are sitting at the top of the music App Store right now, so they've already made their money from this.
It sends an interesting message to other app developers, I wonder if we will see more hype train video series in future
@helmutmaria said:
i have noticed that sometimes I setup some effects in a sequence (thinking they are global) and when I start the next sequence I realise they are only affecting the sequence they were set up on.
not sure if this is what @supadom was experiencing also? maybe it's just me lol!
yeah, the per-sequence mixer/fx settings is both wonderful and horrible! So cool that you can do it but a pain when you're just experimenting or creating a variation. Maybe I'm missing a way to copy the sequence settings without copying the notes.
@syrupcore said:
Just figured out you can set the mixer values globally when you tap into precision mode.
That said I have found a crash bug that is repeatable......if I try and set the master fader globally in the mixer tab (in precision mode) impc pro crashes every time....even on the demo projects...
anyone else get this?
I think it's about time for Willy Papers to come back and slap some more sense into y'all. There are no problems with Pro. Only uncompleted features.
@DanWalton said:
>
Dan, I really don't want to sound like an insensitive jerk but this response has been bugging the heck out of me. Why do you and others at Retronyms not understand the reasons and history around the MIDI mappings of the MPC? That sounds ridiculous to me. To be ignorant of that is not something I expected.
It makes me think the intent behind this app was to make your own proprietary self-contained sample trigger app, throw in whatever key mapping you found on the internet, skin it to stylize like a popular MPC and hope for brand association to carry you the rest of the way to the app store.
@Janie said:
lol
Over 800 comments on the Audiobus forum, for an app that does not even support Audiobus!
@Zymos said:
This app seems to have been heavily rewarded by this forum. Seeing as how I'm the last person on Earth to not own this app, a sincere question: what does iMPCP do that can't be done with BM2?
Earnest question, not hostile in any way, I thought that it was brilliant of Retronyms to answer questions here