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
There were so many good things about AP when it came out, but lack of Cycle/loop recording killed it stone dead for me.
It's like sticking a supercharger on a car before you've had the wheels fitted.
I don't know of any other midi sequencers that don't allow it, and I'm going back years.
I have't had Auria for long and am still using midi I have previously created and importing it so haven't yet found this a problem, but it does kinda put Auria down the list of awesome midi creation and recording tools. This is a real shame because the other midi editing tools are really nice.
Exactly Andy. I pointed the problem out when AP first came out. (It was the first thing I noticed) I thought Rim would have addressed it in an early update, or at least before adding all the knobs, bells and whistles.
Yeah it's a pain, I've just learnt to live with it. I just add midi notes in on a pass and then 'rewind' and do it again. Suppose it's from my tape days?
I'm sure our favorite German gentleman will read this, and hopefully chime in. Now AP has such usable MIDI the loop issue is probably only going to loom larger....would certainly be a nice addition.
Not sure why everyone thinks I'm German, but maybe I should start learning Deutsch
Believe me, I understand how important loop recording is, but it's something that's not going to happen for quite a while. Auria's playback/recording engine was never written with loop recording in mind, and a significant part of it would need to be re-written, taking possibly months of time, which I simply don't have right now.
Rim
Oh well, never mind.
Thanks Rim.
There was an experiment done a number of years ago where some sort of social science blogger stated that over the course of a year the average person swallows eight spiders while they sleep. This notion took off and was reposted/soon accepted as fact. I've decided to do the same with your nationality. I like Chicago, but there's always something more technical and mysterious about the idea of you coding away in Berlin. If you could begin to pepper your responses with odd German phrases (occasional use of umlauts etc), this would help. Thanks.
You are confusing overdub mode with cycle recording. There is overdub mode. There is no cycle recording yet. It's in the roadmap, according to Rim, but not implemented yet, and will take a lot of time for technical reasons.
EDIT: Rim answered it himself, just saw it.
You don't need to rewind: just activate aito-return and it will auto-rewind when you stop the record.
Ableton and Steinberg are both German companies, so It stands to reason that you should be German also
AUv3 support was/is far more important than loop record, so thank you for getting your priorities correct
Where's the fun in that?
On the subject of AUv3, can plugin parameters be automated in Auria Pro? I tried a few but didn't have any luck. May well be me being stupid though!
That's debatable. I can certainly not live without it
The options are there, but I tried here with iSem in write mode and could not write automations for its paramenters, It will go to the first page: thank you for reporting!
Thanks for noting it in the OP. On further testing, I cannot automate any plugin parameters, even the PSP channel strip. Also tried Timeless, with no luck.
Development is by no means a democracy, but my suspicion is that on this issue you may be in the heartfelt minority...
Oh I know that. People love knobs, bells and whistles
Congratulations @WaveMachineLabs on a job well done!
One of the main reasons we like AUv3 is so we can have multiple instances. So I set up 3 iSEMs in Auria Pro with different presets. Worked perfectly.
But when you go out of AP and re-open your song, all three load up the third patch. Or if you load up another patch in a different host, they all load up to that. The same thing happens in Cubasis, but not AUM.
This is not intended as a critique of Auria Pro, it just speaks to the weirdness of AUv3.
One thing I do like about iSEM is that presets saved in one host turn up in other hosts.
Apple needs to step up and give developers standards.
@Reid: could you try the following workaroud, please? For each of the three instances of iSem, save it as a preset - not in iSem, but it the the AU window! Then close and reopen and see if the problem persists. If it persists, recall the three saved presets and see if it brings back the correct patch.
further recording tests all had very significant jitter from a variety of AU and IAA sources. audio was both ahead and behind in the same render. in some cases the last midi note did not render at all.
ios 10 on ipad air 2
It's good to see Auria with AU support. However, I have tried to like Auria but the midi editing is a nightmare.
Is it really jitter or CPU overload causing dropouts, @wellingtonCres? Did you check the CPU meter? What is it saying? Please check it out if you can!
It may well be me doing something wrong, and no doubt someone here will tell me if that is the case. But so far I'm finding the 2.06 update rather frustrating.
Unlike Cubasis 2, which makes it easy to locate and load AU apps, I cannot find Auria's listing of them in a separate section, as I'd expected. When I try to add RF-1 it takes up the whole screen, so I need to keep toggling back and forth. Makes me wonder if this is actually loading an AU or a stand-alone version. Back in Cubasis land this is very clear and easy. Also, I cannot get the new keyboard to play any AU app.
EDIT
Found where I was going wrong. You need to load what is listed as Numerical FX in the green section. IMHO, this could be made more obvious.
How long you tried it? As for the current 2.06 and even the past 2.05, MIDI editing is a breeze, easy as in Garageband and more functional then Gadget. Do you still have Auria Pro?
How long you tried it? As for the current 2.06 and even the past 2.05, MIDI editing is a breeze, easy as in Garageband and more functional then Gadget. Do you still have Auria Pro?
cpu should not be an issue when offline rendering, but all the same it was just one monophonic line from a single app which played realtime with no issue.
@Nkersov, you have to arm the track to hear the notes you play. I don't have your particular AU to try, but iSem, Ruismaker and FM Essentials appear just fine. AUs appear in the same list as IAA instruments, but with a different color - green, I think.
Thank you: please list the jittering apps so O can put the issue in the first page, to warn other users.
>
Yep. Edited my post as I'd already discovered the green section. Would be helpful if these were listed under AU section, and IAA under their own section, etc. Cubasis makes this more intuitive. Thanks for the reminder about arming tracks to hear anything.